Request fees vs bandwidth
Small responses stay request-bound, big JSON or media payloads tip the bill toward egress.
Home / Dev & AI / API Cost Calculator
API & Backend Cost
Estimate what your API costs to run each month. Enter request volume, price per million requests and average response size, and see request fees, bandwidth and how the bill grows with traffic.
Estimated monthly cost
$0
Request fees vs bandwidth
Small responses stay request-bound, big JSON or media payloads tip the bill toward egress.
Cost as traffic grows
What this endpoint costs if monthly volume doubles, 5x or 10x.
Running an API has two recurring costs that scale with traffic: the compute or per request fee for handling each call, and the bandwidth cost of sending responses back over the network. This API cost calculator combines both into a single monthly figure and shows how each part contributes.
The per request price stands in for whatever charges scale with call volume, whether that is a managed gateway fee, serverless invocation cost or your own compute amortised per call. Bandwidth is estimated from your average response size and egress rate, since large JSON or media payloads can quietly dominate a bill.
For 5,000,000 requests a month at $1 per million and 40 KB average responses at $0.09 per GB, request cost is 5 × $1 = $5 and bandwidth is 5,000,000 × 40 ÷ 1,000,000 = 200 GB × $0.09 = $18, for about $23 a month.
Every response you send leaves the provider's network and is billed as egress, per gigabyte. Inbound requests are usually free. Bandwidth is easy to overlook because one response is tiny, but it scales with both traffic and payload size, so a heavy JSON response or an embedded image can outweigh the per-request charge.
20 million requests a month with an 80 KB average response is 20,000,000 × 80 ÷ 1,000,000 = 1,600 GB (1.6 TB). At $0.09 per GB that is about $144 a month in egress. Compressing responses to 20 KB with gzip or Brotli would cut it to about $36.
| Cost component | Typical rate |
|---|---|
| Managed HTTP gateway | $1.00 per million requests |
| Managed REST gateway | $3.50 per million requests |
| Serverless invocation | $0.20 per million requests |
| Egress bandwidth | $0.08 to $0.12 per GB |
| Egress via CDN | $0.02 to $0.05 per GB |
Rates are 2026 estimates and vary by provider and region. Serving responses through a CDN usually lowers egress cost sharply.
Add the per request fees to the bandwidth cost. Multiply requests by your per request rate, then add response size times requests times the egress rate. This tool does both automatically.
For small JSON responses, the per request fee. For large payloads or media, bandwidth. The breakdown chart shows which applies to you.
Serve responses through a CDN, compress payloads, cache common responses, and reduce chatty endpoints that force many small calls.
The per request price can represent your amortised compute. For dedicated always-on servers, use the API hosting cost calculator instead.
They are 2026 planning estimates. Confirm your provider gateway, compute and egress rates for an exact figure.
Data leaving the provider's network, which for an API is mainly the responses you send to clients. Traffic between services in the same region is often free or cheaper, and inbound requests are usually free.
Often. Cacheable responses served from a CDN never reach your origin, and CDN data transfer is usually priced below direct cloud egress. It only helps for responses that can be cached.