Example 1
- 0.4 per 1M
- 2,500,000 requests
1,00 zł
What cost per request at 0.4 per 1M and 2,500,000? 1,00 zł. Price/1e6 × count, not egress.
Cost Per Request Calculator
Type a price per million and a request count. 0.4 and 2,500,000 give 1,00 zł. 1 and 1,000,000 give 1,00 zł. 0.2 and 500,000 give 0,10 zł. This is not transfer.
This is (price per 1M) / 1e6 × request count. Not egress and not a cloud invoice. Transfer sits on bandwidth cost.
Results
Enter data and click Calculate.
How it works
Cost per request in this calculator is the price per million divided by 1e6 and multiplied by the count. 0.4 and 2,500,000 give 1,00 zł. 1 and 1,000,000 give 1,00 zł. 0.2 and 500,000 give 0,10 zł. The calculator does not add egress.
The formula is plain: (price / 1,000,000) × count. 0.4 / 1e6 × 2,500,000 = 1. 1 / 1e6 × 1,000,000 = 1. 0.2 / 1e6 × 500,000 = 0.1. This is not bandwidth, not GB, and not a console bill.
Two fields: price per 1M and request count. Presets only fill numbers. You still press Calculate. The calculator does not know price tiers and does not subtract a free million.
Cloud storage cost next door multiplies GB. Bandwidth cost multiplies egress. Here only the request stays. 1,00 zł at 0.4 and 2,500,000 does not include GB. 0,10 zł at 0.2 and 500,000 does not either.
Type 0.4 and 2500000, then Calculate. The result is 1,00 zł. A comma in 0,4 works. 0.2 and 500000 give 0,10 zł.
0.4 and 2,500,000 give 1,00 zł. 1 and 1,000,000 give 1,00 zł. 0.2 and 500,000 give 0,10 zł. A different price at the same count gives a different cost.
Formula
cost = (price per 1M) / 1e6 × request count
How to use
- Type price 0.4 per million and count 2500000.
- Click Calculate. The result is 1,00 zł.
- 1 and 1000000 give 1,00 zł. 0.2 and 500000 give 0,10 zł.
- This is (price / 1e6) × count, not egress.
- Neighbor cards price storage GB or transfer GB.
0.4 and 2,500,000 give 1,00 zł
Cost = (price / 1e6) × count. 0.4 and 2,500,000 give 1,00 zł. This is not egress.
- Cost
- Price per million times count / 1e6. 0.4 and 2,500,000 give 1,00 zł.
- Request
- Call counts, not GB. 0.2 and 500,000 give 0,10 zł. Not egress.
- Calculator
- Two fields only. 1 and 1,000,000 give 1,00 zł. Not a cloud invoice.
Examples
Example 2
- 1 per 1M
- 1,000,000 requests
1,00 zł
What cost at 1 per 1M and 1,000,000? 1,00 zł.
Example 3
- 0.2 per 1M
- 500,000 requests
0,10 zł
What cost at 0.2 per 1M and 500,000? 0,10 zł.
Related calculators
Common questions
What cost at 0.4 per 1M and 2,500,000 requests?
1,00 zł. (0.4 / 1e6) × 2,500,000. Not egress.
What about 1 per 1M and 1,000,000?
1,00 zł. One million at 1 per million.
What about 0.2 per 1M and 500,000?
0,10 zł. (0.2 / 1e6) × 500,000.
Is this egress or bandwidth?
No. The calculator only multiplies a price per million by a request count.
Is 1,00 zł a cloud invoice?
No. It is a sketch from two fields. A console adds transfer and storage.
Does a free million come off the count?
No. Type the billable count. The calculator does not subtract a free tier.
Does a comma in 0,4 work?
Yes. 0,4 and 0.4 are the same price per million.
How is this different from cloud storage cost?
That card turns 500 GB and 0.02 into 10,00 zł/mies. Here 0.4 and 2,500,000 give 1,00 zł.
Do presets calculate on their own?
No. They only fill numbers. Then Calculate. 0.4 and 2500000 give 1,00 zł.
Knowledge sources
The calculator counts bits, bytes or throughput from your numbers. Below are SI and bit definitions (NIST).
Page updated in 2026.
Unit economics of API requests
API providers (cloud, LLM, SMS, maps) often quote a price per million units (requests, tokens, messages) because a single request costs a tiny fraction of a cent — too small a number to communicate conveniently. This calculator turns that price into three practical figures: the total cost for your volume, the cost of a single request, and the cost per 1,000 requests (a common comparison unit, similar to "cost per mille").
The formula
Total cost = (price per 1M) × (request count / 1,000,000). The cost of a single request is total cost / request count, and the cost per 1,000 is that result times 1,000. For very small numbers, the calculator shows the result in exponential notation to avoid losing precision.
Tiered pricing
Many providers use tiered pricing — e.g. the first million requests free, subsequent millions at a lower per-unit price for scale. This calculator computes at a single, fixed price per 1M; for tiered pricing, compute each tier separately or use a blended rate across your total volume.
Estimating a monthly budget
To estimate monthly cost, multiply your average daily traffic by about 30 days and enter that as the request count. It is worth adding margin for traffic spikes (e.g. +20-30%), especially if the service has seasonality or planned marketing campaigns that increase traffic.
Caching and batching vs cost
Caching and batching can reduce cost per request by lowering the number of paid calls or the size of payloads billed separately.
- Cache frequent reads (CDN, Redis, ETag) — same result without another billable call.
- Batch writes / queries (bulk APIs) instead of N single requests.
- Avoid redundant polling and repeated identical calls in UI loops.
Examples
- $0.40 per 1M requests, 2,500,000 requests → total cost $1.00, cost per request $0.0000004, cost per 1,000 requests $0.0004.
- $2.00 per 1M requests (e.g. an LLM API), 50,000 requests → total cost $0.10, cost per request $0.000002.
- $1.00 per 1M requests, 1,000,000 requests → total cost $1.00, cost per 1,000 requests $0.001.