Rate limits & quotas
Per-plan limits for the feed, history, scoring, and API keys.
Limits are enforced per plan. A 429 response means you've hit a rate limit or
exhausted a daily quota; a 403 means the endpoint isn't included in your plan.
Plan limits
| Capability | Free | Starter | Pro | Quant | Enterprise |
|---|---|---|---|---|---|
| Realtime feeds / day | 50 | 5,000 | ∞ | ∞ | ∞ |
| Scored feed | — | ✓ | ✓ | ✓ | ✓ |
| Historical lookback | — | 48 hours | 30 days | 1 year | Full |
| Max results / page | — | 50 | 200 | 500 | 1,000 |
| Warren (AI chat) | — | ✓ | ✓ | ✓ | ✓ |
| Scoring API | — | — | 100 / day | 1,000 / day | ∞ |
| API keys | 1 | 3 | 10 | ∞ | ∞ |
| Support | Community | Community | Priority | Priority |
Single source of truth
These values mirror the plan entitlements enforced server-side. Check your
key's current usage and remaining quota any time with
GET /v1/me.
Handling limits gracefully
- Respect
next_cursor. Page through results rather than requesting hugelimitvalues — page size is capped per plan anyway. - Back off on
429. Retry with exponential backoff; daily quotas reset at 00:00 UTC. - Cache
GET /v1/me. Poll it occasionally to track usage, not on every request.
Need higher limits? See pricing or talk to sales about Enterprise.