Anthropic released Claude Opus 5.5 on September 22, 2026. This model is priced at $4 per million input tokens and $20 per million output tokens. It holds an agentic score estimate of 87.9 on BenchLM. This release follows the introduction of Claude Sonnet 5 on June 30, 2026, and Claude Opus 5 on July 24, 2026. These models belong to a lineage of rapid updates throughout 2026, including the Claude 4.5, 4.6, 4.7, and 4.8 series.
The current pricing environment for Anthropic models involves several complex layers. Base token costs vary between the Haiku, Sonnet, and Opus tiers. Users can also apply prompt caching to reduce repeat input costs or use the batch API to receive a 50% discount on both input and output. For high-speed tasks, Opus 4.8 provides a Fast Mode that costs $10 per million input tokens and $50 per million output tokens. This Fast Mode is 3x cheaper than the $30 and $150 rates for Opus 4.7 Fast Mode.
Prompt caching and prefix management
Prompt caching saves the KV cache to reduce the cost of processing the same prefix in multiple requests. A 5-minute cache write costs 1.25x the base input rate. A 1-hour cache write costs 2x the base input rate. Cache reads cost only 0.1x the base input rate. The developer platform team at Anthropic published a guide on September 8, 2026, that describes how to avoid six specific prompting anti-patterns which actively reduce the accuracy of frontier models like Opus 5. You can monitor the hit rate using the usage.cache_read_input_tokens metric in the Claude Console.
The effectiveness of caching depends on the prefix being byte-exact. A single changed character anywhere in the cached region invalidates everything after that character. Changing the effort parameter mid-conversation also breaks the cache because the effort setting renders into the prompt ahead of the content. Volatile values like a timestamp or a unique ID in the system prompt will also cause a cache miss on every request.
Developers should also place stable content, such as tool definitions and the system prompt, at the beginning of the prompt. This layout keeps the growing conversation behind the cache breakpoint. If a user needs to change a setting, they can do so after a compaction event when the cache is already broken.
Reasoning effort and token consumption
The effort parameter controls how much reasoning a model performs before it provides a response. Users can set this to low, high, xhigh, or max. For Claude Opus 4.8, the default effort changed from medium to high. This change can increase per-request costs because higher effort levels use more reasoning tokens. Reasoning tokens are billed at the output price even if the model does not show them to the user.
The relationship between effort and performance is not linear. Higher effort buys accuracy, but the returns diminish as the effort increases. For example, on the Humanity’s Last Exam benchmark, the cost-performance curve flattens after reaching a certain threshold. Increasing effort beyond what a specific task requires only increases latency and token spend.
Users can manage these costs by measuring their own cost-performance curves. A strategy involves starting at a medium effort level and only increasing it if a task fails. Users can also use the /claude-api hillclimb command to automate this process. This command splits evaluation into training and test sets to find the best configuration. It can also use the /claude-api prompt-audit command to identify obsolete instructions.
The impact of new tokenizers
Newer models in the Claude 4 and 5 series use a modified tokenizer. The tokenizer in Claude Opus 4.7 and 4.8 may consume up to 35% more tokens for the same input text than the tokenizer in Claude Opus 4.6. This same effect applies to Claude Sonnet 5 and the Fable 5.1 model. The increased token count affects code, structured data, and non-English text the most.
This change means that even if the per-token rate remains the same, the effective cost per request will rise. A prompt that was cost-effective on an older model might become more expensive on a newer model because the new tokenizer produces more tokens for the same input. Developers must account for this multiplier when migrating workflows to the latest flagship models.
Will the increased token count from newer tokenizers eventually force a change in base pricing for the Opus 5 series?
Computer use toolset technicalities
The computer use toolset is a client toolset that allows Claude to interact with desktop environments. It provides 17 member tools, including screenshot, left_click, type, and zoom. Users must add the toolset to the messages API request using the entry {"type": "computer_toolset_20260801"}. This capability is not available in Claude Managed Agents.
When Claude uses these tools, it responds with tool_useblocks that carry the "toolset_name": "computer" designation. These requests often arrive as batch actions, where the model plans several steps at once. The application must run these calls in order and return a tool_resultblock for every tool_useblock. If an action fails, the application must return "is_error": true for that block.
Security is a concern when Claude interacts with a computer. Developers should run the model in a sandboxed environment, such as a virtual machine or a container, with minimal privileges. Using a dedicated virtual display server like Xvfb helps isolate the model from the main system. Anthropic uses classifiers to scan screenshots for prompt injections, but users should still limit internet access to an allowlist of domains.
Calculating cost per task
Every AI price list lists the cost per token, but this does not reflect the real cost of a completed task. The cost per task formula is the price per token multiplied by the tokens per attempt, multiplied by the inverse of the success rate. This calculation must also include tool fees and any costs from retries.
A failed attempt is billed in full, meaning a model with a low success rate will be much more expensive than a model with a high success rate. For example, if a model has a 50% success rate, the user pays for two attempts to get one successful result. Reasoning tokens add to this cost because they are billed as output tokens.
In agentic workflows, the ratio of input to output tokens often flips. An agent that makes dozens of calls for a single task will re-send the entire conversation history with every step. This makes prompt caching a vital tool for reducing the cost of agentic loops.
Current Claude API model comparison
The following table provides the standard pricing for the current generation of Claude models as of September 2026.
| Model | Input Price / 1M | Output Price / 1M | Context Window |
|---|---|---|---|
| Claude Opus 5.5 | $4.00 | $20.00 | 1,000,000 |
| Claude Fable 5.1 | $10.00 | $50.00 | 1,000,000 |
| Claude Opus 5 | $5.00 | $25.00 | 1,000,000 |
| Claude Sonnet 5 | $2.00 | $10.00 | 1,000,000 |
| Claude Haiku 4.5 | $1.00 | $5.00 | 200,000 |
| Claude Sonnet 4.6 | $3.00 | $15.00 | 200,000 |
Third-party tool usage and subscription limits
Anthropic changed how subscriptions interact with third-party tools on April 4, 2026. Claude Pro and Max subscribers can no longer use their subscription quota through third-party agent tools like OpenClaw. These tools now require pay-as-you-go API billing at standard rates. For instance, using Sonnet 4.6 through a third-party harness costs $3 per million input tokens and $15 per million output tokens.
This change significantly increased costs for heavy users who relied on open-source frameworks. In one case, a user running Opus 4.6 on OpenClaw saw costs jump from a $200 monthly subscription to over $3,000 per month. Anthropic stated that subscriptions were not designed for the continuous, automated demand that these third-party tools generate. The company noted that capacity is a resource they manage through these restrictions.
Before the restriction, OpenClaw was a popular tool with 247,000 GitHub stars and 135,000 running instances. Users who want to continue using third-party tools must budget for separate API invoices. Official tools like the Claude Code CLI and the Claude Desktop app still count against the existing subscription quotas. Cursor remains an official partner and is not affected by this change.
