Every model we track charges more for the tokens it writes than for the tokens it reads, from 2× to 8.3× as much. That gap, more than the headline input price, decides what many workloads cost. This page lists the ratio for each model, shows how it changes which model is cheapest, and covers the ways to keep output under control.
The ratio for every model
| Model | Input $/M | Output $/M | Output ÷ input | Blended, 10:1 mix | Blended, 1:1 mix |
|---|---|---|---|---|---|
| xAI Grok Build 0.1 | $1 | $2 | 2× | $1.09 | $1.50 |
| xAI Grok 4.7 | $2 | $6 | 3× | $2.36 | $4.00 |
| DeepSeek V4 Pro | $1.32 | $3.96 | 3× | $1.56 | $2.64 |
| DeepSeek V4.1 Flash | $0.3 | $1.2 | 4× | $0.382 | $0.750 |
| Anthropic Fable 5.1 | $10 | $50 | 5× | $13.64 | $30.00 |
| Anthropic Opus 5.5 | $4 | $20 | 5× | $5.45 | $12.00 |
| Anthropic Sonnet 5.5 | $2 | $10 | 5× | $2.73 | $6.00 |
| Anthropic Haiku 5.5 | $0.1 | $0.5 | 5× | $0.136 | $0.300 |
| OpenAI GPT-6 Astra | $10 | $50 | 5× | $13.64 | $30.00 |
| OpenAI GPT-6.1 Sol | $2 | $10 | 5× | $2.73 | $6.00 |
| OpenAI GPT-6 Luna | $0.1 | $0.5 | 5× | $0.136 | $0.300 |
| OpenAI GPT-5.6 Sol | $4 | $20 | 5× | $5.45 | $12.00 |
| Google Gemini 4 Argon | $2 | $10 | 5× | $2.73 | $6.00 |
| Google Gemini 3.8 Flash | $0.75 | $3.75 | 5× | $1.02 | $2.25 |
| OpenAI GPT-5.5 Pro | $30 | $180 | 6× | $43.64 | $105 |
| Google Gemini 3.1 Pro | $2 | $12 | 6× | $2.91 | $7.00 |
| Google Gemini 3.1 Flash-Lite | $0.25 | $1.5 | 6× | $0.364 | $0.875 |
| OpenAI GPT-5 nano | $0.05 | $0.4 | 8× | $0.082 | $0.225 |
| Google Gemini 3.5 Flash-Lite | $0.3 | $2.5 | 8.3× | $0.500 | $1.40 |
5× is the most common ratio (10 of 19 models), and it is the ratio Anthropic uses across its current models. The outliers are worth knowing: xAI Grok Build 0.1 charges only 2×, while Google Gemini 3.5 Flash-Lite charges 8.3×. The blended columns give one effective price per million tokens for a given mix: (input price × input share + output price × output share). A 10:1 mix is typical of chat with history, summarisation and RAG; 1:1 is closer to rewriting or translation.
Why output is priced higher
Providers do not publish their cost breakdowns, so treat this as the general technical explanation rather than any provider’s statement: a model can process all the tokens of a prompt in parallel, but it must generate its answer one token at a time, each step depending on the last. Generation keeps the hardware busy for longer per token, and the price reflects it. What the providers do document is what counts as output. Google’s Gemini price table labels the output price “including thinking tokens”, and xAI lists reasoning tokens (“internal thinking and planning”) among the token types billed for a request. A reasoning model can therefore bill far more output than the text you see.
The mix changes which model is cheaper
Compare xAI Grok Build 0.1 ($1 in, $2 out) with Google Gemini 3.8 Flash ($0.75 in, $3.75 out) on two jobs of similar size:
- Read-heavy (100M input, 10M output a month, e.g. summarising documents): Grok Build 0.1 costs $120, Gemini 3.8 Flash $113.
- Write-heavy (10M input, 40M output, e.g. drafting long articles from short briefs): Grok Build 0.1 costs $90.00, Gemini 3.8 Flash $158.
The cheaper model swaps places between the two jobs. Sorting a price table by input price alone would have picked the wrong one for one of them. The comparison table sorts by either column; the calculator takes your real input and output counts.
Where the asymmetry bites
- Long-form generation (articles, code files, reports): output dominates, so the output price is the number to shop on.
- Reasoning and agent workloads: hidden thinking tokens and the model’s own tool calls are output, and agents produce output at every step.
- Chat: per turn, input usually dominates because the history is resent, but replies that are three times longer than needed still triple the output line.
- Classification and extraction: the cheapest case. A one-word label or a small JSON object is a handful of output tokens, so input price and caching matter most (see caching and batch discounts).
How to keep output costs down
- Set a maximum output length on every request. Every major API has a max-tokens style parameter; it caps the worst case.
- Ask for the format you need. “Answer in at most three sentences” or a fixed JSON schema produces fewer tokens than open prose.
- Choose the reasoning level deliberately. Where a model lets you switch thinking off or lower its effort, simple tasks rarely need the maximum.
- Do not regenerate what you can reuse. Ask for a diff or the changed section instead of a full rewritten document.
- Batch what can wait. Batch discounts apply to output tokens too: 50% at Anthropic, OpenAI and Google, 20% on the discounted Grok models.
Common misreadings
- “Model X is cheaper because its input price is lower.” Only if your workload is input-heavy. Check both columns.
- “Cached input makes the bill tiny.” Caching only discounts input; output stays at full price, so output-heavy apps save little from it.
- “The visible answer is the output.” Not on reasoning models: the thinking tokens are billed too, and you may not see them.