Claude Pricing Guide (April 2026): Every Model, Discount, and Cost Optimization

Current Claude Model Pricing

All prices are per 1 million tokens. Verified against Anthropic's pricing page, April 2026.

The pricing structure follows a consistent pattern: output tokens cost exactly 5x input tokens across all models. This is important for cost estimation. If your application generates long outputs (code, articles, reports), output tokens will dominate your bill. If your application sends long context but generates short responses (classification, extraction, summarization), input tokens are the primary cost driver.

Batch API: 50% Off Everything

The Batch API is the simplest way to cut Claude costs in half. You submit a batch of requests, and Anthropic returns results within 24 hours (typically faster, often within 1-2 hours). Both input and output tokens are billed at 50% of standard rates.

The batch API works well for: content generation pipelines, bulk document analysis, data extraction and classification, evaluation runs, and any workload where you do not need real-time responses. It does not work for chatbots, interactive assistants, or anything requiring sub-second latency.

One detail that surprises developers: prompt caching works with the Batch API. The discounts stack. A cached-input batch request on Haiku costs $0.05/1M for cached input tokens, which is 20x cheaper than standard Haiku input pricing.

Prompt Caching: Up to 90% Off Input Tokens

Prompt caching is Claude's most powerful cost-saving feature, and it is underused. The concept: you mark a section of your prompt (system instructions, reference documents, few-shot examples) as cacheable. The first request writes it to a cache. Subsequent requests read from that cache at 90% off the normal input price.

How It Works

You add a cache_control breakpoint to your message content. Everything before that breakpoint is eligible for caching. There are two cache durations:

• 5-minute cache (ephemeral): Cache write costs 1.25x normal input. Cache read costs 0.1x normal input. Best for interactive sessions where the same system prompt is reused across multiple user messages.
• 1-hour cache: Cache write costs 2x normal input. Cache read costs 0.1x normal input. Best for batch processing pipelines where the same context is used across many requests over a longer period.

Caching Cost Math

The breakeven point is remarkably fast. If you reuse a cached prompt even twice, you save money. For a chatbot with a 2,000-token system prompt handling 100 messages per session, prompt caching turns $0.006 per message (at Sonnet rates) into $0.0006 per message after the first request. Over a million messages per month, that is $5,400 in savings.

Minimum Cache Sizes

The cached content must meet minimum token thresholds: Haiku 4.5 requires 1,024 tokens, Sonnet 4.6 and Opus 4.6 require 2,048 tokens. If your system prompt is shorter than these thresholds, pad it with reference documentation or few-shot examples. The caching savings almost always justify adding more context.

Extended Thinking Costs

All current Claude models support extended thinking, where the model reasons internally before generating a visible response. This improves output quality on complex tasks but increases costs because thinking tokens are billed as output tokens.

Here is what this means in practice:

• A simple classification task might use 50 thinking tokens and 10 output tokens. The thinking overhead is negligible.
• A complex coding task might use 5,000 thinking tokens and 500 output tokens. You are paying for 5,500 output tokens, 10x what you see in the response.
• A deep research analysis might use 20,000+ thinking tokens. At Opus output rates ($25/1M), 20K thinking tokens cost $0.50 per request.

You can set a max_tokens budget to cap thinking costs. This is important for production applications where unpredictable thinking lengths could spike your bill. A reasonable default: set max_tokens to 3-5x your expected visible output length.

Fast Mode Pricing (Opus 4.6 Only)

Opus 4.6 has a "fast" mode in research preview that provides significantly faster output at a steep premium: 6x standard pricing.

At $150/1M output tokens, fast mode is the most expensive LLM API available from any major provider. It makes sense for latency-sensitive applications where Opus-level reasoning is required and cost is secondary. For most workloads, Sonnet 4.6 at standard speed provides better value than Opus at fast speed.

Claude vs. Competitors: Price Comparison

How Claude stacks up against the other major LLM providers on price as of April 2026.

Claude Opus 4.6 at $5/$25 is cheaper than GPT-5 at $10/$30 while offering a larger context window (1M vs. 128K). Sonnet 4.6 at $3/$15 is slightly more expensive than GPT-4o at $2.50/$10 on a per-token basis. Where Claude loses on price is the budget tier: Haiku at $1/$5 is significantly more expensive than GPT-4o mini at $0.15/$0.60 or Gemini 2.0 Flash at $0.075/$0.30.

The pricing gap at the budget tier matters for high-volume classification and extraction tasks. If you are processing millions of documents and do not need Claude-quality reasoning, GPT-4o mini or Gemini Flash save 7-13x per token.

Real-World Cost Examples

Concrete cost estimates for common workloads, assuming standard pricing (no batch, no caching) and then with optimizations applied.

The "with optimizations" column assumes batch API (50% off) plus prompt caching on a 2K-token system prompt reused across all requests (which reduces that portion of input to 10% of standard). The actual savings depend on how much of your input is cacheable and whether your workload tolerates batch latency.

Model Selection: When to Use Which

Picking the right model for each task is the highest-impact cost decision. Here is a practical framework.

• Haiku 4.5 ($1/$5): Classification, entity extraction, data formatting, intent routing, simple Q&A, content filtering, and any task where the input is structured and the output is short. If you can write the expected output format in a few sentences, Haiku handles it.
• Sonnet 4.6 ($3/$15): Code generation, document analysis, multi-step reasoning, long-form writing, and general-purpose assistant tasks. This is the model most production applications should default to. It handles 90% of tasks at a fraction of Opus cost.
• Opus 4.6 ($5/$25): Complex research synthesis, novel problem-solving, tasks requiring deep domain reasoning, and situations where getting the right answer on the first try is critical (legal analysis, medical reasoning, financial modeling). Only use Opus when Sonnet demonstrably fails at the task.

A well-designed system routes each request to the cheapest capable model. A support chatbot might use Haiku for FAQ-style questions, Sonnet for troubleshooting conversations, and Opus only for escalated technical analysis. This model routing approach can reduce overall costs by 40-60% compared to running everything through Sonnet.

Related Resources