Claude Code Pricing: Pro, Max, and API Costs

Claude Code pricing has two billing routes. You can use Claude Code through a paid Claude subscription, or fund it with pay-as-you-go API usage. As of July 19, 2026, Claude Pro costs $20 per month, while Claude Max costs $100 or $200 per month. API usage has no fixed monthly price: input, output, and prompt-cache tokens are billed at the selected model's rate.

Claude Code pricing at a glance #

Claude Code is included in every paid Claude plan. The important detail is that terminal usage does not have a separate pool: Claude Code, Claude web, desktop, and mobile activity share the same plan limits.

Claude Pro: $20 monthly or $200 annually #

Claude Pro is the lowest-cost paid route into Claude Code. The monthly plan is $20. The annual plan is $200 paid up front, which Anthropic presents as roughly $17 per month.

Pro is the sensible starting point when you want Claude Code and also use Claude's chat applications. It is not an unlimited terminal plan. Anthropic describes plan limits as rolling usage windows, with weekly limits layered on paid plans. The number of prompts you receive varies with conversation length, model choice, files, tools, and your usage across other Claude surfaces.

Choose Pro when:

• You code with Claude regularly but not continuously all day.
• You also value Claude on the web or desktop.
• A predictable $20 bill matters more than per-request accounting.
• Waiting for a reset after an occasional limit is acceptable.

Claude Max: $100 or $200 monthly #

Claude Max has two individual tiers. The $100 option provides 5x the usage of Pro per five-hour session. The $200 option provides 20x the usage of Pro per five-hour session. Both include the rest of the Pro feature set and higher output limits.

Max is designed for people who work with Claude throughout the day. It is still governed by usage limits rather than a fixed token allowance. Paying $200 does not create an unlimited API account.

Choose Max when:

• Claude Code is part of several hours of daily development.
• Pro limits interrupt paid work often enough to cost more than the upgrade.
• You want subscription predictability instead of tracking every token.
• You use Claude's other applications enough to value the shared plan.

The honest test is operational: record how often Pro blocks a productive session and how long you wait. Upgrade when the lost work is consistently worth more than the price difference.

Pay-as-you-go Claude Code API pricing #

API-funded Claude Code has no $20, $100, or $200 subscription tier. The cost is calculated from the model's token rates:

request cost =
  input tokens / 1,000,000 × input rate
  + output tokens / 1,000,000 × output rate
  + cache writes and reads at their published rates

Anthropic's Claude Code cost documentation says API usage averages about $13 per developer per active day and $150–$250 per developer per month, with 90% of users staying below $30 per active day. Those figures are planning baselines, not a promise. Repository size, model choice, agent loops, and tool output can move the real number sharply.

API billing is attractive when use is intermittent. A developer who runs two bounded sessions a week may spend less than a monthly plan. An autonomous agent working across several repositories can spend far more.

What happens when a subscription limit is reached #

Anthropic says paid users can wait for the usage window to reset, upgrade, or enable usage credits to continue at standard API rates. This makes the subscription behave like a base allowance with optional metered overflow.

Before enabling overflow billing:

1. Set a monthly spending cap.
2. Check which model Claude Code selects by default.
3. Clear or compact long sessions when the old context is no longer useful.
4. Separate personal experiments from organization-funded work.
5. Review usage after the first full week, not after the first cheap prompt.

Subscription vs API: which is cheaper? #

There is no honest universal break-even calculation because Anthropic does not sell Pro or Max as fixed token bundles. Limits depend on workload behavior, and the subscription pool is shared with other Claude products.

Use this decision rule:

Run both billing routes for one representative week if the difference matters. Record productive sessions completed, blocks, API cost, and time spent managing limits.

Using Claude Code with a compatible API gateway #

Claude Code accepts a custom Anthropic-compatible base URL. A gateway can be useful when you want pay-as-you-go access, a separate hard budget for the coding key, or the ability to select non-Anthropic models without maintaining several provider accounts.

RouterPlex supports the Anthropic Messages route and bills from a prepaid balance. Each API key can carry a hard lifetime budget, so a coding session can be limited to $5, $10, or another explicit amount at the server.

That route is not automatically cheaper than Claude Pro. It is more measurable and more flexible. You pay for the actual model usage, and you can move between Claude, GPT, Gemini, DeepSeek, Kimi, and other supported models through the same balance.

Read the current Claude Code Router and custom gateway setup, or install Claude Code first.

A practical first-month choice #

Start with Pro if you are an individual who wants Claude Code every week and prefers a fixed bill. Start with a small API budget if usage is occasional, automated, or needs strict cost attribution. Move to Max only after Pro limits repeatedly interrupt work.

If multi-model access is the requirement, create a RouterPlex account, add the minimum $5 balance, and give the Claude Code key a hard cap before the first repository session.