Originally published at https://aicoding-guide.com.
The first decision when adopting Claude Code is how you pay for it. There are two paths — a subscription (Pro, Max, Team, Enterprise) or API usage billing — and they differ in how cost works and how limits behave.
The short answer: a subscription if you use it for hours most days, an API key if you drive it from CI and automation. The documentation puts enterprise averages at $150–250 per developer per month, and at that volume a subscription costs less.
Every figure here was checked on the official pages on October 5, 2026. Prices get revised, so confirm current numbers before you commit.
Key point
What you will learn
- Which plans include Claude Code, and which don't
- Subscription and API pricing, and how their limits differ
- The three options when you hit a limit, and which path fits your use
The free plan does not include it
The pricing page's comparison table lists Claude Code as "No" on Free. You need a paid plan or an API key.
The page puts it this way:
Claude Code is included in all paid plans. It shares the same usage limits as the rest of your plan
So there is no separate Claude Code allowance: it draws on the same pool as Claude chat. The shape of the limit is shared too — every plan has limits that reset on a rolling five-hour session window, and paid plans add weekly limits on top.
Glossary
Rolling five-hour window: the window is five hours from when you start using it, not a reset at a fixed clock time. Exhausting it in the morning doesn't cost you the whole day.
Subscription pricing
The figures on the pricing page as of October 5, 2026:
| Plan | Price | Claude Code | Notes |
|---|---|---|---|
| Free | $0 | Not included | Chat on web, desktop and mobile |
| Pro | $17/month with the annual discount ($200 up front), $20 billed monthly | Included | The individual baseline |
| Max | From $100/month | Included | Choose 5x or 20x more usage than Pro |
| Team (Standard) | $20 per seat/month billed annually, $25 monthly | Included | Claude Cowork too. For teams of 2 to 150 |
| Team (Premium) | $100 per seat/month billed annually, $125 monthly | Included | 5x more usage than standard seats |
| Enterprise | $20/seat/month billed annually; usage cost scales with model and task | Included | Team's features plus advanced security and admin controls |
Max comes in 5x and 20x tiers, but the pricing page shows "From $100 Per month" for both, so the exact 20x figure could not be read off it separately. Check the signup flow for the actual number.
On Team and Enterprise, each member's usage draws from a per-seat allowance. Per the documentation, that allowance is shared with Claude chat and Cowork, and its size depends on the seat tier (Standard or Premium).
API usage pricing
With a Console API key you pay per input and output token. From the official pricing table on October 5, 2026, for the models Claude Code uses most:
| Model | Input | Output | Cache reads |
|---|---|---|---|
| Claude Opus 5.5 | $4 / MTok | $20 / MTok | $0.20 / MTok |
| Claude Sonnet 5.5 | $2 / MTok | $10 / MTok | $0.20 / MTok |
| Claude Haiku 4.5 | $1 / MTok | $5 / MTok | $0.10 / MTok |
There is no usage ceiling on the API; you are billed for what you use. The documentation notes that authenticating Claude Code with a Console account creates a workspace called "Claude Code" automatically, giving you centralized cost tracking. You cannot create API keys for that workspace — it exists for Claude Code authentication and usage.
For scale, the documentation reports:
the average cost is around $13 per developer per active day and $150-250 per developer per month, with costs remaining below $30 per active day for 90% of users
At $150–250 a month, Max (from $100) is cheaper. Used a few times a week, the API can come out ahead.
Three options when you hit a limit
The pricing page's FAQ names them:
When you reach a limit, you can wait for it to reset, move to a higher plan, or, on paid plans, turn on usage credits to keep working at standard API rates.
The third one, usage credits, is the practical lever: turn it on and work past your allowance at standard API rates. Manage it by signing in with /login and running /usage-credits. That command is not available with API key authentication.
| Situation | What to do |
|---|---|
| A one-off squeeze | Wait for the reset. /usage shows what is left and when it resets |
| Routinely short | Move up a tier (Pro → Max, Standard seat → Premium seat) |
| Only over before a deadline | Turn on usage credits and set a monthly spend limit |
For reading your usage and cutting it, see Claude Code cost and usage. Keeping context short pays off on every plan — see Managing context in Claude Code.
Choosing by how you work
| How you use it | Pick | Why |
|---|---|---|
| Personal learning, a few times a week | Pro | Claude Code for $17–20 a month |
| Hours a day, professionally | Max | Headroom, and no overage bill |
| A team of 2 to 150 | Team | Per-seat management, and Cowork |
| Audit or security requirements | Enterprise | Advanced security and admin controls |
| Called from CI or automation | An API key | No ceiling, with workspace-level cost tracking |
| Fine-grained org usage control | An API key | Workspace spend limits and per-key breakdowns |
Data handling differs by path
Cost is not the only axis. How your input is treated depends on the contract you use. Before pointing it at work code, read Is your code used to train Claude?
If you are also weighing other tools, Codex vs Claude Code covers that comparison.
Summary
- Claude Code is in every paid plan and absent from Free, and it shares your plan's limits with everything else
- As of October 5, 2026: Pro is $17/month annually or $20 monthly, Max starts at $100/month, Team Standard is $20 per seat annually
- API billing has no ceiling: Opus 5.5 at $4/$20 and Sonnet 5.5 at $2/$10 per MTok
- At a limit you can wait, move up a tier, or spend usage credits at standard API rates
- Around $150–250 a month of use favors a subscription; occasional or automation-led use favors the API
Top comments (0)