Get startedRate limits & access
Rate limits & access
Access is by API key during the private beta. Two rate limits apply to every key, and rate-limit headers on every response tell you exactly where you stand.
Access
The API is in private beta. There is no public pricing yet; a single key unlocks all v1 endpoints, subject to the limits below.
Access
Private beta
Includes
All v1 endpoints
Daily quota
1,000 requests / day
Burst limit
120 requests / min
Two limits, both enforced. Requests are capped by a rolling per-minute burst (120/min) and a daily quota (1,000/day). Hit either and you'll get a 429 until that window resets.
Rate-limit headers
Every response carries your current standing, so you can throttle proactively rather than waiting to be rejected. The bare RateLimit-* headers describe the most constrained window; the per-window variants report the minute and day budgets explicitly.
| Header | Description |
|---|---|
| RateLimit-Limit | Request ceiling for the most-constrained window. |
| RateLimit-Remaining | Requests left in that window. |
| RateLimit-Reset | Seconds until that window resets. |
| RateLimit-*-Minute | Limit / Remaining / Reset for the per-minute burst window. |
| RateLimit-*-Day | Limit / Remaining / Reset for the daily quota window. |
| Retry-After | On a 429 only — seconds to wait before retrying. |
Response headers
HTTP/1.1 200 OK
Content-Type: application/json
RateLimit-Limit: 120
RateLimit-Remaining: 117
RateLimit-Reset: 43
RateLimit-Limit-Minute: 120
RateLimit-Remaining-Minute: 117
RateLimit-Reset-Minute: 43
RateLimit-Limit-Day: 1000
RateLimit-Remaining-Day: 863
RateLimit-Reset-Day: 51840When you hit a limit
A throttled request returns 429 with a RATE_LIMITED error and a Retry-After header. Back off for that many seconds, then retry — ideally with exponential backoff and jitter.
429 Too Many Requests
{
"error": {
"code": "RATE_LIMITED",
"message": "Rate limit exceeded"
}
}