Rate limits
Requests and tokens per minute, how a 429 tells you when to retry, and how to get more.
Rate limits
Limits apply per account (shared by all its API keys) and per model (a model's pinned versions share its budget; fast mode counts as its own model). A request that would cross a budget is refused with 429 and a Retry-After header; retry after that many seconds.
| Budget | Per minute |
|---|---|
| Requests | 100 |
| Tokens (prompt, cached prompt and completion combined) | 10,000,000 |
Need more? Email hello@openscale.so with your account email and expected volume, and we will raise your limits.
More of the API reference
- API reference: base URLs, authentication and a first request.
- Chat Completions: POST /v1/chat/completions: the OpenAI Chat Completions format, streamed or not, with reasoning and tools.
- Responses: POST /v1/responses: the OpenAI Responses format with stored state, background runs and enforced tool rules.
- Conversations: Keep the turns of a Responses conversation on our side and continue it by id.
- Prompts: Save instructions, messages and settings once, then use them by id in the Responses API.
- Anthropic Messages: POST /anthropic/v1/messages: the Anthropic Messages format, for Claude Code and Anthropic SDKs.
- Models and pricing: Model ids, prices per 1M tokens, context windows, output limits, versions and the live catalog endpoint.
- Batch: Upload a JSONL file of chat completions, create a batch and collect the results when it finishes.
- Errors: The error shape, every status code and code, and which ones to retry.
- Data retention: What is stored, for how long, how to delete it, and zero data retention.
- Interactive reference: try every endpoint in the browser.
- OpenAPI document: the whole API as OpenAPI 3.1.
This page as Markdown: /docs/rate-limits.md