Rate limits & tiers

Standard tier (live today)

Over-limit requests get 429 with a Retry-After header. The limiter is atomic and multi-instance safe — it counts in the billing database, not in any single server's memory.

Spend caps (optional, per key)

At key creation you can set a daily spend cap. Once the key's 24h spend crosses the cap, requests fail with 402 key_budget_exceeded — even if the account balance is healthy. This is the blast-radius control for agent workloads: if a prompt loop runs away, the damage stops at the cap.

Model caps

Some models cap the per-request estimate (reasoning models with huge context can estimate high). If a request's worst-case exceeds the cap you'll get 400 est_too_large — lower max_tokens or pick a bigger-balance account.

Retry posture

• 429 — honor Retry-After, exponential backoff with jitter
• 529 upstream_warming — retry after the header value (seconds; the autoscaler is provisioning capacity)
• 502 upstream_error — safe to retry immediately; the failed attempt was refunded
• Idempotency: retries create fresh reservations, so failed attempts can't double-charge even if you retry in a tight loop