Rate limits and quotas
Two separate limits. The burst limit caps requests per
60-second window and returns
RATE_LIMIT_EXCEEDED. The monthly quota
caps successful conversions per UTC calendar month and returns
QUOTA_EXCEEDED.
Plans
Free
100 req / 60 s
10,000 conversions / month
Batch max 100 items
Developer
500 req / 60 s
250,000 conversions / month
Batch max 100 items
Pro
2,000 req / 60 s
2,000,000 conversions / month
Batch max 100 items
Business
5,000 req / 60 s
10,000,000 conversions / month
Batch max 100 items
What counts
| Operation | Cost |
|---|---|
| Any authenticated HTTP request (convert, batch, parse, normalize, currency, substances, unit price) | 1 request (burst limit) |
Successful convert, parse with to, normalize, currency convert, or substance convert | 1 conversion (monthly quota) |
| Successful unit-price comparison | 1 conversion per offer |
| Listing currency rates or substances | Not counted against the monthly quota |
| Batch item that succeeds | 1 conversion each; a batch that does not fit in the remaining quota is rejected whole |
Failed or invalid conversion, parse without to | Not counted |
| Public discovery (categories, units, health, OpenAPI) and latest currency rates | No key needed; 120 requests / 60 s per IP address |
When the burst limit is exceeded, the API returns
RATE_LIMIT_EXCEEDED with
Retry-After: 60. When the monthly quota
is used, it returns QUOTA_EXCEEDED
(HTTP 429, no Retry-After) until the
quota resets at 00:00 UTC on the first of the month or you upgrade. Your
usage page shows usage for the month.