Guides & resources
Rate limits & concurrency
Requests are subject to per-key and per-account concurrency and rate limits.
How limits are applied
Limits are enforced at multiple levels: per API key, and per account across all of your keys combined. Exact numeric limits depend on your plan and are shown in your dashboard rather than fixed in this documentation, since they can be adjusted per account.
- Per-key concurrency — the maximum number of in-flight requests for a single API key.
- Per-account concurrency — the maximum combined in-flight requests across all keys under your account.
- Rate limit (requests per time window) — enforced per key.
What happens when you hit a limit
Depending on the endpoint, an over-limit request is either rejected immediately with HTTP 429, held briefly in a wait queue, or (for async task submission) queued for later processing. A 429 response includes an OpenAI-compatible error body with code rate_limit or concurrency_limit_exceeded — back off and retry.
Checking your current limits
See the Usage / Plan section of your dashboard for the concurrency and rate limits attached to your account and each key.