Errors and rate limits
Rate limits
Section titled “Rate limits”Limits apply at subscription level (shared by all API keys of that subscription). They are not multiplied by key count.
| Plan | Requests per minute |
|---|---|
| Starter | 10 |
| Pro | 60 |
| Business | 300 |
A custom RPM on the subscription may override the plan default when configured for Business customers.
There is no monthly request quota — usage is gated by RPM (and normal abuse protection).
Successful responses include:
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-Reset(Unix timestamp, seconds)
429 response
Section titled “429 response”HTTP/1.1 429 Too Many RequestsX-RateLimit-Limit: 10X-RateLimit-Remaining: 0X-RateLimit-Reset: 1710000060Retry-After: 42
{ "code": "RATE_LIMIT_EXCEEDED", "message": "Rate limit exceeded for this subscription."}Back off using Retry-After (seconds) when present.
Billing and 402
Section titled “Billing and 402”While a subscription is past due, access continues for a 7-day grace period. After grace ends (or if billing is otherwise blocked), requests return 402 BILLING_REQUIRED until the subscription is in good standing again.
Common error codes
Section titled “Common error codes”| HTTP | code | When |
|---|---|---|
| 400 | validation / bad request | Invalid query or path parameters |
| 401 | UNAUTHORIZED | Missing or invalid X-API-Key |
| 402 | BILLING_REQUIRED | Billing state blocks access |
| 403 | INSUFFICIENT_CAPABILITY | Endpoint needs a higher capability tier |
| 429 | RATE_LIMIT_EXCEEDED | Subscription RPM exceeded |
Error bodies follow a consistent JSON shape with at least code and message. Full schemas are in the OpenAPI reference.