Using the API Rate Limit Calculator
Enter the quota and its window in seconds, the refill rate, and the maximum bucket capacity. Use limits that apply to the same client, route, or account.
Worked example
A quota of 6,000 requests per minute averages 100 per second. An 80-per-second refill caps sustained traffic at 80, while a full bucket allows a burst of up to 200 with unused quota.
Example inputs
- Request quota per window
- 6000
- Quota window (seconds)
- 60
- Token bucket refill (requests/second)
- 80
- Token bucket capacity (requests)
- 200
- Planned throughput (requests/second)
- 100
Example result
- Sustainable requests per second
- 80
- Quota average requests per second
- 100
- Immediate burst with full bucket and unused quota
- 200
- Planned excess requests per second
- 20
- Spare requests per second
- 0
Method and assumptions
Long-run throughput is capped by both the quota rate and token refill. An immediate burst is capped by the full bucket and unused quota.
Model billable usage
The starting rates are illustrative. For cost estimates, use your provider’s billing units, region and plan, and keep all prices in the same currency.
Common question
Can I send the full burst every second?
A burst uses available tokens immediately. Repeated bursts depend on how many tokens have refilled and how much quota remains in the current window.