Claude Code billing

Claude Code Cost Calculator

Estimate what your Claude Code workflow could cost if it runs through API billing, then compare that exposure with subscription plan pressure.

API estimate $0.00
Token volume 0M
Checked May 20, 2026

What this calculator answers

It answers a narrow question: if a Claude Code-like workload were charged by API tokens, what rough monthly bill would it create? That helps you decide whether to stay on a subscription, upgrade a plan, or intentionally use API billing with a budget cap.

What it cannot know

It cannot see your account, hidden plan limits, prompt compression, real cache hit rate, or the exact mix of tool calls. Use it for planning, then verify real usage in Claude settings, Claude Code messages, and API billing dashboards.

How Claude Code cost actually happens

Claude Code users usually search for a cost calculator after seeing one of two problems: a subscription limit message, or an unexpectedly large API bill. Those are different situations. Anthropic's Claude Code help article says metering is determined by how you sign in. A plan or Enterprise login uses included usage and shows a reset window when you run out. An API key uses pay-as-you-go billing, and there may be no hard stop unless your Console or cloud account has budget limits.

This calculator focuses on the second case: estimating what your coding sessions would cost if they were charged as API token usage. It also shows subscription pressure because the same behavior that creates high API spend usually burns through plan usage windows too: long conversations, large project context, pasted logs, repeated tool calls, and leaving an expensive model active after the hard part is done.

Sign-in mode What usage means What to watch Best control
Claude subscription or Enterprise login Included usage pool with reset windows. Limit messages, model availability, and context indicator. Use `/clear`, `/compact`, and model switching.
Anthropic Console API key Pay-as-you-go token billing. `/cost`, Console usage, and monthly budget settings. Set spend limits before long loops.
Bedrock, Vertex, or Foundry API key Cloud-provider token billing. Cloud billing dashboard plus provider-specific regional pricing. Use cloud budget alerts and project separation.

Model assumptions used here

The model dropdown uses current public Anthropic API prices checked on May 20, 2026: Claude Sonnet 4.6/4.5 at $3 input, $0.30 cache read, and $15 output per million tokens; Claude Opus 4.7/4.6 at $5 input, $0.50 cache read, and $25 output per million tokens; and Claude Haiku 4.5 at $1 input, $0.10 cache read, and $5 output per million tokens. The page models cache hits at the cache-read price, not cache-write setup cost, because it is estimating a steady coding workflow.

That simplification is intentional. A real Claude Code session may include tool definitions, file excerpts, command output, error messages, and repeated conversation history. Anthropic's pricing page also lists cache writes, data residency multipliers, batch discounts, and tool-use costs. Those can matter for production API systems, but for an individual Claude Code workflow the bigger first-order variable is whether you are carrying too much context across unrelated tasks.

Practical ways to lower Claude Code spend

  • Use `/clear` whenever the next task would make sense in a fresh terminal. This removes old chat history while leaving project files and memory available.
  • Use `/compact` when you are mid-task and need to preserve the core context without carrying every previous turn.
  • Use Sonnet for most implementation, tests, and known-bug work. Reserve Opus for hard planning, architectural decisions, and debugging that cheaper models fail.
  • Keep `CLAUDE.md` short and current. It is loaded into context repeatedly, so stale or broad instructions create both cost and quality problems.
  • Point Claude at file paths instead of pasting whole files or long logs. Trim stack traces to the relevant lines.
  • When using API billing, check `/cost` during long sessions and add Console or cloud-provider budget alerts before starting agent loops.

FAQ

Why does the calculator ask whether `ANTHROPIC_API_KEY` is set?

Because Claude Code usage can be metered differently depending on sign-in. If an API key is active, a workflow may create pay-as-you-go token charges instead of only consuming subscription usage. The checkbox is a reminder to verify your local setup before a heavy session.

Does Opus always cost more than Sonnet in Claude Code?

In API pricing, Opus is more expensive per token than Sonnet. In subscription usage windows, Anthropic describes Opus as using meaningfully more quota. The practical pattern is to plan with Opus only when needed, then execute routine changes with Sonnet.

Can this calculate my exact Pro or Max limit?

No. Claude Code plan limits are not published as a simple token bucket. This page estimates pressure from session count and session size so you can compare patterns, but the source of truth remains the limit/reset messages and account-specific model availability.

Checklist before a heavy session

  • Run without ANTHROPIC_API_KEY if you want subscription usage.
  • Set API budget alerts before any long-running agent loop.
  • Use /clear between unrelated tasks to reduce context carryover.
  • Use smaller models for edits that do not need frontier reasoning.

Sources

AI Code Limits is independent and is not affiliated with Anthropic, Claude, or Claude Code.