Rate Limits
Rate limits keep tenant performance predictable. They are applied per API key over a fixed 60-second window.
Tiers
| Tier | Requests / minute |
|---|---|
standard (default) | 120 |
elevated | 600 |
Your key's tier and current budget are reported by GET /v1/auth/context (rate_limit_tier) and GET /v1/usage (rate_limit.limit_per_minute and rate_limit.remaining_per_minute). Always read the live values rather than hard-coding them.
When you exceed the limit
Requests over the limit return 429 with code: "RATE_LIMITED". Back off and retry after the window resets.
Designing within limits
- Cache reference data and prefer incremental syncs over full-table polling.
- Use webhooks for event-driven updates instead of polling.
- Back off on
429and avoid parallel retry storms after transient failures. - Combine filters (
search,status,module) to fetch less.