# Pricing¶
¶
Learn about Anthropic's pricing structure for models and features¶
¶
---¶
¶
This page provides detailed pricing information for Anthropic's models and features. All prices are in USD.¶
¶
For the most current pricing information, please visit [claude.com/pricing](https://claude.com/pricing).¶
¶
## Model pricing¶
¶
The following table shows pricing for all Claude models across different usage tiers:¶
¶
| Model | Base Input Tokens | 5m Cache Writes | 1h Cache Writes | Cache Hits & Refreshes | Output Tokens |¶
|-------------------|-------------------|-----------------|-----------------|----------------------|---------------|¶
| Claude Opus 4.6 | $5 / MTok | $6.25 / MTok | $10 / MTok | $0.50 / MTok | $25 / MTok |¶
| Claude Opus 4.5 | $5 / MTok | $6.25 / MTok | $10 / MTok | $0.50 / MTok | $25 / MTok |¶
| Claude Opus 4.1 | $15 / MTok | $18.75 / MTok | $30 / MTok | $1.50 / MTok | $75 / MTok |¶
| Claude Opus 4 | $15 / MTok | $18.75 / MTok | $30 / MTok | $1.50 / MTok | $75 / MTok |¶
| Claude Sonnet 4.6 | $3 / MTok | $3.75 / MTok | $6 / MTok | $0.30 / MTok | $15 / MTok |¶
| Claude Sonnet 4.5 | $3 / MTok | $3.75 / MTok | $6 / MTok | $0.30 / MTok | $15 / MTok |¶
| Claude Sonnet 4 | $3 / MTok | $3.75 / MTok | $6 / MTok | $0.30 / MTok | $15 / MTok |¶
| Claude Sonnet 3.7 ([deprecated](/docs/en/about-claude/model-deprecations)) | $3 / MTok | $3.75 / MTok | $6 / MTok | $0.30 / MTok | $15 / MTok |¶
| Claude Haiku 4.5 | $1 / MTok | $1.25 / MTok | $2 / MTok | $0.10 / MTok | $5 / MTok |¶
| Claude Haiku 3.5 | $0.80 / MTok | $1 / MTok | $1.6 / MTok | $0.08 / MTok | $4 / MTok |¶
| Claude Opus 3 ([deprecated](/docs/en/about-claude/model-deprecations)) | $15 / MTok | $18.75 / MTok | $30 / MTok | $1.50 / MTok | $75 / MTok |¶
| Claude Haiku 3 | $0.25 / MTok | $0.30 / MTok | $0.50 / MTok | $0.03 / MTok | $1.25 / MTok |¶
¶
<Note>¶
MTok = Million tokens. The "Base Input Tokens" column shows standard input pricing, "Cache Writes" and "Cache Hits" are specific to [prompt caching](#prompt-caching), and "Output Tokens" shows output pricing. See [prompt caching pricing](#prompt-caching) below for an explanation of the cache columns and pricing multipliers.¶
</Note>¶
¶
## Third-party platform pricing¶
¶
Claude models are available on [AWS Bedrock](/docs/en/build-with-claude/claude-on-amazon-bedrock), [Google Vertex AI](/docs/en/build-with-claude/claude-on-vertex-ai), and [Microsoft Foundry](/docs/en/build-with-claude/claude-in-microsoft-foundry). For official pricing, visit:¶
- [AWS Bedrock pricing](https://aws.amazon.com/bedrock/pricing/)¶
- [Google Vertex AI pricing](https://cloud.google.com/vertex-ai/generative-ai/pricing)¶
- [Microsoft Foundry pricing](https://azure.microsoft.com/en-us/pricing/details/ai-foundry/#pricing)¶
¶
<Note>¶
**Regional endpoint pricing for Claude 4.5 models and beyond**¶
¶
Starting with Claude Sonnet 4.5 and Haiku 4.5, AWS Bedrock and Google Vertex AI offer two endpoint types:¶
- **Global endpoints:** Dynamic routing across regions for maximum availability¶
- **Regional endpoints:** Data routing guaranteed within specific geographic regions¶
¶
Regional endpoints include a 10% premium over global endpoints. The Claude API (1P) is global by default; for 1P data residency options and pricing, see [Data residency pricing](#data-residency-pricing) below.¶
¶
**Scope:** This pricing structure applies to Claude Sonnet 4.5, Haiku 4.5, and all future models. Earlier models (Claude Sonnet 4, Opus 4, and prior releases) retain their existing pricing.¶
¶
For implementation details and code examples:¶
- [AWS Bedrock global vs regional endpoints](/docs/en/build-with-claude/claude-on-amazon-bedrock#global-vs-regional-endpoints)¶
- [Google Vertex AI global vs regional endpoints](/docs/en/build-with-claude/claude-on-vertex-ai#global-vs-regional-endpoints)¶
</Note>¶
¶
## Feature-specific pricing¶
¶
### Prompt caching¶
¶
Prompt caching reduces costs and latency by reusing previously processed portions of your prompt across API calls. Instead of reprocessing the same large system prompt, document, or conversation history on every request, the API reads from cache at a fraction of the standard input price.¶
¶
There are two ways to enable prompt caching:¶
¶
- **Automatic caching:** Add a single `cache_control` field at the top level of your request. The system automatically manages cache breakpoints as conversations grow. This is the recommended starting point for most use cases.¶
- **Explicit cache breakpoints:** Place `cache_control` directly on individual content blocks for fine-grained control over exactly what gets cached.¶
¶
Prompt caching uses the following pricing multipliers relative to base input token rates:¶
¶
| Cache operation | Multiplier | Duration |¶
|:----------------|:-----------|:---------|¶
| 5-minute cache write | 1.25x base input price | Cache valid for 5 minutes |¶
| 1-hour cache write | 2x base input price | Cache valid for 1 hour |¶
| Cache read (hit) | 0.1x base input price | Same duration as the preceding write |¶
¶
Cache write tokens are charged when content is first stored. Cache read tokens are charged when a subsequent request retrieves the cached content. A cache hit costs 10% of the standard input price, which means caching pays off after just one cache read for the 5-minute duration (1.25x write), or after two cache reads for the 1-hour duration (2x write).¶
¶
These multipliers stack with other pricing modifiers, including the Batch API discount, long context pricing, and data residency.¶
¶
For implementation details, supported models, and code examples, see the [prompt caching documentation](/docs/en/build-with-claude/prompt-caching).¶
¶
### Data residency pricing¶
¶
For Claude Opus 4.6 and newer models, specifying US-only inference via the `inference_geo` parameter incurs a 1.1x multiplier on all token pricing categories, including input tokens, output tokens, cache writes, and cache reads. Global routing (the default) uses standard pricing.¶
¶
This applies to the Claude API (1P) only. Third-party platforms have their own regional pricing. See [AWS Bedrock](https://aws.amazon.com/bedrock/pricing/) and [Google Vertex AI](https://cloud.google.com/vertex-ai/generative-ai/pricing) for details. Earlier models retain their existing pricing regardless of `inference_geo` settings.¶
¶
For more information, see the [data residency documentation](/docs/en/build-with-claude/data-residency).¶
¶
### Fast mode pricing¶
¶
[Fast mode](/docs/en/build-with-claude/fast-mode) (beta: research preview) for Claude Opus 4.6 provides significantly faster output at premium pricing (6x standard rates). Fast mode pricing applies across the full context window, including requests over 200k input tokens. Currently supported on Opus 4.6:¶
¶
| Input | Output |¶
|:------|:-------|¶
| $30 / MTok | $150 / MTok |¶
¶
Fast mode pricing stacks with other pricing modifiers:¶
- [Prompt caching multipliers](#model-pricing) apply on top of fast mode pricing¶
- [Data residency](/docs/en/build-with-claude/data-residency) multipliers apply on top of fast mode pricing¶
¶
Fast mode is not available with the [Batch API](#batch-processing).¶
¶
For more information, see the [fast mode documentation](/docs/en/build-with-claude/fast-mode).¶
¶
### Batch processing¶
¶
The Batch API allows asynchronous processing of large volumes of requests with a 50% discount on both input and output tokens.¶
¶
| Model | Batch input | Batch output |¶
|-------------------|------------------|-----------------|¶
| Claude Opus 4.6 | $2.50 / MTok | $12.50 / MTok |¶
| Claude Opus 4.5 | $2.50 / MTok | $12.50 / MTok |¶
| Claude Opus 4.1 | $7.50 / MTok | $37.50 / MTok |¶
| Claude Opus 4 | $7.50 / MTok | $37.50 / MTok |¶
| Claude Sonnet 4.6 | $1.50 / MTok | $7.50 / MTok |¶
| Claude Sonnet 4.5 | $1.50 / MTok | $7.50 / MTok |¶
| Claude Sonnet 4 | $1.50 / MTok | $7.50 / MTok |¶
| Claude Sonnet 3.7 ([deprecated](/docs/en/about-claude/model-deprecations)) | $1.50 / MTok | $7.50 / MTok |¶
| Claude Haiku 4.5 | $0.50 / MTok | $2.50 / MTok |¶
| Claude Haiku 3.5 | $0.40 / MTok | $2 / MTok |¶
| Claude Opus 3 ([deprecated](/docs/en/about-claude/model-deprecations)) | $7.50 / MTok | $37.50 / MTok |¶
| Claude Haiku 3 | $0.125 / MTok | $0.625 / MTok |¶
¶
For more information about batch processing, see the [batch processing documentation](/docs/en/build-with-claude/batch-processing).¶
¶
### Long context pricing¶
¶
Claude Opus 4.6 and Sonnet 4.6 include the full [1M token context window](/docs/en/build-with-claude/context-windows) at standard pricing. (A 900k-token request is billed at the same per-token rate as a 9k-token request.) Prompt caching and batch processing discounts apply at standard rates across the full context window.¶
¶
For Claude Sonnet 4.5 and Sonnet 4, the 1M token context window is in beta for organizations in [usage tier](/docs/en/api/rate-limits) 4 and organizations with custom rate limits. When the `context-1m-2025-08-07` beta header is included, requests that exceed 200k input tokens are automatically charged at premium long context rates:¶
¶
| Model | ≤ 200k input tokens<br />Input | ≤ 200k input tokens<br />Output | > 200k input tokens<br />Input | > 200k input tokens<br />Output |¶
| --- | --- | --- | --- | --- |¶
| Claude Sonnet 4.5 / 4 | \$3 / MTok | \$15 / MTok | \$6 / MTok | \$22.50 / MTok |¶
¶
Long context pricing for Sonnet 4.5 and Sonnet 4 stacks with other pricing modifiers:¶
- The [Batch API 50% discount](#batch-processing) applies to long context pricing¶
- [Prompt caching multipliers](#model-pricing) apply on top of long context pricing¶
¶
<Note>¶
Even with the beta flag enabled, requests with fewer than 200k input tokens are charged at standard rates. If your request exceeds 200k input tokens, all tokens incur premium pricing.¶
¶
The 200k threshold is based solely on input tokens (including cache reads/writes). Output token count does not affect pricing tier selection, though output tokens are charged at the higher rate when the input threshold is exceeded.¶
</Note>¶
¶
For Claude Sonnet 4.5 and Sonnet 4, to check if your API request was charged at premium long context rates, examine the `usage` object in the API response:¶
¶
```json¶
{¶
"usage": {¶
"input_tokens": 250000,¶
"cache_creation_input_tokens": 0,¶
"cache_read_input_tokens": 0,¶
"output_tokens": 500¶
}¶
}¶
```¶
¶
Calculate the total input tokens by summing:¶
- `input_tokens`¶
- `cache_creation_input_tokens` (if using prompt caching)¶
- `cache_read_input_tokens` (if using prompt caching)¶
¶
If the total exceeds 200,000 tokens, the entire request was billed at premium long context rates.¶
¶
For more information about the `usage` object, see the [API response documentation](/docs/en/api/messages#response-usage).¶
¶
### Tool use pricing¶
¶
Tool use requests are priced based on:¶
1. The total number of input tokens sent to the model (including in the `tools` parameter)¶
2. The number of output tokens generated¶
3. For server-side tools, additional usage-based pricing (e.g., web search charges per search performed)¶
¶
Client-side tools are priced the same as any other Claude API request, while server-side tools may incur additional charges based on their specific usage.¶
¶
The additional tokens from tool use come from:¶
¶
- The `tools` parameter in API requests (tool names, descriptions, and schemas)¶
- `tool_use` content blocks in API requests and responses¶
- `tool_result` content blocks in API requests¶
¶
When you use `tools`, we also automatically include a special system prompt for the model which enables tool use. The number of tool use tokens required for each model are listed below (excluding the additional tokens listed above). Note that the table assumes at least 1 tool is provided. If no `tools` are provided, then a tool choice of `none` uses 0 additional system prompt tokens.¶
¶
| Model | Tool choice | Tool use system prompt token count |¶
|--------------------------|------------------------------------------------------|---------------------------------------------|¶
| Claude Opus 4.6 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Opus 4.5 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Opus 4.1 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Opus 4 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Sonnet 4.6 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Sonnet 4.5 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Sonnet 4 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Sonnet 3.7 ([deprecated](/docs/en/about-claude/model-deprecations)) | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Haiku 4.5 | `auto`, `none`<hr />`any`, `tool` | 346 tokens<hr />313 tokens |¶
| Claude Haiku 3.5 | `auto`, `none`<hr />`any`, `tool` | 264 tokens<hr />340 tokens |¶
| Claude Opus 3 ([deprecated](/docs/en/about-claude/model-deprecations)) | `auto`, `none`<hr />`any`, `tool` | 530 tokens<hr />281 tokens |¶
| Claude Sonnet 3 | `auto`, `none`<hr />`any`, `tool` | 159 tokens<hr />235 tokens |¶
| Claude Haiku 3 | `auto`, `none`<hr />`any`, `tool` | 264 tokens<hr />340 tokens |¶
¶
These token counts are added to your normal input and output tokens to calculate the total cost of a request.¶
¶
For current per-model prices, refer to the [model pricing](#model-pricing) section.¶
¶
For more information about tool use implementation and best practices, see the [tool use documentation](/docs/en/agents-and-tools/tool-use/overview).¶
¶
### Specific tool pricing¶
¶
#### Bash tool¶
¶
The bash tool adds **245 input tokens** to your API calls.¶
¶
Additional tokens are consumed by:¶
- Command outputs (stdout/stderr)¶
- Error messages¶
- Large file contents¶
¶
See [tool use pricing](#tool-use-pricing) for complete pricing details.¶
¶
#### Code execution tool¶
¶
**Code execution is free when used with web search or web fetch.** When `web_search_20260209` or `web_fetch_20260209` is included in your API request, there are no additional charges for code execution tool calls beyond the standard input and output token costs.¶
¶
When used without these tools, code execution is billed by execution time, tracked separately from token usage:¶
¶
- Execution time has a minimum of 5 minutes¶
- Each organization receives **1,550 free hours** of usage per month¶
- Additional usage beyond 1,550 hours is billed at **$0.05 per hour, per container**¶
- If files are included in the request, execution time is billed even if the tool is not invoked, due to files being preloaded onto the container¶
¶
Code execution usage is tracked in the response:¶
¶
```json¶
"usage": {¶
"input_tokens": 105,¶
"output_tokens": 239,¶
"server_tool_use": {¶
"code_execution_requests": 1¶
}¶
}¶
```¶
¶
#### Text editor tool¶
¶
The text editor tool uses the same pricing structure as other tools used with Claude. It follows the standard input and output token pricing based on the Claude model you're using.¶
¶
In addition to the base tokens, the following additional input tokens are needed for the text editor tool:¶
¶
| Tool | Additional input tokens |¶
| ----------------------------------------- | --------------------------------------- |¶
| `text_editor_20250429` (Claude 4.x) | 700 tokens |¶
| `text_editor_20250124` (Claude Sonnet 3.7 ([deprecated](/docs/en/about-claude/model-deprecations))) | 700 tokens |¶
¶
See [tool use pricing](#tool-use-pricing) for complete pricing details.¶
¶
#### Web search tool¶
¶
Web search usage is charged in addition to token usage:¶
¶
```json¶
"usage": {¶
"input_tokens": 105,¶
"output_tokens": 6039,¶
"cache_read_input_tokens": 7123,¶
"cache_creation_input_tokens": 7345,¶
"server_tool_use": {¶
"web_search_requests": 1¶
}¶
}¶
```¶
¶
Web search is available on the Claude API for **$10 per 1,000 searches**, plus standard token costs for search-generated content. Web search results retrieved throughout a conversation are counted as input tokens, in search iterations executed during a single turn and in subsequent conversation turns.¶
¶
Each web search counts as one use, regardless of the number of results returned. If an error occurs during web search, the web search will not be billed.¶
¶
#### Web fetch tool¶
¶
Web fetch usage has **no additional charges** beyond standard token costs:¶
¶
```json¶
"usage": {¶
"input_tokens": 25039,¶
"output_tokens": 931,¶
"cache_read_input_tokens": 0,¶
"cache_creation_input_tokens": 0,¶
"server_tool_use": {¶
"web_fetch_requests": 1¶
}¶
}¶
```¶
¶
The web fetch tool is available on the Claude API at **no additional cost**. You only pay standard token costs for the fetched content that becomes part of your conversation context.¶
¶
To protect against inadvertently fetching large content that would consume excessive tokens, use the `max_content_tokens` parameter to set appropriate limits based on your use case and budget considerations.¶
¶
Example token usage for typical content:¶
- Average web page (10 kB): ~2,500 tokens¶
- Large documentation page (100 kB): ~25,000 tokens¶
- Research paper PDF (500 kB): ~125,000 tokens¶
¶
#### Computer use tool¶
¶
Computer use follows the standard [tool use pricing](/docs/en/agents-and-tools/tool-use/overview#pricing). When using the computer use tool:¶
¶
**System prompt overhead**: The computer use beta adds 466-499 tokens to the system prompt¶
¶
**Computer use tool token usage**:¶
| Model | Input tokens per tool definition |¶
| ----- | -------------------------------- |¶
| Claude 4.x models | 735 tokens |¶
| Claude Sonnet 3.7 ([deprecated](/docs/en/about-claude/model-deprecations)) | 735 tokens |¶
¶
**Additional token consumption**:¶
- Screenshot images (see [Vision pricing](/docs/en/build-with-claude/vision))¶
- Tool execution results returned to Claude¶
¶
<Note>¶
If you're also using bash or text editor tools alongside computer use, those tools have their own token costs as documented in their respective pages.¶
</Note>¶
¶
## Agent use case pricing examples¶
¶
Understanding pricing for agent applications is crucial when building with Claude. These real-world examples can help you estimate costs for different agent patterns.¶
¶
### Customer support agent example¶
¶
When building a customer support agent, here's how costs might break down:¶
¶
<Note>¶
Example calculation for processing 10,000 support tickets:¶
- Average ~3,700 tokens per conversation¶
- Using Claude Opus 4.6 at $5/MTok input, $25/MTok output¶
- Total cost: ~$37.00 per 10,000 tickets¶
</Note>¶
¶
For a detailed walkthrough of this calculation, see the [customer support agent guide](/docs/en/about-claude/use-case-guides/customer-support-chat).¶
¶
### General agent workflow pricing¶
¶
For more complex agent architectures with multiple steps:¶
¶
1. **Initial request processing**¶
- Typical input: 500-1,000 tokens¶
- Processing cost: ~$0.003 per request¶
¶
2. **Memory and context retrieval**¶
- Retrieved context: 2,000-5,000 tokens¶
- Cost per retrieval: ~$0.015 per operation¶
¶
3. **Action planning and execution**¶
- Planning tokens: 1,000-2,000¶
- Execution feedback: 500-1,000¶
- Combined cost: ~$0.045 per action¶
¶
For a comprehensive guide on agent pricing patterns, see the [agent use cases guide](/docs/en/about-claude/use-case-guides).¶
¶
### Cost optimization strategies¶
¶
When building agents with Claude:¶
¶
1. **Use appropriate models:** Choose Haiku for simple tasks, Sonnet for complex reasoning¶
2. **Implement prompt caching:** Reduce costs for repeated context¶
3. **Batch operations:** Use the Batch API for non-time-sensitive tasks¶
4. **Monitor usage patterns:** Track token consumption to identify optimization opportunities¶
¶
<Tip>¶
For high-volume agent applications, contact the [enterprise sales team](https://claude.com/contact-sales) for custom pricing arrangements.¶
</Tip>¶
¶
## Additional pricing considerations¶
¶
### Rate limits¶
¶
Rate limits vary by usage tier and affect how many requests you can make:¶
¶
- **Tier 1:** Entry-level usage with basic limits¶
- **Tier 2:** Increased limits for growing applications¶
- **Tier 3:** Higher limits for established applications¶
- **Tier 4:** Maximum standard limits¶
- **Enterprise:** Custom limits available¶
¶
For detailed rate limit information, see the [rate limits documentation](/docs/en/api/rate-limits).¶
¶
For higher rate limits or custom pricing arrangements, [contact the sales team](https://claude.com/contact-sales).¶
¶
### Volume discounts¶
¶
Volume discounts may be available for high-volume users. These are negotiated on a case-by-case basis.¶
¶
- Standard tiers use the pricing shown above¶
- Enterprise customers can [contact sales](mailto:sales@anthropic.com) for custom pricing¶
- Academic and research discounts may be available¶
¶
### Enterprise pricing¶
¶
For enterprise customers with specific needs:¶
¶
- Custom rate limits¶
- Volume discounts¶
- Dedicated support¶
- Custom terms¶
¶
Contact the sales team at [sales@anthropic.com](mailto:sales@anthropic.com) or through the [Claude Console](/settings/limits) to discuss enterprise pricing options.¶
¶
## Billing and payment¶
¶
- Billing is based on actual monthly usage¶
- All payments are in USD¶
- Credit card and invoicing options available¶
- Usage tracking available in the [Claude Console](/)¶
¶
## Frequently asked questions¶
¶
**How is token usage calculated?**¶
¶
Tokens are pieces of text that models process. As a rough estimate, 1 token is approximately 4 characters or 0.75 words in English. The exact count varies by language and content type.¶
¶
**Are there free tiers or trials?**¶
¶
New users receive a small amount of free credits to test the API. [Contact sales](mailto:sales@anthropic.com) for information about extended trials for enterprise evaluation.¶
¶
**How do discounts stack?**¶
¶
Batch API and prompt caching discounts can be combined. For example, using both features together provides significant cost savings compared to standard API calls. See [prompt caching pricing](#prompt-caching) for how the multipliers interact.¶
¶
**What payment methods are accepted?**¶
¶
Major credit cards are accepted for standard accounts. Enterprise customers can arrange invoicing and other payment methods.¶
¶
For additional questions about pricing, contact [support@anthropic.com](mailto:support@anthropic.com).