Case 1
- 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 valuesChange any value to update the result.
13.750USD
Monthly token cost: 13.750 USDEvery rate here was read on the provider's own pricing page on 2026-09-03 and is a snapshot, not a promise: on each model page the two prices arrive prefilled in the form and you overwrite them with today's figure. The spread is wide — gpt-5.5-pro charges $180 per million output tokens, GLM-5.3-Flash charges $0.25. 47 models have their own page; seven are retired, limited or carry no printed rate and get a row only.
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 | Monthly token cost (USD) |
|---|---|
| 10 | 6.250 |
| 20 | 12.500 |
| 22Your value | 13.750 |
| 30 | 18.750 |
| 40 | 25.000 |
Every rate in this table was read on 2026-09-03 on the pricing page of the provider that charges it — never from a third-party comparison. The last column names the page and any condition attached to the number. The rate is a snapshot, not a promise, and this family carries prices only because it hands them straight into an input field. On each model page both prices arrive prefilled and stay editable, and the calculator uses whatever stands in the field. The calculator underneath deliberately holds no price list, for the reason set out in its own file: a page with a rate baked into it goes wrong quietly, keeping a confident number long after the number stopped being true. A prefilled field with a check date next to it is the one shape a price can take on a statically built page without doing that. All eight providers quote per million tokens and say so on the page — Anthropic writes "MTok = Million tokens", Moonshot writes "1M = 1,000,000" — so nothing here needed converting. Some providers quote per 1,000 tokens instead, Amazon Bedrock among them; multiply such a rate by 1,000 before you enter it. Four things these two numbers do not cover. Prompt caching: a cache read typically costs a tenth of the input rate and a cache write 1.25 to 2 times it, so a heavily cached agent runs well under this figure. Batch processing: asynchronous requests are commonly half price. Server-side tools: web search at $10 per 1,000 searches, container and session runtime by the hour, all billed apart from tokens. And tool definitions, which add several hundred to several thousand input tokens to every single request. Same rate does not mean same bill. Claude models from 4.7 on use a newer tokenizer that produces about 30% more tokens for the same text, so a given file costs more at an unchanged per-token price. Gemini 3.6, 3.7 and 3.8 Flash are on a promotional rate that doubles on 2027-01-01, and GLM-5.3-Flash on a launch discount that doubles on 2026-09-09, six days after this check. Gemini Pro and every Grok model step up above 200k tokens of context. DeepSeek's listed rate is the peak-hour rate and halves off-peak. Kimi K3's input rate is the cache-miss rate. Seven models have a row and no page: four are marked retired by Anthropic and priced only on Bedrock and Google Cloud, two are limited availability, and Kimi K2.7 Code has a documentation page that names the model and prints no rate. Guessing that one number is exactly the failure this family exists to avoid. Amazon Bedrock and Cohere are missing for the same reason. Bedrock's tables did not render a Nova figure on the check date, and Cohere prints rates only for its legacy models. No source, no row. The order is by output price, highest first: output is charged at four to five times the input rate on almost every list here, so it is what decides a coding bill.
| Model | Provider | Input / 1M tokens | Output / 1M tokens | Source, checked 2026-09-03 |
|---|---|---|---|---|
| Claude Opus 4.1 | Anthropic | $15.00 | $75.00 | platform.claude.com/docs · Model pricing · retired, priced only on Bedrock and Google Cloud |
| Claude Opus 4 | Anthropic | $15.00 | $75.00 | platform.claude.com/docs · Model pricing · retired, priced only on Bedrock and Google Cloud |
| Claude Mythos 5.1 | Anthropic | $10.00 | $50.00 | platform.claude.com/docs · Model pricing · limited availability |
| Claude Mythos 5 | Anthropic | $10.00 | $50.00 | platform.claude.com/docs · Model pricing · limited availability |
| Claude Sonnet 4 | Anthropic | $3.00 | $15.00 | platform.claude.com/docs · Model pricing · retired, priced only on Bedrock and Google Cloud |
| Claude Haiku 3.5 | Anthropic | $0.80 | $4.00 | platform.claude.com/docs · Model pricing · retired, priced only on Bedrock and Google Cloud |
| Kimi K2.7 Code | Moonshot | no rate | no rate | platform.kimi.ai/docs/pricing · model page names it and prints no rate |
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 50,000 tokens of context and writes 15,000 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.
MisconceptionOne price covers the whole request.
CorrectionInput and output are separate line items at different rates. You have to multiply twice and add.
MisconceptionPrices are quoted per thousand tokens, so divide by 1000.
CorrectionProviders quote both ways. This page uses price per million; a per-thousand rate becomes a per-million rate by multiplying it by 1000.
MisconceptionThe token count is roughly the word count.
CorrectionA 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.
Diese Seite gibt es auch auf Deutsch.
Zu Deutsch wechseln