Rate Limits
Every API key has daily and per-minute request limits based on subscription tier.
Each key is governed by two independent limits: a per-minute limit that protects against bursts, and a per-day limit that reflects your plan's total allowance. A request only needs to clear both to succeed — hitting either one returns a rate-limit error, even if the other still has room.
Limits by tier
| Tier | Requests / minute | Requests / day | Layers |
|---|---|---|---|
| Starter | 10 | 10,000 | 0, 1, 2 |
| Professional | 100 | 100,000 | 0, 1, 2, 3 |
| Enterprise | Custom | Custom | 0, 1, 2, 3 |
Enterprise limits are set per contract to match your usage pattern — reach out to size a plan.
Exceeding a limit
Requests beyond either limit return 429 Too Many Requests. A Retry-After
header tells you how many seconds to wait before your next request will be accepted.
Checking your usage
Every response includes headers describing where you stand against the per-minute limit:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1699200000
For your daily total, the console's Usage page shows real-time consumption against your plan.
Need more room?
You can raise your limits by moving to a higher tier — see Pricing — or, for enterprise customers, by requesting a custom volume commitment.