Skip to main content
On this page

Limits and the balance

Two things bound a request: the rate limits, which bound how fast a key and an account can spend, and the balance, which bounds how much can be spent at all.

Rate limits#

LimitScopeBehaviour
Requests per minuteper key and per account0 means no per-key limit. A burst up to a whole minute is fine, and the allowance refills evenly
Tokens per minuteper keyAn estimate of input plus the output the request may ask for. 0 means none
Daily and monthly spend capper key and per accountAn optional cap in EUR on settled spend, per UTC day and per calendar month. Requests in flight still finish; past the cap the key is refused with 429 daily_cap_reached or monthly_cap_reached until the period turns
Concurrencyper accountThe account's requests in flight, from its usage tier (below). One more is a 429 rate_limited with a one second retry-after

A key created without rates of its own starts with 60 requests and no token rate limit. Set a token rate on the key at any time; a lower one applies. A key never raises the account's rate: an account's requests are counted together, whatever key they arrive with.

A refused request still carries the retry-after and x-ratelimit-* headers: x-ratelimit-limit-requests, x-ratelimit-remaining-requests and x-ratelimit-reset-requests, and the same three for -tokens. A reset is a duration such as 1s, 6m0s or 120ms.

Usage tiers#

An account's default limits follow the total it has topped up over the life of the account, not its balance. Spending the balance never lowers a tier. The total counts the money that came in through a paid top-up; sandbox or test credit is not money that came in and does not count.

TierLifetime top-upsRequests a minuteRequests at once
Tier 1under €10048080
Tier 2€100 and above1,600200
Tier 3€500 and above4,000480
Tier 4€1,000 and above8,0001,200
Tier 5€5,000 and above16,0002,400
Company / Enterpriseset per accountset by the operatorset by the operator

The two figures are the account's: every key shares them, and a key may set a lower requests-a-minute rate of its own but never a higher one. The same holds for the spend caps: a key can cap its own daily and monthly spend under any account-wide ceiling an operator sets. Company and Enterprise limits are an operator's per-account override, which wins over the tier; an account that has one keeps its top-up tier for the table but is limited by the override. The Limits page shows the figures in force and the tier table they come from.

If a limit cannot be checked, the request is refused with a 503 rather than let through.

Endpoint scopes#

A key carries a set of scopes, and each /v1 endpoint needs the scope it belongs to. A request outside the key's set is refused 403 insufficient_scope, naming the scope to add.

ScopeEndpoints
inferencePOST /v1/chat/completions, POST /v1/messages, POST /v1/responses and their token counters
modelsGET /v1/models
usageGET /v1/usage
toolsPOST /v1/tools/search and POST /v1/tools/browse

A key created in the dashboard starts with inference and models. The dashboard sets and edits the scopes of a key. The MCP endpoint is not gated by them: it reads and writes a vault rather than generating.

The balance#

Credit is bought in crypto and kept in EUR. A request reserves its estimated cost before dispatch, the input plus the output it may ask for, and settles the real usage after. A balance that cannot cover the hold is a 402 insufficient_balance, and nothing reaches a model.

When the balance covers less output than the request asked for, the output cap is lowered to what it covers and x-token-notice says so. A hold that outlives its request is dropped after 15 minutes. A negative balance is owed and is offset against the next top-up.

The balance is the only limit on how much can be spent. There is no monthly allowance, no overage fee and no automatic refill. A refusal costs nothing.

See also#

  • Usage for the endpoint that reports the balance and the day
  • Billing for how credit is bought and how a request is priced
  • Errors for rate_limited, insufficient_balance and the spend caps

This site uses only the technical cookies the sign-in and the security need. No analytics, no advertising, no tracking. Cookie policy