How much Claude Code costs per month — and what actually drives the number
Claude Code has no subscription fee on top of the API. Your bill is token spend, and it is driven by one thing almost nobody tracks: how much context each turn resends. Understand that and the bill becomes predictable.
The three numbers that decide your bill
- Context size per turn. Claude Code sends the accumulated conversation on every request. This is the dominant factor, not message count.
- Turns per session. An agent loop that runs 40 tool calls is 40 billed requests, each carrying the context.
- Model rate. The per-million-token input and output price of the model you selected.
Current rates
| Model | Gateway rate in / out per 1M tokens | Official list in / out per 1M tokens | Diff |
|---|---|---|---|
| claude-haiku-4-5 | $0.5 / $2.5 | $1 / $5 | 50% |
| claude-sonnet-5 | $1 / $5 | $2 / $10 | 50% |
| claude-opus-5 | $2.5 / $12.5 | $5 / $25 | 50% |
Rates checked 2026-09-16. Gateway rates move with upstream promotions — verify the current number in your dashboard before committing to a budget.
What that means in practice
Take a realistic working day: 15 sessions, each with about 30 turns, averaging 40k tokens of context per turn. That is roughly 18M input tokens a day. At the rates above the difference between model classes is not marginal — it is the difference between a coffee and a dinner, every single day.
Use the Claude Code cost calculator with your own session length rather than trusting a generic figure. Two developers can differ by 10x on the same model purely because of how they manage context.
Six ways to cut the bill without slowing down
| Lever | What it does | Typical effect |
|---|---|---|
| Compact long threads | Runs /compact to summarise history instead of resending it | Largest single saving on long sessions |
| Start fresh per task | One thread per task instead of one thread per day | High — avoids unrelated context being resent |
| Model per task | Cheap model for mechanical edits, expensive one for hard reasoning | High |
| Scope the repo | Keep unrelated large files out of context | Medium |
| Cap output length | Limit long explanations where you only need the diff | Medium — output is the expensive side |
| Batch mechanical work | One well-specified request instead of ten exploratory ones | Medium |
See the full walkthrough in how to reduce Claude API cost.
How to verify your own number
Do not estimate from the CLI. Read the usage log on the provider dashboard, filter to a single day, and divide by the number of sessions you ran. That gives a per-session figure you can actually act on — and it is the only number worth optimising against.
Where the rate comes from
The rate you pay is whatever your provider charges per token — it is not fixed by the tool. Comparing that per-token number across models is the highest-leverage check you can do, and it takes a minute in the cost calculator.
FAQ
How much does Claude Code cost per month?
It is pure token spend — there is no seat fee on top. A light user (a few sessions a day, short threads) lands in the low tens of dollars. A heavy user running long agent sessions every working day can reach several hundred. The multiplier is not the number of messages, it is how much context each turn resends.
Why does the cost grow so fast in long sessions?
Every turn sends the accumulated conversation back to the model. Input is billed per token each time, so a 200k-token context resent 50 times costs the same as sending 10M input tokens, even though you typed a few hundred words.
Does a cheaper model actually work for Claude Code?
For mechanical tasks — renaming, formatting, running tests, applying a described change — yes, and it is the single biggest saving available. Reserve the expensive model for the parts where a wrong answer costs you an hour.
How do I find out what I am actually spending?
Check the usage log on your provider dashboard rather than inferring it from the CLI. For a forward-looking estimate, use the Claude Code cost calculator with your real session length.
Is there a way to cap the bill?
Set a top-up ceiling on the account and keep conversations short. There is no per-request hard cap inside the CLI itself, so the account-level limit is the reliable brake.