Rate Limits
Per-plan rate limits, concurrency limits, and how to handle 429 responses.
Each plan has a maximum number of requests per minute and concurrent requests. These limits apply per organization across all API keys.
Limits by plan
| Plan | Requests / min | Concurrent requests |
|---|---|---|
| Starter | 10 | 3 |
| Growth | 200 | 25 |
| Business | 500 | 50 |
| Enterprise | Custom | Custom |
Rate limit responses
When you exceed your rate limit, you'll receive a 429 response with the code RATE_LIMIT_ERROR:
{
"success": false,
"error": "Rate limit exceeded"
}Check the Retry-After header (if present) to determine how long to wait before retrying.
Best practices
- Use caching. Set
cache: true(the default) to serve repeat requests from cache without hitting rate limits. - Use exponential backoff. When you receive a
429, wait with exponential backoff rather than retrying immediately. - Spread requests over time. Avoid sending bursts of requests — distribute them evenly across the minute.
- Monitor your usage. Track your request rate in the dashboard to stay within limits.
- Upgrade your plan if you consistently hit rate limits. Growth and Business plans offer significantly higher throughput.
Custom rate limits
Enterprise plans include custom rate limits tailored to your workload. Organization admins can also configure per-product rate limit overrides in the dashboard under Settings > Rate Limits.