{"slug": "sonnet-pricing-update", "title": "Sonnet Pricing Update", "summary": "Anthropic updated its Claude model pricing, introducing Claude Fable 5 at $10 per million input tokens, $12.50 per million for 5-minute cache writes, $20 per million for 1-hour cache writes, $1 per million for cache hits and refreshes, and $50 per million output tokens. The update also details Claude Platform on AWS and Claude in Microsoft Foundry billing via Claude Consumption Units at $0.01 per CCU, with a 1.1x pricing multiplier for US data zone deployments.", "body_md": "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).\n\nThis page provides detailed pricing information for Anthropic's models and features. All prices are in USD.\n\nFor the most current pricing information, visit [claude.com/pricing](https://claude.com/pricing).\n\nThe following table shows pricing for all Claude models:\n\n| Model | Base Input Tokens | 5m Cache Writes | 1h Cache Writes | Cache Hits & Refreshes | Output Tokens |\n|---|---|---|---|---|---|\n| Claude Fable 5 | $10 / MTok | $12.50 / MTok | $20 / MTok | $1 / MTok | $50 / MTok |\n| Claude Mythos 5 (\n|\n\nFor Claude Platform on AWS pricing, see [Claude Platform on AWS pricing](#claude-platform-on-aws-pricing).\n\nThis 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).\n\nClaude 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:\n\n[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.\n\n| Concept | Details |\n|---|---|\nBilling unit | Claude Consumption Unit (CCU) |\nCCU price | $0.01 per CCU (fixed; discounts apply at token-to-CCU conversion, not to the CCU price) |\nConversion | Token usage rated in USD at standard per-model, per-feature rates (same as\n|\n\nFor Claude 4.6 and later models, using `inference_geo: \"us\"`\n\napplies a 1.1x pricing multiplier. `inference_geo: \"global\"`\n\n(default) uses standard pricing. See [Data residency](/docs/en/manage-claude/data-residency) for details.\n\nWhen 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.\n\n[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.\n\n| Concept | Details |\n|---|---|\nBilling unit | Claude Consumption Unit (CCU) |\nCCU price | $0.01 per CCU (fixed; discounts apply at token-to-CCU conversion, not to the CCU price) |\nConversion | Token usage rated in USD at standard per-model, per-feature rates (same as\n|\n\nDeployments 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\"`\n\non the Claude API and applies the same 1.1x pricing multiplier. See [Data residency](/docs/en/manage-claude/data-residency) for details.\n\nPrompt 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.\n\nThere are two ways to enable prompt caching:\n\n`cache_control`\n\nfield 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`\n\ndirectly 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:\n\n| Cache operation | Multiplier | Duration |\n|---|---|---|\n| 5-minute cache write | 1.25x base input price | Cache valid for 5 minutes |\n| 1-hour cache write | 2x base input price | Cache valid for 1 hour |\n| Cache read (hit) | 0.1x base input price | Same duration as the preceding write |\n\nCache 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).\n\nThese multipliers stack with other pricing modifiers, including the Batch API discount and data residency.\n\nFor implementation details, supported models, and code examples, see [Prompt caching](/docs/en/build-with-claude/prompt-caching).\n\nFor Claude 4.6 and later models, specifying US-only inference through the `inference_geo`\n\nparameter 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.\n\nThis 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`\n\nparameter and always use standard pricing; requests that include the parameter on these models return a 400 error.\n\nFor more information, see [Data residency](/docs/en/manage-claude/data-residency).\n\n[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.\n\n| Model | Input | Output |\n|---|---|---|\n| Claude Opus 5 / Claude Opus 4.8 | $10 / MTok | $50 / MTok |\n\nFast mode is not available on Claude Opus 4.7 (requests with `speed: \"fast\"`\n\nreturn 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).\n\nFast mode pricing stacks with other pricing modifiers:\n\nFast mode is not available with the [Batch API](#batch-processing).\n\nFor more information, see [Fast mode](/docs/en/build-with-claude/fast-mode).\n\nThe Batch API allows asynchronous processing of large volumes of requests with a 50% discount on both input and output tokens.\n\n| Model | Batch input | Batch output |\n|---|---|---|\n| Claude Fable 5 | $5 / MTok | $25 / MTok |\n| Claude Mythos 5 (\n|\n\nFor more information about batch processing, see [Batch processing](/docs/en/build-with-claude/batch-processing).\n\nClaude 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.\n\nTool use requests are priced based on:\n\n`tools`\n\nparameter)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.\n\nThe additional tokens from tool use come from:\n\n`tools`\n\nparameter in API requests (tool names, descriptions, and schemas)`tool_use`\n\ncontent blocks in API requests and responses`tool_result`\n\ncontent blocks in API requestsWhen you use `tools`\n\n, 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`\n\nare provided, then a tool choice of `none`\n\nuses 0 additional system prompt tokens.\n\n| Model | Tool choice | Tool use system prompt token count |\n|---|---|---|\n| Claude Opus 5 | `auto` , `none` `any` , `tool` | 286 tokens 406 tokens |\n| Claude Opus 4.8 | `auto` , `none` `any` , `tool` | 290 tokens 410 tokens |\n| Claude Opus 4.7 | `auto` , `none` `any` , `tool` | 675 tokens 804 tokens |\n| Claude Opus 4.6 | `auto` , `none` `any` , `tool` | 497 tokens 589 tokens |\n| Claude Opus 4.5 | `auto` , `none` `any` , `tool` | 496 tokens 588 tokens |\n| Claude Opus 4.1 (\n|\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\n`auto`\n\n, `none`\n\n`any`\n\n, `tool`\n\nThese token counts are added to your normal input and output tokens to calculate the total cost of a request.\n\nFor current per-model prices, refer to the [model pricing](#model-pricing) section.\n\nFor more information about tool use implementation and best practices, see [Tool use](/docs/en/agents-and-tools/tool-use/overview).\n\nThe 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.\n\n| Model | Additional input tokens |\n|---|---|\n| Claude Opus 5, Claude Opus 4.8, and Claude Opus 4.7 | 325 tokens |\n| Claude Opus 4.6, Claude Sonnet 4.6, and earlier | 244 tokens |\n\nAdditional tokens are consumed by:\n\nSee [tool use pricing](#tool-use-pricing) for complete pricing details.\n\n**Code execution is free when used with web search or web fetch.** When `web_search_20260209`\n\n(or later) or `web_fetch_20260209`\n\n(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.\n\nWhen used without these tools, code execution is billed by execution time, tracked separately from token usage:\n\nCode execution usage is tracked in the response:\n\n```\n{\n  \"usage\": {\n    \"input_tokens\": 105,\n    \"output_tokens\": 239,\n    \"server_tool_use\": {\n      \"code_execution_requests\": 1\n    }\n  }\n}\n```\n\nThe 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.\n\nIn addition to the base tokens, the following additional input tokens are needed for the text editor tool:\n\n| Tool | Additional input tokens |\n|---|---|\n`text_editor_20250429` (Claude 4.x) | 700 tokens |\n\nSee [tool use pricing](#tool-use-pricing) for complete pricing details.\n\nWeb search usage is charged in addition to token usage:\n\n```\n{\n  \"usage\": {\n    \"input_tokens\": 105,\n    \"output_tokens\": 6039,\n    \"cache_read_input_tokens\": 7123,\n    \"cache_creation_input_tokens\": 7345,\n    \"server_tool_use\": {\n      \"web_search_requests\": 1\n    }\n  }\n}\n```\n\nWeb 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.\n\nEach 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.\n\nWeb fetch usage has **no additional charges** beyond standard token costs:\n\n```\n{\n  \"usage\": {\n    \"input_tokens\": 25039,\n    \"output_tokens\": 931,\n    \"cache_read_input_tokens\": 0,\n    \"cache_creation_input_tokens\": 0,\n    \"server_tool_use\": {\n      \"web_fetch_requests\": 1\n    }\n  }\n}\n```\n\nThe 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.\n\nTo protect against inadvertently fetching large content that would consume excessive tokens, use the `max_content_tokens`\n\nparameter to set appropriate limits based on your use case and budget considerations.\n\nExample token usage for typical content:\n\nComputer use follows the standard [tool use pricing](/docs/en/agents-and-tools/tool-use/overview#pricing). When using the computer use tool:\n\n**System prompt overhead:** The computer use beta adds 466–499 tokens to the system prompt\n\n**Computer use tool token usage:**\n\n| Model | Input tokens per tool definition |\n|---|---|\n| Claude 4.x models | 735 tokens |\n\n**Additional token consumption:**\n\n[Claude Managed Agents](/docs/en/managed-agents/overview) is billed on two dimensions: tokens and session runtime.\n\nAll 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`\n\nis set to `\"fast\"`\n\n.\n\nThe [data residency multiplier](#data-residency-pricing) also applies: when an agent's `model.inference_geo`\n\nis pinned to `\"us\"`\n\n, 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.\n\nThe following Messages API modifiers do **not** apply to Claude Managed Agents sessions:\n\n| Modifier | Why it doesn't apply |\n|---|---|\n|\n\n| SKU | Rate | Metering |\n|---|---|---|\n| Session runtime | $0.08 per session-hour | `running` status duration |\n\nRuntime is measured to the millisecond and accrues only while the session's status is `running`\n\n. Time spent `idle`\n\n(waiting for your next message or a tool confirmation), `rescheduling`\n\n, or `terminated`\n\ndoes not count toward runtime.\n\nA one-hour coding session using Claude Opus 5 that consumes 50,000 input tokens and 15,000 output tokens:\n\n| Line item | Calculation | Cost |\n|---|---|---|\n| Input tokens | 50,000 × $5 / 1,000,000 | $0.25 |\n| Output tokens | 15,000 × $25 / 1,000,000 | $0.375 |\n| Session runtime | 1.0 hour × $0.08 | $0.08 |\nTotal | $0.705 |\n\nIf prompt caching is active and 40,000 of the input tokens are cache reads:\n\n| Line item | Calculation | Cost |\n|---|---|---|\n| Uncached input tokens | 10,000 × $5 / 1,000,000 | $0.05 |\n| Cache read tokens | 40,000 × $5 × 0.1 / 1,000,000 | $0.02 |\n| Output tokens | 15,000 × $25 / 1,000,000 | $0.375 |\n| Session runtime | 1.0 hour × $0.08 | $0.08 |\nTotal | $0.525 |\n\nFor a detailed walkthrough of this calculation, see the [customer support agent guide](/docs/en/about-claude/use-case-guides/customer-support-chat).\n\nWhen building agents with Claude:\n\nRate limits vary by usage tier and affect how many requests you can make:\n\nFor detailed rate limit information, see [Rate limits](/docs/en/api/rate-limits).\n\nFor limits beyond the Scale tier or custom pricing arrangements, [contact the sales team](https://claude.com/contact-sales).\n\nVolume discounts may be available for high-volume users. These are negotiated on a case-by-case basis.\n\nFor enterprise customers with specific needs:\n\nContact the sales team at [[email protected]](/cdn-cgi/l/email-protection#4231232e273102232c362a302d322b216c212d2f) or through the [Claude Console](/settings/limits) to discuss enterprise pricing options.\n\n**How is token usage calculated?**\n\nTokens 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.\n\n**Are there free tiers or trials?**\n\nNew 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.\n\n**How do discounts stack?**\n\nBatch 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.\n\n**What payment methods are accepted?**\n\nMajor credit cards are accepted for standard accounts. Enterprise customers can arrange invoicing and other payment methods.\n\nFor additional questions about pricing, contact [[email protected]](/cdn-cgi/l/email-protection#8efdfbfefee1fcfaceefe0fae6fce1fee7eda0ede1e3).\n\nWas this page helpful?", "url": "https://wpnews.pro/news/sonnet-pricing-update", "canonical_source": "https://platform.claude.com/docs/en/about-claude/pricing", "published_at": "2026-08-12 06:45:45+00:00", "updated_at": "2026-08-12 07:10:51.892760+00:00", "lang": "en", "topics": ["ai-products", "ai-infrastructure"], "entities": ["Anthropic", "Claude Fable 5", "Claude Mythos 5", "Amazon Bedrock", "Google Cloud", "AWS Marketplace", "Azure Marketplace", "Microsoft Foundry"], "alternates": {"html": "https://wpnews.pro/news/sonnet-pricing-update", "markdown": "https://wpnews.pro/news/sonnet-pricing-update.md", "text": "https://wpnews.pro/news/sonnet-pricing-update.txt", "jsonld": "https://wpnews.pro/news/sonnet-pricing-update.jsonld"}}