Rate limits

26Rate limits

Every key gets 60 requests per minute. Each reply carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and going over returns 429 with a Retry-After in seconds. On top of that an account may have 8 requests in flight at once; a ninth gets 429 until one finishes. The per-minute limit counts per key, so one runaway job cannot starve your other keys, while the concurrency ceiling counts per account, because that is what protects the balance itself.

To be precise about the two scopes: requests per minute is per key and concurrency is per account, across all of that account's keys. Running a batch workload (an OCR queue, a backfill) that needs more than 60 rpm? Write to us and we raise the limit on that specific key; the new ceiling shows in X-RateLimit-Limit and on the key in the dashboard.