Claude Code pricing: plans, API costs, and how to lower your bill

If you are developing software professionally in 2026, there is a good chance you have used Claude Code. There’s an even better chance that your token consumption has increased at least 3x in the past year. With that, developers globally are now paying close attention to the cost of said token usage. Claude Code costs depend on how a developer accesses it. Pro, Max, and Team subscriptions include usage within plan limits. API users pay by token, while Enterprise combines a seat price with usage-based charges.

For API and Enterprise deployments, the selected model has a direct effect on cost. While Anthropic models are the default, Fireworks-hosted open-weight models such as GLM 5.2, Kimi K2.7 Code, and MiniMax M3 are also accessible, and have lower per-token rates than Fable, Opus 4.8, or Sonnet 5. Many open-weight models have also narrowed the gap on agentic coding evaluations, although benchmark scores do not guarantee equivalent results on a particular repository.

Claude Code provides the coding interface and agent loop. Its configured model endpoint supplies the model behavior behind that interface. Fireworks supports two ways to test a lower-cost model layer:

• •Keep Claude Code: use FireConnect to route supported Claude Code model calls through Fireworks’ Anthropic-compatible endpoint. The CLI remains familiar, but model behavior, tool support, latency, and output quality can change.
• •Use an OpenAI-compatible coding harness: connect OpenCode, Cursor, Cline, Aider, or another compatible harness to Fireworks’ OpenAI-compatible API.

Evaluate either path with real repository tasks before standardizing. Compare completion rate, model spend, latency, retries, and human repair time rather than relying on token rates alone.

Anthropic offers subscription, usage-credit, and API-based ways to pay for Claude Code. The relevant cost model depends on the account and authentication method.

For Pro and Max subscribers, usage is included within plan limits, so the dollar estimate shown by /usage is not a direct billing figure. The command still shows plan bars, activity statistics, and a breakdown of token usage. Subscription users who enable additional usage credits can incur charges after reaching their included allowance. API and Enterprise usage is priced according to model consumption.

Anthropic’s Claude Code cost documentation reports an enterprise average of about $13 per active developer per day, or $150 to $250 per month. However, actual spend varies with the model, codebase size, context length, tool calls, subagents, automation, and parallel sessions.

Claude API pricing charges separately for base input, cache writes, cache hits, and output. Current list prices per million tokens are:

Prompt caching charges 1.25 times the base input rate for a five-minute cache write and twice the base rate for a one-hour write. Reading cached content costs 10% of the base input rate. According to Anthropic, caching pays off after one cache read with the five-minute duration or after two reads with the one-hour duration.

Anthropic's Batch API discounts input and output tokens by 50% for eligible asynchronous workloads. Prompt-caching charges can still apply to batch requests, so teams should account for cache writes and reads separately from the discounted input and output rates.

Context size still controls much of the bill. Tool-heavy workflows add definitions, results, logs, diffs, and test output to each request. Extended thinking is also billed as output. If you’ve been using Anthropic models for a while, keep in mind that Sonnet 5's newer tokenizer produces approximately 30% more tokens than Sonnet 4.6 for the same text, with the exact increase depending on the workload. When trying to estimate potential costs, measure token use against representative repositories rather than extrapolating from a short prompt.

The $150 to $250 range comes from Anthropic's enterprise deployment data, not from the price of a typical Pro, Max, or Team subscription. Four variables account for much of the difference between a light pilot and a high-usage deployment:

• •Model selection: output from Fable or Opus costs more than output from Sonnet or Haiku.
• •Context size: repository files, instructions, tool definitions, logs, diffs, and test results can be resent across multiple turns.
• •Task length: long-running agents create more model calls, tool loops, and output tokens.
• •Concurrency: subagents and agent teams run separate context windows, so token use grows with the number of active instances and their runtime.

A change in the default model or effort level can change expected spend without a plan-price increase. A rollout budget should therefore track seat cost, model rate, repeated context, parallel agents, and tool payloads separately. Use a pilot to establish completion rate and cost per completed task before expanding access.

Claude Code manages the interface, repository context, tool loop, and session, while the configured endpoint supplies the model response that determines the next action. Routing the CLI to another provider can preserve the interface while changing model behavior behind it.

Fireworks exposes an OpenAI-compatible endpoint at https://api.fireworks.ai/inference/v1 and an Anthropic-compatible endpoint at https://api.fireworks.ai/inference. Configuration covers the endpoint, authentication, and model mapping. Before rollout, validate tool compatibility, context handling, caching, latency, and output quality against representative tasks.

Artificial Analysis publishes independent benchmarks across proprietary and open-weight models: the Intelligence Index covers broad reasoning, and the Coding Index covers software-engineering performance. Fireworks-hosted open models run at materially lower token rates than Anthropic API models on Fireworks serverless.

