Rate limits
Every plan has a monthly quota, a sustained rate, and a burst capacity. Limits are enforced by AWS API Gateway usage plans tied to your x-api-key. Hitting either limiter returns 429 Too Many Requests.
◆ Plan limits
| Plan | Monthly quota | Rate | Burst |
|---|---|---|---|
| Free | 3,000 / mo | 1 req/sec | 5 |
| Standard | 30,000 / mo | 3 req/sec | 15 |
| Pro | 300,000 / mo | 10 req/sec | 50 |
| Elite | 3,000,000 / mo | 25 req/sec | 150 |
| Enterprise | Custom | Custom | Custom |
Need a higher ceiling? Upgrade or contact sales for Enterprise.
Seats are workspace access (Free: 1 seat, Standard: 3 seats, Pro: 5 seats, Elite: 10 seats, Enterprise: Custom). Adding teammates does not multiply API keys, quota, rate, or burst limits.
◆ How enforcement works
- Each API key is synced to an AWS API Gateway key and attached to your tier's usage plan when created in the dashboard.
- Send the key in the
x-api-keyheader on every request. The gateway applies throttle (rate + burst) and monthly quota before the request reaches the API. - Your dashboard quota gauge and 30-day chart read live counters updated on each API call.
- Poll programmatically with
GET /v2/usage(see Usage).
◆ Hitting the limit
- Honor Retry-After. 429 responses may include seconds to wait before the next attempt.
- Cache aggressively. The catalog moves daily, not per-second. A 5-minute cache on a busy endpoint shaves 99% of calls without affecting freshness.
- Batch with filters. One
GET /v2/events?coins=bitcoin,ethereum,solanabeats three single-coin requests. - Subscribe to webhooks (Elite+). Push delivery replaces polling. Manage endpoints in the dashboard; see Webhooks.
◆ Burst limits
Burst caps short-term spikes separately from the monthly quota. Bursts above the cap return 429 immediately. If you hit the burst limit, waiting 1s is usually enough to send the next call.
◆ Per-request timeout
Every request has a hard 30s server-side timeout. Slow responses return 500; reduce the page size (limit) or narrow filters before retrying.