Skip to main content
Organization API keys have no Beeble Developer API requests-per-minute, requests-per-day, or concurrent-job limits. This includes product estimates, submissions, account reads, and the legacy SwitchX generation endpoints. Personal API keys retain their account limits. Credit balances, model permissions, source limits, and upstream provider constraints still apply. Use a delay between polls and exponential backoff if a downstream service returns 429. Preserve the same idempotency key and request body when retrying an uncertain submission. Unlimited concurrency does not make a replacement request safe: the original job may already have started and charged. Use max_credits to cap each job’s charge. See Billing & credits and Jobs & retries.