Skip to content

Claude API Pricing: Per-Model Cost Per Token

Compare the cost per token to the price you pay to ship the right-quality answer. These aren't necessarily the same.

ModelInputOutputBatch inBatch outCache read
Claude Fable 5$10.00$50.00$5.00$25.00$1.00
Claude Fable 5.1$10.00$50.00$5.00$25.00$0.25
Claude Haiku 4.5$1.00$5.00$0.50$2.50$0.10
Claude Opus 4.5$5.00$25.00$2.50$12.50$0.50
Claude Opus 4.6$5.00$25.00$2.50$12.50$0.50
Claude Opus 4.7$5.00$25.00$2.50$12.50$0.50
Claude Opus 4.8$5.00$25.00$2.50$12.50$0.50
Claude Opus 5$5.00$25.00$2.50$12.50$0.50
Claude Sonnet 4.5$3.00$15.00$1.50$7.50$0.30
Claude Sonnet 4.6$3.00$15.00$1.50$7.50$0.30
Claude Sonnet 5$2.00$10.00$1.00$5.00$0.20

All prices in USD per 1M tokens. Batch runs asynchronously at a reduced rate; cache read applies to reused input tokens. A dash means the provider does not publish that rate.

The spread from Haiku to Opus is 5-fold, which makes model choice look like a straight quality-for-money trade. It’s not, here’s why.

The sticker price is not the real rate

Batch processing halves the standard rate, and prompt caching bills reused tokens (a fixed system prompt or document) at a fraction of it. The headline number is where the estimate starts, not where the bill lands.

Claude Opus 4.5 input: one headline rate, three real rates ($/1M tokens)

When every model is good enough, cost is the differentiator

All three models answered a sample support email task,[^task] landing within five points of each other (Haiku 90, Sonnet 85, Opus 95). When quality is that close, cost decides, and Haiku delivered its 90 for about a seventh of what Opus charged. Paying up for the flagship bought almost nothing here.

Close quality (85-95), far apart on cost

Paying more does not always buy better quality

On a harder task with one right answer,[^task] Haiku dropped to 75 while Sonnet and Opus both scored 100. But Sonnet matched the flagship at a fifth of Opus’s cost, so a higher price did not buy a better answer. Which model wins depends on the task, not its token price.

On a harder task the flagship is matched for a fifth of the price

The best model today is not the best model forever

Anthropic updates these models constantly, so the model that clears your bar today can slip below it next week while a rival climbs past it. Measuring once picks the right model now; measuring on a schedule keeps quality high and cost down with no quiet regressions or cost creep.

The best model today is not the best model forever (illustrative)

Build the hygiene in from day one

If you are choosing between Haiku, Sonnet, and Opus before you have written the app, this is the moment to set up good model-selection and pipeline hygiene, while it costs nothing to change. The teams who stay cheap and reliable do four things from the start.

Baked in at the start, this is a few minutes of setup. Bolted on after a surprise bill or a quality complaint, it is a cleanup job. The pricing table is where the decision starts; this is the habit that keeps it right.

What you get on Pro

  • Score any Claude model on your own task
  • Cost, quality, and latency side by side
  • Pipeline diagnostics that identify actionable improvements
  • Scheduled benchmarks alert you when models regress or drift
  • API access to integrate measurements into your applications

Drive it from your agent, over MCP

  • Let your agent run the comparisons and read the results for you
  • Work from where you already are: your IDE, chat, or console
  • Over 40 tools your agent discovers automatically, no integration code
  • Agentic recipes for model selection, drift checks, and optimization loops

$129/mo $10 for your first week

Then $129/mo. Cancel anytime.

The table lists the Claude models we support for evaluation, not Anthropic's full catalogue. Rates come from our live registry and are updated frequently. The scored runs are real: three models, two tasks, October 2026. Your own task will score differently, against your prompts and data.