Model Serving Cost Calculator
Estimate recurring inference cost from your own output-token assumptions.
← Back to Compute College
Compute College
Why Reasoning Models Cost More to Serve
Reasoning models generate long chains of thought before answering, multiplying output tokens — and output tokens drive inference cost.
Interactive calculator
Serving cost calculator
Total API calls served per month.
Average prompt size sent per request, in tokens.
Average response size generated per request, in tokens.
Price charged per million input tokens.
$
Price charged per million output tokens.
$
5,000,000 requests/month → estimated $42,000 in monthly serving cost.
Monthly input token cost$12,000
Monthly output token cost$30,000
Total monthly serving cost$42,000
Cost per 1,000 requests$8.40
Starting values are illustrative defaults you can edit — not live ComputeTape Market benchmark prices. Replace them with a real quote.
Plain-English definition
A reasoning model uses extra compute while answering a question, doing more internal work before it returns the final answer. That work produces additional output tokens, which are usually more expensive to serve than input tokens. The result is that one question can use several times the compute of a standard model. This extra inference-time work is often called test-time compute.
Memory trick: Thinking out loud isn't free — every word of a model's reasoning is an output token, and output tokens are what you pay for.
Why it matters
Serving cost scales with the tokens a model generates, not just the prompt you send in — and reasoning models generate far more of them. That shifts compute demand from one-time training toward recurring inference and changes how buyers plan capacity.
- Serving cost scales with generated tokens, not just the prompt, and reasoning models generate far more of them.
- It shifts demand from one-time training toward recurring inference, changing how buyers plan capacity.
- Longer outputs hold GPU memory longer per request, which lowers how many requests a cluster can run at once.
Simple example
Suppose a standard answer uses 500 output tokens. A reasoning model answers the same question with 5,000 output tokens: 500 for the answer and 4,500 for its additional work. That is 10 times the output. If output tokens dominate the bill, the reasoning query could cost roughly 10 times more to serve.
- Reasoning multiplies the expensive side of the bill: output tokens, not the prompt.
- A 10× jump in output tokens can mean roughly a 10× jump in serving cost for that query.
- Figures here are illustrative calculations, not quoted prices; real ratios vary by model, prompt, and how much reasoning a task triggers.
Example figures are illustrative calculations, not current quoted market prices.
Common mistake
Treating a reasoning model's cost like a standard model's because the prompt is the same size. The prompt (input) is processed in parallel and is comparatively cheap; the cost lives in the output, which is generated one token at a time and grows the memory (KV cache) held per request. A short question can still produce a long, expensive answer.
Practical takeaway
What you can do with this
Estimate reasoning-model cost from expected output length, not prompt size, and decide per task whether the extra reasoning is worth it.
- Buyers: budget on output tokens × output rate; ask providers for the output-token price specifically, and whether reasoning tokens are billed.
- Founders and analysts: separate "standard" from "reasoning" traffic in your unit economics, because blending them hides the real cost driver.
- For example, an illustrative reasoning query of 5,000 output tokens at an illustrative $15 per million output tokens is about $0.075 per query, versus ~$0.0075 for a 500-token standard answer — before input, overhead, or latency-driven capacity costs.
- Route easy tasks to a standard model and reserve reasoning for tasks that measurably benefit; the cheapest reasoning token is the one you did not need to generate.
- Keep provider observations separate from these calculated estimates: a modeled per-query cost guides decisions but is not an observed market price.
Decision check: more reasoning is worth paying for only when the better answer changes the outcome enough to justify the extra tokens.
Compute College
Follow the market after the calculation
Read the ComputeTape Market Brief for weekday AI compute pricing, power, capacity, and infrastructure signals.
Compute College track
Model Benchmarks & AI Compute Economics
Step 25 of 25: Why reasoning models cost more to serve