Developers
Rate limits & quotas
Two controls apply: a monthly included quota (by plan) and a per-key request rate limit.
Monthly quota
Each plan includes a monthly quota of billable requests. Usage beyond the quota is billed at the plan’s overage rate — see pricing. Usage is metered per request.
Per-key rate limit
Each API key is rate-limited to protect the platform. When you exceed the limit, the API returns 429 Too Many Requests with a Retry-After header indicating how long to wait.
Handling 429
- Respect
Retry-After; retry after the indicated delay. - Use exponential backoff with jitter for bursts.
- Cache responses where possible (tiles are edge-cached; cache geocoding results you reuse).
- For sustained higher throughput, request a higher limit via sales.
Exact limits depend on your plan and are confirmed against the billing configuration; this page describes the mechanism, not a fixed number.