Rate limits

Per-key rate limits, tier defaults, and how to read the rate-limit headers.

Each API key has a tier-based rate limit.

Tier defaults

TierDefault rate
default100 requests / minute
starter300 requests / minute
growth1000 requests / minute

Inspect your current tier and limit values with GET /account/key-info.

Headers

Every response includes informational rate-limit headers:

x-request-id: req_abc123
x-ratelimit-limit: 300
x-ratelimit-remaining: 287
x-ratelimit-reset: 41
HeaderMeaning
x-ratelimit-limitTotal requests allowed in the current window.
x-ratelimit-remainingRequests remaining in the current window.
x-ratelimit-resetSeconds until the window resets.

When you hit the limit

A 429 rate_limit_exceeded response means you have hit the limit:

{ "error": { "code": "rate_limit_exceeded", "message": "Rate limit exceeded. Please try again later." } }

Back off and retry after the x-ratelimit-reset window (seconds).

Recommended client behavior

  1. Read x-ratelimit-remaining after every response.
  2. When you receive a 429, back off for at least x-ratelimit-reset seconds before retrying.
  3. For batch jobs, throttle proactively rather than relying on 429s.
  4. Use GET /account/key-info to discover your effective tier on each environment.