Skip to main content

​
Track your usage

The usage page shows your spend over time and a summary by model. Your current balance and recent activity are on billing overview.

​
Spend limits

From the usage page you can set:
  • a monthly cap — a hard ceiling on monthly spend, and
  • a warning threshold — you’re alerted when spend crosses it, before the cap is reached.
While a monthly cap is reached, requests are refused even if your balance is positive. The cap resets at the beginning of each month (UTC); to resume sooner, raise or remove the cap.

​
What a refusal looks like

Whether the cause is an empty balance or a reached cap, the API responds the same way:
  • REST requests fail with 429 and an error body with "type": "insufficient_quota".
  • Realtime sessions receive an error event (type: "insufficient_quota") with the upstream message, then close with WebSocket code 4429.
See Common error types for the full error reference, and Payment & credits for how to add credits.

​
Concurrency

Realtime connections are also subject to a concurrency limit: exceeding it closes the WebSocket with code 1013 (retry later). See the Realtime API overview for the close-code table.