# Sonnet Pricing Update

> Source: <https://platform.claude.com/docs/en/about-claude/pricing>
> Published: 2026-08-12 06:45:45+00:00

We use cookies to deliver and improve our services, analyze site usage, and if you agree, to customize or personalize your experience and market our services to you. You can read our Cookie Policy [here](https://www.anthropic.com/legal/cookies).

This page provides detailed pricing information for Anthropic's models and features. All prices are in USD.

For the most current pricing information, visit [claude.com/pricing](https://claude.com/pricing).

The following table shows pricing for all Claude models:

| Model | Base Input Tokens | 5m Cache Writes | 1h Cache Writes | Cache Hits & Refreshes | Output Tokens |
|---|---|---|---|---|---|
| Claude Fable 5 | $10 / MTok | $12.50 / MTok | $20 / MTok | $1 / MTok | $50 / MTok |
| Claude Mythos 5 (
|

For Claude Platform on AWS pricing, see [Claude Platform on AWS pricing](#claude-platform-on-aws-pricing).

This section covers partner-operated cloud platforms, where the cloud provider invoices you. For Anthropic-operated cloud platforms billed through a marketplace, see [Claude Platform on AWS pricing](#claude-platform-on-aws-pricing) and [Claude in Microsoft Foundry pricing](#claude-in-microsoft-foundry-pricing).

Claude models are available on [Amazon Bedrock](/docs/en/build-with-claude/claude-in-amazon-bedrock) and [Google Cloud](/docs/en/build-with-claude/claude-on-vertex-ai). For official pricing, visit:

[Claude Platform on AWS](/docs/en/build-with-claude/claude-platform-on-aws) bills through AWS Marketplace using Claude Consumption Units (CCUs). Anthropic rates your token usage in USD at standard per-model, per-feature rates, applies any negotiated discount, converts the result to CCUs at $0.01 per CCU, and reports the CCU quantity to AWS Marketplace hourly. Your AWS bill shows a single CCU line item.

| Concept | Details |
|---|---|
Billing unit | Claude Consumption Unit (CCU) |
CCU price | $0.01 per CCU (fixed; discounts apply at token-to-CCU conversion, not to the CCU price) |
Conversion | Token usage rated in USD at standard per-model, per-feature rates (same as
|

For Claude 4.6 and later models, using `inference_geo: "us"`

applies a 1.1x pricing multiplier. `inference_geo: "global"`

(default) uses standard pricing. See [Data residency](/docs/en/manage-claude/data-residency) for details.

When you sign up on the AWS Console **Claude Platform on AWS** service page, the AWS Console looks up any private offer associated with your account and prompts you to accept it in AWS Marketplace. Contact your Anthropic account representative for private offer terms.

[Claude in Microsoft Foundry](/docs/en/build-with-claude/claude-in-microsoft-foundry) bills through the Azure Marketplace using Claude Consumption Units (CCUs). Anthropic rates your token usage in USD at standard per-model, per-feature rates, applies any negotiated discount, converts the result to CCUs at $0.01 per CCU, and reports the CCU quantity to the Azure Marketplace hourly. Your Azure bill shows a single CCU line item.

| Concept | Details |
|---|---|
Billing unit | Claude Consumption Unit (CCU) |
CCU price | $0.01 per CCU (fixed; discounts apply at token-to-CCU conversion, not to the CCU price) |
Conversion | Token usage rated in USD at standard per-model, per-feature rates (same as
|

Deployments hosted on Azure can use the US Data Zone Standard deployment type, which keeps inference within the United States. This is equivalent to `inference_geo: "us"`

on the Claude API and applies the same 1.1x pricing multiplier. See [Data residency](/docs/en/manage-claude/data-residency) for details.

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:

`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.`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 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 and data residency.

For implementation details, supported models, and code examples, see [Prompt caching](/docs/en/build-with-claude/prompt-caching).

For Claude 4.6 and later models, specifying US-only inference through 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 (first-party) and Claude Platform on AWS. On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments that use the US Data Zone Standard deployment type (see [Inference geography](#foundry-inference-geography)). Partner-operated platforms (Bedrock and Google Cloud) have independent regional pricing. See [Bedrock](https://aws.amazon.com/bedrock/pricing/) and [Google Cloud](https://cloud.google.com/vertex-ai/generative-ai/pricing#claude-models) for details. Earlier models do not support the `inference_geo`

parameter and always use standard pricing; requests that include the parameter on these models return a 400 error.

For more information, see [Data residency](/docs/en/manage-claude/data-residency).

[Fast mode](/docs/en/build-with-claude/fast-mode), in research preview, provides significantly faster output for Claude Opus 5 and Claude Opus 4.8 at premium pricing. Fast mode pricing applies across the full context window, including requests over 200k input tokens. Fast mode is available on the Claude API (first-party) only; it is not available on Claude Platform on AWS or partner-operated cloud platforms.

| Model | Input | Output |
|---|---|---|
| Claude Opus 5 / Claude Opus 4.8 | $10 / MTok | $50 / MTok |

Fast mode is not available on Claude Opus 4.7 (requests with `speed: "fast"`

return an error) or Claude Opus 4.6 (requests run at standard speed and are billed at standard rates). See [Fast mode](/docs/en/build-with-claude/fast-mode#supported-models).

Fast mode pricing stacks with other pricing modifiers:

Fast mode is not available with the [Batch API](#batch-processing).

For more information, see [Fast mode](/docs/en/build-with-claude/fast-mode).

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 Fable 5 | $5 / MTok | $25 / MTok |
| Claude Mythos 5 (
|

For more information about batch processing, see [Batch processing](/docs/en/build-with-claude/batch-processing).

Claude 4.6 and later models and [Claude Mythos Preview](https://anthropic.com/glasswing) 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.

Tool use requests are priced based on:

`tools`

parameter)Client-side tools are priced the same as any other Claude API request, although server-side tools can incur additional charges based on their specific usage.

The additional tokens from tool use come from:

`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 requestsWhen you use `tools`

, the API also automatically includes a special system prompt for the model that enables tool use. The number of tool use tokens required for each model is listed in the following table (excluding the additional tokens listed earlier). 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 5 | `auto` , `none` `any` , `tool` | 286 tokens 406 tokens |
| Claude Opus 4.8 | `auto` , `none` `any` , `tool` | 290 tokens 410 tokens |
| Claude Opus 4.7 | `auto` , `none` `any` , `tool` | 675 tokens 804 tokens |
| Claude Opus 4.6 | `auto` , `none` `any` , `tool` | 497 tokens 589 tokens |
| Claude Opus 4.5 | `auto` , `none` `any` , `tool` | 496 tokens 588 tokens |
| Claude Opus 4.1 (
|

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

`auto`

, `none`

`any`

, `tool`

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 [Tool use](/docs/en/agents-and-tools/tool-use/overview).

The bash tool definition adds the following input tokens to your request. This is in addition to the per-model [tool use system prompt](/docs/en/agents-and-tools/tool-use/overview#pricing) that applies whenever any tool is present.

| Model | Additional input tokens |
|---|---|
| Claude Opus 5, Claude Opus 4.8, and Claude Opus 4.7 | 325 tokens |
| Claude Opus 4.6, Claude Sonnet 4.6, and earlier | 244 tokens |

Additional tokens are consumed by:

See [tool use pricing](#tool-use-pricing) for complete pricing details.

**Code execution is free when used with web search or web fetch.** When `web_search_20260209`

(or later) or `web_fetch_20260209`

(or later) 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:

Code execution usage is tracked in the response:

```
{
  "usage": {
    "input_tokens": 105,
    "output_tokens": 239,
    "server_tool_use": {
      "code_execution_requests": 1
    }
  }
}
```

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 |

See [tool use pricing](#tool-use-pricing) for complete pricing details.

Web search usage is charged in addition to token usage:

```
{
  "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 usage has **no additional charges** beyond standard token costs:

```
{
  "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:

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 |

**Additional token consumption:**

[Claude Managed Agents](/docs/en/managed-agents/overview) is billed on two dimensions: tokens and session runtime.

All tokens consumed by a Claude Managed Agents session are billed at the rates shown in [Model pricing](#model-pricing). [Prompt caching](#prompt-caching) multipliers apply identically. Web search triggered inside a session incurs the standard $10 per 1,000 searches. On [Claude Platform on AWS](#claude-platform-on-aws-pricing), session token and runtime charges convert to Claude Consumption Units at the standard rate. [Fast mode](#fast-mode-pricing) premium pricing applies when an agent's `model.speed`

is set to `"fast"`

.

The [data residency multiplier](#data-residency-pricing) also applies: when an agent's `model.inference_geo`

is pinned to `"us"`

, tokens consumed by sessions running that agent are billed at 1.1x the standard rates, the same multiplier that applies to US-only inference on the Messages API.

The following Messages API modifiers do **not** apply to Claude Managed Agents sessions:

| Modifier | Why it doesn't apply |
|---|---|
|

| SKU | Rate | Metering |
|---|---|---|
| Session runtime | $0.08 per session-hour | `running` status duration |

Runtime is measured to the millisecond and accrues only while the session's status is `running`

. Time spent `idle`

(waiting for your next message or a tool confirmation), `rescheduling`

, or `terminated`

does not count toward runtime.

A one-hour coding session using Claude Opus 5 that consumes 50,000 input tokens and 15,000 output tokens:

| Line item | Calculation | Cost |
|---|---|---|
| Input tokens | 50,000 × $5 / 1,000,000 | $0.25 |
| Output tokens | 15,000 × $25 / 1,000,000 | $0.375 |
| Session runtime | 1.0 hour × $0.08 | $0.08 |
Total | $0.705 |

If prompt caching is active and 40,000 of the input tokens are cache reads:

| Line item | Calculation | Cost |
|---|---|---|
| Uncached input tokens | 10,000 × $5 / 1,000,000 | $0.05 |
| Cache read tokens | 40,000 × $5 × 0.1 / 1,000,000 | $0.02 |
| Output tokens | 15,000 × $25 / 1,000,000 | $0.375 |
| Session runtime | 1.0 hour × $0.08 | $0.08 |
Total | $0.525 |

For a detailed walkthrough of this calculation, see the [customer support agent guide](/docs/en/about-claude/use-case-guides/customer-support-chat).

When building agents with Claude:

Rate limits vary by usage tier and affect how many requests you can make:

For detailed rate limit information, see [Rate limits](/docs/en/api/rate-limits).

For limits beyond the Scale tier or custom pricing arrangements, [contact the sales team](https://claude.com/contact-sales).

Volume discounts may be available for high-volume users. These are negotiated on a case-by-case basis.

For enterprise customers with specific needs:

Contact the sales team at [[email protected]](/cdn-cgi/l/email-protection#4231232e273102232c362a302d322b216c212d2f) or through the [Claude Console](/settings/limits) to discuss enterprise pricing options.

**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](/cdn-cgi/l/email-protection#14677578716754757a607c667b647d773a777b79) 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 [[email protected]](/cdn-cgi/l/email-protection#8efdfbfefee1fcfaceefe0fae6fce1fee7eda0ede1e3).

Was this page helpful?