Solved Docs

Rate limits

The rate-limit layers and their headers.

Limits stack in independent layers; hitting any one of them returns 429 with the same shape:

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

{"code":"rate_limited","status":429,"retryable":true,
 "meta":{"policy":"write","limit":60,"window_seconds":60}}

Every response (not just 429s) carries your current standing:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 57
X-RateLimit-Reset: 1790000041

Always honor Retry-After (seconds) before retrying — it's the one header guaranteed to stay on v1. Limits are per account, by call class (read/write/heavy — generation-style calls), not per key: issuing more keys doesn't raise your ceiling. Plan-level daily/monthly quotas (where a product has them) return 503 service_unavailable instead of 429 if they can't be checked — rare, and only for API-key/OAuth traffic, never for the product's own web app.

Next: Errors · Idempotency