Rate limits

Current limits

Search and tool calls share one per-organization requests/minute budget. The default is 60; your organization may have a custom limit -- contact support to adjust it.

Response headers

Every response includes rate limit headers so you can track your usage:

HTTP/1.1 200 OK
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 57
X-RateLimit-Reset: 1709000000

• X-RateLimit-Limit -- Maximum requests allowed per window.
• X-RateLimit-Remaining -- Requests remaining in the current window.
• X-RateLimit-Reset -- Unix timestamp when the window resets.

Billing headers

Search responses also carry billing headers so you can track cost per request without a separate call:

HTTP/1.1 200 OK
X-Tokens-Used: 842
X-Query-Cost: 0.001684
X-Billing-Mode: metered
X-Credits-Remaining: 48.316000

• X-Tokens-Used -- Tokens billed for this request.
• X-Query-Cost -- Cost of this request, to 6 decimal places.
• X-Billing-Mode -- How this request was billed (e.g. metered, exempt).
• X-Credits-Remaining -- Organization credit balance after this request. Omitted if your organization has balance visibility hidden.

None of these headers are present when billing is kill-switched for your organization.

Exceeding the limit

When you exceed the rate limit, the API returns 429 Too Many Requests with a Retry-After header:

HTTP/1.1 429 Too Many Requests
Retry-After: 30

{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. Try again in 30 seconds.",
    "request_id": "req_a1b2c3d4"
  }
}

Best practices

• Respect Retry-After -- wait the indicated time before retrying.
• Use exponential backoff -- on repeated 429s, double your wait time between retries.
• Cache results -- avoid redundant requests for the same query.
• Monitor your usage -- check X-RateLimit-Remaining to proactively throttle before hitting limits.