Skip to main content
Rate limits cap how many requests and tokens you can use in a given window. Your limits are set by your tier, and each limit applies separately to your organization, each project, and each API key.

​
How limits are measured

Every limit is enforced at three scopes — organization, project, and API key — and a request counts against all three.

​
Tiers

Your tier is the higher of two things:
  • your subscription plan, and
  • the spend tier you earn from your total lifetime payments.
Whichever is higher applies, so paying more — by subscription or by usage — only ever raises your limits. A subscription sets your tier immediately. Spend accumulates over time and graduates you automatically — a free account that has paid $200 in usage reaches Tier 3 without a subscription.

​
Limits by tier

Values below are per API key. Project limits are 1.5× and organization limits are 2× the per-key request and token values. Concurrent-request limits are set per scope:

​
Rate limit headers

Every response reports your current usage:

​
When you hit a limit

Requests over a limit return 429 Too Many Requests with a Retry-After header. Wait for the indicated delay and retry, ideally with exponential backoff. See pricing for per-token rates and plans to subscribe or buy credits.
Last modified on August 11, 2026