How to use this calculator
- Enter or choose requests per month.
- Enter or choose free requests.
- Enter or choose first price tier covers.
- Enter or choose price per million (first tier).
- Enter or choose price per million above the first tier.
- The monthly cost updates as you type. Use Copy result or Share to keep it.
Method
Billable = Requests − Free; Request cost = min(Billable, Tier) × P1 + max(0, Billable − Tier) × P2; Transfer GB = Requests × Response kB ÷ 1,000,000
- Requests, Free, Tier
- in millions of requests
- P1, P2
- price per million requests
- Response kB
- average response size in kilobytes (1,000 bytes)
Worked example
- Billable: 500 − 1 = 499 million.
- Requests: 300 × 3.50 + 199 × 2.80 = 1,050 + 557.20 = 1,607.20.
- Transfer: 500,000,000 × 2,000 bytes = 1,000 GB × 0.09 = 90. Total 1,697.20.
At these example rates, 500 million requests with 2 kB responses cost about 1,697 a month.
What the result means
Compare the effective price per million with alternatives such as a load balancer or a different gateway type; at high volume the per-request charge can exceed the compute behind it.
Assumptions and limits
- The free allowance is taken from the first tier.
- Every request returns the average response size.
- Caching, WebSocket connection minutes, custom authorisers and the backend’s own costs are not included.
Questions
Do request headers count towards data transfer?
Usually yes. If you know the full response size on the wire, use that instead of the body size.
Why is the effective price lower than the first-tier price?
Requests above the tier are charged at the lower second price, so the average falls as volume rises.