Sonnet 5 introductory pricing runs through August 31, 2026. Rates increase to $3 input, $0.30 cached hit, and $15 output on September 1.

GLM 5.2 is the closest open-weight model to Claude models according to Artificial Analysis. Kimi K2.7 Code and MiniMax M3 trade larger score differences for lower token rates. Treat these scores as signals rather than proof of how these models will perform on a specific codebase.

Start with the Artificial Analysis Coding Agent Index, which combines DeepSWE, Terminal-Bench v2, and SWE-Atlas-QnA results. Then run the same repository tasks through the strongest candidates and the current Claude default.

Track completed tasks, failed tool calls, retries, latency, repeated context, output tokens, and human repair time. A lower token rate only produces a lower total task cost when the model completes the work with an acceptable number of retries and corrections.

After choosing a model, use the current Fireworks serverless pricing page to budget model-specific input, cached-input, and output rates. Keep repeated repository context cacheable where possible. For large asynchronous workloads, Fireworks Batch API reduces input and output prices by an additional 50%. Batch API is recommended for asynchronous work such as evals, migrations, and large refactors.

Teams can route Claude Code through FireConnect, or route OpenCode, Cline, Aider, and other OpenAI-compatible coding tools through Fireworks’ OpenAI-compatible API.

FireConnect configures Claude Code to use Fireworks’ Anthropic-compatible endpoint and maps Claude model aliases to Fireworks models or routers.

1. Install Claude Code and FireConnect.
2. Authenticate with fireconnect login, or provide a Fireworks key when enabling the integration.
3. Run fireconnect claude on.
4. Restart Claude Code, start a new session, or use /model so the updated mapping takes effect.
5. Run fireconnect claude status to inspect the active endpoint, model aliases, and Fireworks rates.

FireConnect stores the API key in the operating system keychain when available and uses apiKeyHelper to retrieve it at runtime. It also backs up the previous provider settings so fireconnect claude off can restore them.

Defaults can change between FireConnect releases. Use fireconnect claude model list to see callable serverless models and fireconnect claude model select to update the main, Opus, Fable, Sonnet, Haiku, or subagent slot. Claude Code may display Anthropic list-price estimates for aliased models, so use FireConnect status, the model list, or the Fireworks billing dashboard for actual Fireworks rates.

Anthropic compatibility does not guarantee support for every Anthropic-specific field or server-side tool. Validate the tools and settings your repository depends on before wider deployment.

For OpenCode, Cursor, Cline, Aider, or any other coding tool that accepts OpenAI-compatible configuration, the setup is manual but covers the same three parts:

1. Set the base URL to https://api.fireworks.ai/inference/v1.
2. Set the API key to your Fireworks key.
3. Set the model ID in the format your tool expects.

Once configured, run the same repository task across two or three candidates and compare completion, latency, cache behavior, and total cost.

• •Cline: OpenAI Compatible, Base URL, API Key, Model.
• •Aider: OPENAI_API_BASE, OPENAI_API_KEY, aider --model openai/<model-name>.

Use benchmarks to create a shortlist, then verify each candidate against the repository and tools it will handle. As of July 2026, we recommend evaluating the following:

• •GLM 5.2: start here when benchmark performance is the main selection criterion among the three Fireworks-hosted models compared above.
• •Kimi K2.7 Code: test it for coding-focused workloads where its lower output rate offsets the benchmark difference.
• •MiniMax M3: include it when multimodal input is required or when a primary constraint is minimizing token cost

Keep a frontier Claude model in the evaluation set for hard debugging, complex refactors, and ambiguous requirements. Compare models on completed tasks and repair time, not only benchmark scores or token rates. Route a workload to a lower-cost model only when it clears the required quality threshold with acceptable latency and retries.

Claude Code's pricing is both high and layered: subscription tiers, per-token API rates, separate cache and batch charges, and a tokenizer change that quietly inflates token counts. Collectively, these compound and sit between you and a predictable bill. The complexity is exactly why the model layer is worth evaluating as a way to increase both savings and predictability. Many Fireworks customers have already run that test in production. A few noteworthy examples:

1. Gumloop moved an internal production agent from Opus 4.8 to GLM-5.2 on Fireworks and saw up to 72% cost savings with no change in user experience.
2. In Fireworks' research with Harvey on the Legal Agent Benchmark, an open-source GLM 5.1 setup matched or beat Claude Opus on all-pass tasks at roughly 40% of the end-to-end Opus cost ($368 versus $954), and a follow-up study generalized the pattern across coding, terminal, and legal benchmarks at 19% to 67% lower cost.

While open-source software is nearly always the most budget-friendly path, AI engineering teams understand that those savings are only worth it when an open model clears the quality bar on your repository, so it is critical validate performance on representative set of tasks or workflows. When it does clear the bar, keeping Claude Code and routing through FireConnect produces a significantly lower monthly bill while allowing developers to continue using the harness and daily workflows they’re already used to.