- Input tokens per session
- 50000
- Output tokens per session
- 15000
- Price per million input tokens
- 5
- Price per million output tokens
- 25
- Sessions per month
- 22
13.750USD
Open with these values13.750USD
Result: 13.750 USDToken pricing is a straight multiplication: tokens divided by a million, times the price per million, input and output priced separately. A session of 50000 input and 15000 output tokens at 5 and 25 per million costs 0.625 — twenty-two of those a month come to 13.75.
Held fixed: Input tokens per session 50,000, Output tokens per session 15,000, Price per million input tokens 5.0000, Price per million output tokens 25.0000.
| Sessions per month | Result (USD) |
|---|---|
| 10 | 6.250 |
| 20 | 12.500 |
| 22Your value | 13.750 |
| 30 | 18.750 |
| 40 | 25.000 |
13.750USD
Open with these values36.000USD
Open with these values2.750USD
Open with these valuescost = sessions × (in ÷ 1M × price_in + out ÷ 1M × price_out)
Language models are billed by the token, and the arithmetic is simpler than the pricing pages make it look. Divide the tokens by a million, multiply by the price per million, and do it twice — once for what you send and once for what comes back, because output is charged at a higher rate than input. A session that reads 50000 tokens of context and writes 15000 tokens of code costs 0.25 for the input and 0.375 for the output: 0.625 in total. Run twenty-two of those in a working month and the bill is 13.75. This page deliberately has no price list. Provider rates move, and a page with a rate baked into it goes wrong quietly — it keeps showing a confident number long after the number stopped being true. So the price per million is a field you fill in from whatever your provider publishes today, and the page does the multiplication. That also makes it work for any provider and any model, including ones that did not exist when this page was written. Two things the figure leaves out. Caching changes the input price — a cache read is typically billed at a fraction of the base rate, a cache write at a premium — so a heavily cached agent costs less than this suggests. And server-side extras such as web searches or container time are billed separately from tokens altogether.
Provider rates change, and a page that hard-codes one is wrong three months later while still looking right. The price per million is an input field; take today's figure from your provider's own pricing page.
The 5 and 25 in the form are the numbers used in the worked example this page is checked against. They are there so the starting view shows a calculation you can verify, not as a claim about what anything costs today.
Every published example prices output above input, often five times higher. A workload that reads a lot and writes little is far cheaper per token than one that generates long files.
Cache reads are usually billed at a fraction of the input rate and cache writes at a premium, so a cached agent costs less than this. Web searches and container time are billed separately from tokens.
One price covers the whole request.
Input and output are separate line items at different rates. You have to multiply twice and add.
Prices are quoted per thousand tokens, so divide by 1000.
Providers quote both ways. This page uses price per million; a per-thousand rate becomes a per-million rate by multiplying it by 1000.
The token count is roughly the word count.
A token is closer to four characters, so a token count runs well above the word count. Use your provider's token counting endpoint rather than guessing.
| Published example | Input | Output | Cost |
|---|---|---|---|
| One coding session, 5 and 25 per million | 50000 × 5 ÷ 1M = 0.250 | 15000 × 25 ÷ 1M = 0.375 | 0.625 |
| Vendor example, 12.50 both ways | 10000 × 12.50 ÷ 1M = 0.125 | 2000 × 12.50 ÷ 1M = 0.025 | 0.150 |
| Vendor example, 8 and 24 | 11000 × 8 ÷ 1M = 0.088 | 4000 × 24 ÷ 1M = 0.096 | 0.184 |
| Vendor example, 1.50 and 2 | 6000 × 1.50 ÷ 1M = 0.009 | 2000 × 2 ÷ 1M = 0.004 | 0.013 |
| 10000 short conversations at 1 per million | 3700 × 1 ÷ 1M × 10000 | none priced | 37.000 |
Tokens divided by a million, times the price per million, done separately for input and output and then added. For 50000 input tokens at 5 per million and 15000 output tokens at 25 per million that is 0.25 plus 0.375, so 0.625.
Because provider rates change and this page would otherwise go stale without any visible sign of it. Entering the current rate keeps the result correct and makes the calculator work for every provider and model.
Multiply it by 1000. A rate of 0.008 per thousand input tokens is 8 per million, and 0.024 per thousand output tokens is 24 per million.
Generating tokens costs far more compute than reading them, and every published price list reflects that. Output rates are commonly four to five times the input rate for the same model.
No. Cache reads are typically billed at a fraction of the base input rate and cache writes at a premium. If your workload caches heavily, price the cached portion separately at its own rate.
It varies enormously with the size of the context you load and the length of what gets written. Measure your own with your provider's token counting endpoint instead of trusting a rule of thumb.
Information, not professional advice.
Diese Seite gibt es auch auf Deutsch.
Zu Deutsch wechseln