What You'll Learn
- The full token pricing table for Claude Opus 4.8 across standard, Fast Mode, batch, and prompt cache
- How Effort Control (Low, Medium, High, Extra, Max) shifts token spend by ~2.7x at the same $5/$25 rate
- Where the 3x cheaper Fast Mode ($10/$50) and the 50% Batch API discount actually pay off
- Why prompt caching can drop the effective input bill by up to 90% for repeated prefixes
- How the 4x honesty improvement and 61% multimodal savings change the enterprise ROI math for 2026
What Anthropic Shipped on May 28, 2026, and Why Pricing Matters Now
Anthropic released Claude Opus 4.8 on Thursday, May 28, 2026 — the same day the company also closed a $65 billion Series H at a $965 billion post-money valuation. The model sits on the same $5 per million input and $25 per million output token pricing as Opus 4.7, ships with the same 1M-token context window (the same tokenizer shift that changed Opus 4.7's literal mode behavior in April 2026), and uses the same claude-opus-4-8 model ID across the API, Claude Code, claude.ai, AWS, Google Cloud Vertex AI, and Microsoft Foundry. What is different is the shape of the price schedule underneath that headline rate. Fast Mode dropped 3x. A new Effort Control selector (Low, Medium, High, Extra/xhigh, Max) changes how many tokens a single request consumes without changing the per-token price. And the 4x reduction in unflagged code flaws, plus a 61% drop in multimodal token cost on partner benchmarks, has changed the production-cost math more than the price card alone suggests.
For anyone running Opus in production in 2026 — developers shipping Claude Code features, enterprise teams running document workflows through Box or Hebbia, finance and legal teams on CoCounsel, data agents like Databricks Genie reasoning over PDFs and diagrams — the pricing question is no longer "what does it cost per million tokens." The real questions are: which mode am I on, which effort level matches the task, am I paying for cached prefixes I am rereading, and is the new honesty saving me more than the new tokens cost. This article is the cost-analysis answer to all four, with the verified pricing from Anthropic's official Claude API pricing page as the source of truth.
The Full Token Pricing Table for Claude Opus 4.8
Anthropic lists five distinct token price points for Opus 4.8 in the standard, Fast Mode, batch, and prompt-cache categories. The headline $5/$25 is just the start; the actual cost per task depends on which category each of your tokens falls into. Per the Claude API pricing documentation, the full table for Opus 4.8 looks like this:
| Pricing tier | Input (per 1M tokens) | Output (per 1M tokens) | Notes |
|---|---|---|---|
| Standard | $5 | $25 | Same as Opus 4.7, 4.6, 4.5 |
| Fast Mode | $10 | $50 | 2.5x speed, down from $30/$150 |
| Batch API | $2.50 | $12.50 | 50% off, async 24h window |
| Cache write (5m) | $6.25 | — | 1.25x base input, 5-min TTL |
| Cache write (1h) | $10 | — | 2x base input, 1-hour TTL |
| Cache read | $0.50 | — | 10% of base input rate |
The official Claude API pricing page also notes that Opus 4.7 and later use a new tokenizer, "contributing to their improved performance on a wide range of tasks," but that the new tokenizer "may use up to 35% more tokens for the same fixed text." That is a real cost consideration: if you are migrating an Opus 4.1 or 4.0 application to Opus 4.8, the same prompt will bill for more tokens than it did before, even at the same per-token rate. The 4.6 to 4.8 migration is roughly token-neutral because the tokenizer did not change between 4.6 and 4.7.
Why Standard Pricing Stayed at $5/$25
The simplest read of the launch is also the most important: Anthropic chose to keep the standard API rate flat at $5/$25, even though the model is meaningfully better. On Anthropic's own framing, the model itself is "a modest but tangible improvement" over Opus 4.7. The release post explicitly says "pricing for regular usage is unchanged from Opus 4.7." That decision is a competitive signal, not a cost signal. Anthropic is essentially giving existing Opus 4.7 customers a free upgrade in the standard lane and asking them to pay more in the Fast Mode and high-effort lanes if they want the speed and reasoning depth that justify a premium.
The practical implication is that anyone who was happy with Opus 4.7 on the standard rate will be happy with Opus 4.8 on the standard rate, with better coding, sharper judgment, and the same 1M-token context window. The cost story for the standard lane is — by design — not the story. The cost story is in Fast Mode, in effort selection, in cache, and in the honesty and multimodal efficiency gains that reduce the number of times you have to re-run a task to get a usable answer. (For a deep dive on the architectural shift that ships alongside the model, including the new Plan → Assign → Verify multi-agent system, see our breakdown of Claude Opus 4.8 Dynamic Workflows.)
Claude Opus 4.8 Dynamic Workflows Explained: How Anthropic's Multi-Agent System Transforms Large-Scale Coding
Effort Control: 5 Levels and the ~2.7x Token-Cost Spread
The single most under-reported cost dimension of Opus 4.8 is the new Effort Control selector, which lives in the model picker on claude.ai, Claude Code, and Cowork. There are five named levels: Low, Medium, High, Extra (called "xhigh" in Claude Code), and Max. The default for new sessions is High, which Anthropic says "spends a similar number of tokens as Opus 4.7's default, but with better performance." Per the official effort documentation, the level controls how much reasoning the model does before producing a response. Higher effort means more output tokens, more thinking, and a higher-quality answer. Lower effort means faster, cheaper, less depth.
The cost spread across effort levels is real, and it is roughly a 2.7x ratio between the cheapest and most expensive levels. The Reddit PSA on the launch framed the surprise this way: "Opus 4.8 'medium' effort now spends more output tokens than 4.7 high or almost as much as 4.6 max. Opus 4.8 'low' has about the same problem" — meaning Opus 4.8 rebalances the entire effort curve relative to 4.7. A community benchmark on Opus 4.7 vs GPT-5.4 effort selectors found that Max effort hit 75% on the test prompt, against the next-best level at 71% — a four-percentage-point gain for roughly 2.7x the token cost vs xhigh. That ratio is the practical reason the menu exists. Same model, same context window, same $5/$25 per-token rate — but the user controls how much of the model's reasoning budget the question is allowed to consume.
The activation recipe in the Claude Code community is consistent: /model opus 4.8 + /effort ultracode (which sets Extra/xhigh) + include the word "workflow" in the prompt. For one-off triage, "low" is the right call. For architectural reviews and complex multi-step reasoning, the cost of skipping effort is more expensive than paying for the extra tokens. For Dynamic Workflows specifically, the recommended pairing is Extra — the orchestrator has to plan a multi-agent fan-out and coordinate adversarial verification, and skimping on the orchestrator's reasoning budget is a false economy.
Fast Mode: The 3x Cheaper, 2.5x Faster Story
The single biggest headline number on the Opus 4.8 pricing page is the Fast Mode price cut. Per Anthropic's Fast Mode documentation, Fast Mode pricing on Opus 4.8 is $10 per million input tokens and $50 per million output tokens. On Opus 4.7 and Opus 4.6, the same Fast Mode was $30/$150 — a 3x reduction in cost, with the same 2.5x speed multiplier relative to standard inference. Fast Mode is available to all Claude Code users on Pro, Max, and Team plans, and via the Claude API for $10/$50. The Reddit reaction in r/ClaudeAI captured the shift: "The fast mode alone at $10/50 per million tokens (3x cheaper, 2.5x faster) would already justify the upgrade for most of my workloads."
The per-request cost of Fast Mode is 2x the standard rate ($10 input, $50 output, vs $5/$25). That sounds like a premium, but the math is different: the user gets 2.5x the speed, so the cost per minute of wall-clock time is lower, not higher. A request that would take 12 seconds on standard inference at $0.025 of output cost is the same 12 seconds of work delivered in 4.8 seconds on Fast Mode for $0.050 of output cost — 2x more expensive per request, 2.5x cheaper per minute of latency. For interactive coding, customer-facing agents, and any UI where the user is staring at a spinner, Fast Mode is the right lane.
The use case breakdown from Anthropic's own docs and the partner commentary is consistent. Fast Mode is for interactive coding in Claude Code where a developer is waiting on a response between keystrokes; standard mode is for async work where latency does not matter; Fast Mode is not available with the Batch API (because batch is the cheaper async path) and is not available on Claude Platform on AWS (the first-party AWS billing path through Claude Consumption Units). For sub-50ms response times and conversational agents, Fast Mode at $10/$50 is the new default, and the 3x price cut from the previous Opus generation is the part of the launch that has the most immediate impact on monthly bills.
Prompt Caching: 90% Off for Repeated Prefixes
Prompt caching is the highest-leverage cost optimization on the Claude API, and Opus 4.8 extends the surface where it pays off. Per Anthropic's prompt caching documentation, there are three pricing multipliers relative to the base input rate: 5-minute cache writes cost 1.25x the base input rate ($6.25 per million tokens for Opus 4.8), 1-hour cache writes cost 2x the base input rate ($10 per million tokens), and cache reads cost 0.1x the base input rate ($0.50 per million tokens). Caching pays off after just one cache read for the 5-minute duration, or after two cache reads for the 1-hour duration, because the 1.25x write is amortized over multiple hits.
The cost math is straightforward for any application that sends a large repeated prefix on every request. A customer support agent that re-sends a 5,000-token system prompt and 20,000-token knowledge base on every turn is paying 25,000 tokens of input at $5/M = $0.125 per turn at the standard rate. With prompt caching, the 25,000-token prefix is a cache write at $6.25/M = $0.15625 once every 5 minutes, and every subsequent turn inside that 5-minute window is a cache read at $0.50/M = $0.0125. For a 10-turn conversation, the standard path costs $1.25 in input; the cached path costs $0.15625 + (9 × $0.0125) = $0.269. That is a 78% reduction on the input side, and the 90% headline number cited in Anthropic's own materials is the asymptotic case where the prefix dominates the request and is read many times within the cache window.
Opus 4.8 also lowers the minimum cacheable prompt length to 1,024 tokens, down from 2,048 on Opus 4.7. That change unlocks prompt caching on a class of applications that previously could not justify it: short conversational agents, code-completion suggestions, in-app assistants, and any flow where the system prompt plus a short context fits inside 1,024 tokens. Simon Willison's launch-day note on the change captures the practical impact: prompts that were too short to cache on 4.7 are now cacheable on 4.8. The cache discount is also stackable: cache writes and reads can be combined with the Batch API 50% discount on a different request, so the same prefix can drive both an interactive cached conversation and an overnight batch job at a combined discount.
Batch Processing: 50% Off for Async Workloads
The Batch API is the cheapest path through Claude for any workload that does not need a synchronous response. Per Anthropic's pricing documentation, the Batch API on Opus 4.8 is $2.50 per million input tokens and $12.50 per million output tokens — exactly half the standard rate. The tradeoff is that requests are processed asynchronously inside a 24-hour window. For evals, document analysis pipelines, overnight backfills, large classification jobs, and any workload where the answer does not need to be in a user's hand inside 60 seconds, the Batch API is the right lane.
A worked example from Apidog's breakdown makes the math concrete. An overnight batch job with 1,000,000 input tokens and 200,000 output tokens runs at the standard rate for $0.25 of input + $5.00 of output = $5.25, or at the batch rate for $0.125 of input + $2.50 of output = $2.625. That is a $2.625 saving on a single batch — a 50% reduction, by design, on the same Opus 4.8 model. The same batch discount applies to Opus 4.7, 4.6, 4.5, Sonnet 4.6, and Haiku 4.5, so the discount is not Opus 4.8-specific; it is a feature of the Batch API that has been live since 2024 and is now the default async lane for any cost-sensitive workload.
The combinations matter. The 50% batch discount stacks with the 90% prompt-cache read discount, so a workload that uses both batch and caching can be substantially cheaper than the headline rate suggests. The Batch API is not available with Fast Mode (because Fast Mode is a latency feature, not a cost feature), but the two paths can be combined in the same application: interactive Fast Mode for the user-facing surface, batch for the overnight backfill. The same prompt prefix can be cached and used in both flows, with the cache write amortized across the interactive and batch paths. The 50% saving on batch alone is enough to justify a re-architecture of any application that has a "run once a night" job currently using synchronous API calls.
The 4x Honesty ROI: Fewer Code Flaws, Lower Production Costs
The single most consequential cost story in the Opus 4.8 launch is not a price card change — it is the 4x reduction in unflagged code flaws. Anthropic's own evaluations show that Opus 4.8 is around four times less likely than Opus 4.7 to allow flaws in code it has written to pass unremarked. Independent validation lines up: a Towards AI test of Opus 4.8 vs GPT-5.5 vs Gemini 3.1 Pro on 20 tasks described the "4x reduction in unflagged code flaws" as the single number that survived skeptical testing, and the analyst noted that "I gave all three a 1,200-line [task]... previous Claude 4.7 hallucinates. Claude Opus 4.8 hits a zero-error build."
The honest-improvement story is the one that changes enterprise ROI, and it does not show up on the pricing page. A typical production codebase in 2026 has a small per-task cost (the API tokens to write a function or fix a bug) and a large per-defect cost (the engineering time to find, triage, fix, and re-deploy the broken function, the customer-impact cost of a production bug, the opportunity cost of the engineer who could have been building features instead of debugging the AI's output). The Anthropic numbers on internal evals suggest the per-defect rate on Opus 4.8 is roughly 25% of the Opus 4.7 rate. If the average cost of a missed flaw in your pipeline is $200 in engineering time, the per-defect saving of 4x is worth more than the entire API bill for a typical team. That is the part of the launch the per-token pricing page does not capture.
The honest-improvement story is also the part of the launch that the partners emphasized. CoCounsel Legal reported "meaningful improvements in consistency and reasoning quality" on Opus 4.8 vs prior Opus models for legal-document workflows. Hebbia reported the same quality as Opus 4.7 with "noticeably better citation precision and more token efficiency on retrieval" for financial-document workflows. Box AI reported meaningful gains on report drafting and financial analysis. Browserbase reported Opus 4.8 scoring 84% on Online-Mind2Web, the highest score they have measured on a computer-use benchmark. None of these are headline-grabbing benchmark numbers — they are the boring, enterprise-relevant numbers that change the cost-per-outcome calculation that procurement teams actually use.
61% Cheaper Multimodal and the Databricks Genie Numbers
The second non-pricing-page cost story is the 61% drop in multimodal token cost reported by Databricks on its Genie data agent. Per Databricks' CTO Hanlin Tang in Anthropic's launch post (alongside benchmark data from GLM-4.7 vs Opus comparisons), Genie running on Opus 4.8 can "reason directly over PDFs, diagrams, and other unstructured content at 61% cheaper token cost than Opus 4.7." The way to read that number is that Opus 4.8 needs fewer tokens to do the same multimodal reasoning task than Opus 4.7, even at the same per-token rate. The 61% is a token-efficiency gain, not a price-card cut — the same $5/$25 applies, but the request consumes 61% fewer tokens for the same output.
The reason is the new tokenizer introduced with Opus 4.7, plus targeted improvements to how the model handles image and document inputs. The same input PDF requires fewer tokens to represent on Opus 4.7 and 4.8 than it did on Opus 4.6, and the new model also extracts the same information with fewer rounds of inference. The combined effect is a 61% drop in the tokens billed for a multimodal workflow. For applications that do heavy document analysis — legal discovery, financial filings review, medical records processing, any enterprise workflow where PDFs and diagrams are the primary input — this is the highest-leverage cost improvement in the launch. The headline $5/$25 does not move; the actual cost per document does.
The Databricks number lines up with the partner numbers from Browserbase (84% on Online-Mind2Web for computer use) and with the broader April 2026 model war between Claude, GPT-5.5 Spud, and DeepSeek V4 and from Cursor (where Opus 4.8 used fewer tool-call steps to reach the same intelligence on CursorBench). The through-line is that the model is more token-efficient on the workloads that enterprise teams actually run. The 4x honesty improvement means fewer re-runs to fix a broken output. The 61% multimodal saving means fewer tokens per document. The 2.5x speed of Fast Mode at 3x lower cost means lower latency for interactive workflows. None of these are headline benchmark numbers, and all of them are the cost improvements that procurement teams will feel in their monthly bills.
Model Tier Comparison: Opus 4.8 vs Sonnet 4.6 vs Haiku 4.5
The Claude model lineup in mid-2026 is three tiers: Haiku 4.5 at $1/$5 per million tokens, Sonnet 4.6 at $3/$15, and Opus 4.8 at $5/$25. The pricing ratios are roughly 5x between Haiku and Opus on input, 5x on output, and the same 5x on cache write and read prices. For a workload that is well within the capability envelope of Sonnet 4.6, routing the request to Sonnet 4.6 instead of Opus 4.8 is a 40% input cost reduction and a 40% output cost reduction. For a workload that is well within the capability envelope of Haiku 4.5, the reduction is 80% on both sides. The capability gap is what makes Opus worth the premium; for workloads where Sonnet or Haiku can do the job, they should do the job.
| Workload | Best model | Standard rate | Why |
|---|---|---|---|
| High-volume customer support triage | Haiku 4.5 | $1 / $5 | 80% cheaper than Opus, sub-200ms latency |
| Standard chat, summarization, edits | Sonnet 4.6 | $3 / $15 | 40% cheaper than Opus, near-Opus quality on most tasks |
| Long-running agents, code migration | Opus 4.8 (High effort) | $5 / $25 | 4x fewer unflagged code flaws, max honesty |
| Interactive coding in Claude Code | Opus 4.8 Fast Mode | $10 / $50 | 2.5x speed, lowest latency per minute |
| Overnight evals, document pipelines | Opus 4.8 Batch | $2.50 / $12.50 | 50% off, 24h async window |
The honest read on the 5x price gap between Haiku and Opus is that the gap (and the much wider gap to DeepSeek V4 at $0.55 per million tokens) is that the gap is not as wide as it looks when you factor in token efficiency and re-run rates. For workloads that push the capability envelope, Opus 4.8 produces correct code on the first attempt where Sonnet 4.6 and Haiku 4.5 would require a re-run, and the re-run is the most expensive part of the cost per task. For workloads that are within the capability envelope of Sonnet 4.6, the 40% saving is real and worth routing. For workloads that are within the capability envelope of Haiku 4.5, the 80% saving is real and worth routing. The cost-optimized 2026 stack is a router that picks the right model for the task, not a single model that tries to do everything at the highest price.
The same model-tier logic applies to the cache and batch lanes. A Sonnet 4.6 cache read is $0.30 per million tokens (10% of the $3 base input rate), and a Haiku 4.5 cache read is $0.10 per million tokens — both are 90% off their respective standard input rates, but the absolute price floor is lower on Haiku. For applications where Haiku's quality is acceptable, the optimal cost is Haiku + cache + batch. The optimal cost on the highest-capability model is Opus 4.8 + cache + batch, with Fast Mode reserved for interactive use cases where the latency saving is worth the 2x per-token premium. The cost-analysis answer to "which model should I use" in 2026 is "the cheapest one that produces a correct answer on the first attempt" — and that answer changes by workload.
Conclusion
The Claude Opus 4.8 pricing story is not a price-card story. The standard $5/$25 rate is unchanged from Opus 4.7, and the headline takeaway for most teams is "free upgrade" — same per-token rate, better coding, sharper judgment, more honest output, same 1M-token context window. The real cost story is in the four other price points on the schedule: Fast Mode at $10/$50 is 3x cheaper than before for interactive workflows that need 2.5x the speed; the Batch API at $2.50/$12.50 is 50% off for async jobs that can wait up to 24 hours; prompt caching at $0.50 cache reads drops the effective input bill by up to 90% for repeated prefixes; and Effort Control lets the user pick how many tokens a single request consumes, with a ~2.7x spread between the cheapest and most expensive levels. The 4x reduction in unflagged code flaws and the 61% drop in multimodal token cost on partner benchmarks are the non-pricing-page cost wins that change the per-task ROI more than any rate change.
The procurement question for 2026 is no longer "which model costs less per million tokens." The right questions are: which mode am I on, which effort level matches the task, am I paying for cached prefixes I am rereading, and is the new honesty saving me more than the new tokens cost. Opus 4.8 is the first Anthropic release where the answer to all four questions matters more than the headline rate. If you are routing work between Opus, Sonnet, and Haiku, the right cost-optimized stack is a router that picks the cheapest model that produces a correct answer on the first attempt, with cache and batch on every request, and Effort Control on every interactive session. Treat the May 28, 2026 launch date as the day the Claude pricing model stopped being a single number and started being a five-by-five decision matrix. (For a parallel look at how MiniMax-M3 prices against the Claude family, see our M3 pricing and context window guide.)
Last Updated: July 06, 2026 | Source: Anthropic Claude API Pricing (Official), Introducing Claude Opus 4.8 (Official), and Fast Mode Documentation (Official)