A rate per million tokens is not a budget. The calculator takes your request volume, prompt size and cache hit rate and gives you a monthly figure.
Claude Opus 5 API pricing (September 2026)
1M-token context window at standard pricing.
What it costs at real volumes
A chat-shaped workload: 800 input tokens and 300 output tokens per request, no caching, no batch.
Specifications
- Provider
- Anthropic Claude
- Context window
- 1.0M tokens
- Max output
- 128K tokens
- Tier
- frontier
- Status
- GA
- Blended $/1M (3:1)
- $10.00
- Cache break-even hit rate
- 22%
- Prices verified
- 11 Sep 2026
Source: Anthropic Claude pricing. Finitizer is not affiliated with Anthropic Claude.
Similar models
Other claude models
- Claude Sonnet 5-$6.00
- Claude Opus 4.1+$20.00
- Claude Sonnet 4.5-$4.00
- Claude Haiku 4.5-$8.00
- Claude Haiku 3.5-$8.40
Closest prices elsewhere
- Amazon Nova Premier-$5.00
- GPT-4o-$5.63
- GPT-4.1-$6.50
- o3-$6.50
Frequently asked questions
How much does Claude Opus 5 cost per 1M tokens?
Claude Opus 5 costs $5.00 per million input tokens and $25.00 per million output tokens at Anthropic Claude list prices. Output is 5.0x the input rate, so the input:output ratio of your workload drives the real cost more than the headline price.
Does Claude Opus 5 support prompt caching?
Yes. Cached input is billed at $0.500 per million tokens, 10x cheaper than uncached input. Cache writes carry a premium, so caching only pays above roughly a 22% hit rate.
What is the batch discount for Claude Opus 5?
Requests submitted through the asynchronous batch endpoint are billed at 50% off both input and output rates, bringing input to $2.50 and output to $12.50 per million tokens.
What is Claude Opus 5's context window?
1.0M tokens of context with up to 128K output tokens per request. A larger context window raises the ceiling on what you can send, not the price per token, but filling it on every request is one of the most common causes of an unexpected bill.
Running Claude Opus 5 in production?
Finitizer TokenOps attributes real token spend to teams, features, and prompts, so you find out which workload moved the bill before the invoice does.
