Claude Opus 5 Released: API Pricing, Fast Mode, Performance, and Opus 4.8 Migration Guide

Anthropic releases Claude Opus 5 on July 24, 2026. It is not simply pushing the benchmark score up a bit, but trying to achieve a more practical balance between cutting-edge capabilities, task costs and autonomous working capabilities: officials say its capabilities are close to Claude Fable 5, but the price is only half the latter; compared with Opus 4.8, the base API unit price remains unchanged.

For developers, the most immediate change is that new model identifiers are now available:

1

claude-opus-5

This article not only lists the release data, but also answers more practical questions: whether it is worth upgrading from Opus 4.8, how much a typical API request costs, what scenarios Fast Mode is suitable for, and how the fallback mechanism after the security classifier is triggered will affect production systems.

Quick Answer: Is Claude Opus 5 worth upgrading?

If your tasks include long-link programming, cross-tool operations, complex fault location, scientific research analysis, or require active model verification results, Opus 5 deserves to be prioritized for a round of regression testing. Its advantage is not just in the quality of the answer once, but in the ability to formulate steps, call tools, find errors and continue to correct them.

If your application is primarily short text classification, fixed-format extraction, or cost-sensitive, high-concurrency requests, you shouldn’t just switch just because of the “new model.” First use the existing real traffic to establish a test set, compare the success rate, output token, end-to-end time consumption and cost of each successful task, and then decide whether to migrate.

You can remember four conclusions first:

1. The API model ID is claude-opus-5.
2. The basic price is US$5 per million input tokens and US$25 per million output tokens, the same as Opus 4.8.
3. Fast Mode is approximately 2.5 times faster than Default Mode, but costs 2 times the base rate.
4. Opus 5 is available in Claude web client, Claude Code, Cowork and API, but the default location is different in different subscription plans.

Where Claude Opus 5 fits

Anthropic describes the Opus 5 as a more “thoughtful and proactive” model in the release notes. The initiative here is not about performing dangerous actions without permission, but when faced with an open task, being able to complete the necessary steps, create test tools and check your own results.

Several official cases illustrate this change:

• Completing the computer vision pipeline in FreeCAD instead of just generating an isolated piece of code;
• Locate the root cause of a package manager problem instead of just reporting an error on the surface;
• Build trading market data sources and create your own test tools to verify behavior.

Such tasks have one thing in common: the goals given by the user are often incomplete, and the model must maintain state between multiple steps and determine when validation is needed. For Claude Code, internal R&D agents and desktop automation, this is more valuable than a single Q&A score.

How does it compare with Opus 4.8, Fable 5, Mythos 5?

According to Anthropic’s official positioning, it can be understood as follows:

This chart is not a substitute for your own testing. In particular, conclusions such as “close” and “leading” rely on specific benchmarks, effort levels, and tool environments, and cannot be directly equated to the effects in all business scenarios.

What performance improvements have been officially announced?

Anthropic publishes results covering agent tasks, programming, computer operations, scientific research, and visual output.

1. Agents and real work tasks

On Frontier-Bench v0.1, Opus 5 outperforms Opus 4.8 by more than twice while costing less per task. Anthropic also said that Opus 5 achieved new best results on Frontier-Bench and GDPval-AA.

These benchmarks focus more on completing the entire task rather than answering a static question, so they have certain reference value for agent applications. But production environments should also record the number of retries after a failure, because a more expensive model that reduces two retries at a time may end up being cheaper.

2. Programming and tool usage

At the highest effort settings of CursorBench 3.2, Opus 5 was only 0.5% shy of Fable 5’s best result, at about half the cost per task.

Officials also emphasized the model’s ability to handle complex tool chains. When migrating a Claude Code workflow, it is recommended to focus on testing the following types of tasks:

• Track bugs across multiple files;
• Locate the root cause after reading the log and perform additional tests;
• Perform build, test and format check after modifying the code;
• Identify constraints when requirements are incomplete rather than committing implementation prematurely;
• Operation processes that require continuous invocation of multiple MCP tools.

3. Computer operation and automation

In OSWorld 2.0, the Opus 5 outperformed other models at a similar cost; officials say it beat the Fable 5’s best result at slightly more than one-third the cost.

On Zapier AutomationBench, Opus 5 scores approximately 1.5 times higher than the next best model for the same task cost. Even with the lowest effort level, it still accomplished the most tasks.

This means that low effort levels are not necessarily just for simple chat. For well-structured automation tasks, it may become a practical option for controlling tokens and latency.

4. Scientific research and visual tasks

Anthropic says the Opus 5 outperforms the Opus 4.8 in all life sciences tests. Among them, the internal organic chemistry evaluation increased by 10.2 percentage points, and the protein variation evaluation increased by 7.7 percentage points.

Additionally, web pages, slideshows, and other visuals generated by the model have been improved. However these are still reviews and examples provided by the publisher. When it comes to scientific research conclusions, medical information or experimental design, manual review and source verification must be retained, and higher benchmark scores cannot be regarded as a guarantee of factual correctness.

Claude Opus 5 API pricing

The base API prices for Opus 5 are as follows:

Above are the base prices given in the release notes. Note that caching, batch processing or cloud platform channels may adopt different billing rules, and the official budget should still be based on the billing instructions of the calling channel at the time.

How much does a request cost approximately?

Assume that a long task uses cumulatively:

• Enter 1 million tokens;
• Output 200,000 tokens.

The base fee for the default model is:

1
2
3

输入：1 × 5 美元 = 5 美元
输出：0.2 × 25 美元 = 5 美元
合计：10 美元

If the same token usage is calculated at twice the rate of Fast Mode, it will be about $20.

Real agent tasks cannot be estimated by just a single call. A more useful metric is “cost per successful task”:

1

每个成功任务成本 = 总调用费用 ÷ 最终成功完成的任务数

If a cheap model retries frequently and requires manual takeover, the final cost may be higher than Opus 5; conversely, using Opus 5 for simple tasks may not yield enough benefits.

Calling Claude Opus 5 through the API

curl example

First put the API Key into the environment variable and then call the Messages API. Don’t write real keys into scripts or commit to Git repositories.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16

export ANTHROPIC_API_KEY="your-api-key"

curl https://api.anthropic.com/v1/messages \
  --header "x-api-key: $ANTHROPIC_API_KEY" \
  --header "anthropic-version: 2023-06-01" \
  --header "content-type: application/json" \
  --data '{
    "model": "claude-opus-5",
    "max_tokens": 1024,
    "messages": [
      {
        "role": "user",
        "content": "分析这个服务的错误日志，给出根因、验证步骤和最小修复方案。"
      }
    ]
  }'

In Windows PowerShell, you can first set the current session environment variables:

1

$env:ANTHROPIC_API_KEY = "your-api-key"

Then use the Anthropic SDK, or construct the request according to the current official documentation. Environment variables only take effect for the current PowerShell session and are more suitable for temporary testing.

Python SDK Example

Install SDK:

1

python -m pip install -U anthropic

Create a minimal calling script:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

from anthropic import Anthropic

client = Anthropic()

message = client.messages.create(
    model="claude-opus-5",
    max_tokens=1024,
    messages=[
        {
            "role": "user",
            "content": (
                "检查下面的部署故障。先列假设，再给验证命令；"
                "没有证据时不要直接修改配置。"
            ),
        }
    ],
)

print(message.content[0].text)
print(message.usage)

Production environments should at least additionally record:

• The model ID requested;
• Input and output tokens;
• Total time taken and first token delay;
• Number of tool calls and reasons for failure;
• Whether model rollback occurs;
• Whether the final task is taken over manually.

Simply logging an HTTP 200 is not a sufficient measure of the success of the proxy task.

What scenarios is Fast Mode suitable for?

Opus 5’s Fast Mode is about 2.5 times faster than the default mode and costs 2 times the base rate. This mode is available with Claude Platform and is also available with Claude Code via usage credits.

Scenarios suitable for testing Fast Mode first include:

• Interactive Claude Code sessions where developers are waiting;
• Online accident analysis that requires rapid iteration;
• Demonstrations, pair programming and real-time tool manipulation;
• Processes where the impact of delay on business value is higher than the cost of a single token.

Scenarios that are not suitable for enabling by default include:

• Nightly batch processing;
• Offline code reviews that can be queued to run;
• Large-scale low-priority data sorting;
• An agent cycle where fee caps and monitoring have not yet been established.

It is recommended to set independent budget tags for Fast Mode and compare P50, P95 latency and cost per successful task. Turning it on for all requests just because you see “2.5 times faster” usually doesn’t lead to an optimal cost structure.

How should you use effort settings?

Opus 5 provides different effort settings to choose between intelligence level, token usage, latency and cost. Anthropic’s published data shows that low effort is still competitive in partially automated benchmarks, while the highest effort is more suitable for approaching the upper limit of model capabilities.

A layered strategy can be used:

The specific parameter names and available ranges may be updated with the SDK or platform, and the request fields should not be guessed based on the release. When accessing, please refer to the official documentation of the API version used.

Migrating from Claude Opus 4.8 to Opus 5

Don’t just replace the model string and put it all online immediately. A more robust migration process is as follows.

Step 1: Freeze a real-world test set

Select 30 to 100 masked tasks from the production log, covering:

• Normal success cases;
• Cases that once needed to be retried;
• Tool call failure cases;
• Long context and high output tasks;
• Legitimate tasks that may trigger security classifiers.

The test set should retain expected results or manual scoring standards, otherwise we can only compare writing styles but not task success rates.

Step 2: Modify only the model ID

First keep the prompt word, tool definition, maximum output length and timeout unchanged, and switch the model to:

1

claude-opus-5

This separates model changes from other configuration changes. If the prompt word and tool schema are rewritten at the same time, it will be difficult to locate the cause when regression occurs.

Step 3: Compare four groups of metrics

At least compare:

1. Final mission success rate;
2. Input, output and total token;
3. P50, P95 end-to-end delay;
4. Actual cost per successful mission.

Agent tasks should also separately record the number of tool calls, the number of invalid cycles, and the manual takeover rate.

Step 4: Recalibrate your prompts

Opus 5 is more proactive, and the large number of repeated instructions of “please continue checking” and “please verify yourself” in the old prompt words may no longer be necessary. Redundancy requirements can be phased out, but business boundaries must be preserved, for example:

• No deployment without approval;
• Production data must not be deleted;
• Export evidence before modification;
• Keys and personal information are not allowed to enter the log;
• High-risk operations must wait for manual confirmation.

Increased initiative does not mean expanded scope of authority.

Step 5: Roll out gradually and keep a rollback path

First cut a small amount of traffic to Opus 5, and then gradually expand. Fallback conditions can include:

• The error rate exceeds the threshold;
• P95 latency significantly worsened;
• The cost of a single task exceeds the budget;
• Repeated loops occur in tool calls;
• The security classifier fallback ratio increased abnormally.

The rollback strategy itself must also be tested, and you cannot wait for the production request to be triggered before confirming whether the log and response formats are compatible.

Two API Beta updates

Anthropic also introduced two API beta capabilities that work with Opus 5.

Change tools mid-conversation

Apps can change available tools in the middle of a conversation without invalidating the prompt cache. This is useful for long-running agents: the system can load databases, browsers, or deployment tools by task phase, without having to cram all the tool definitions into the context from the beginning.

Potential benefits include:

• Reduce the interference of irrelevant tools on model selection;
• Keep prompt cache to reduce the cost of repeated context;
• Dynamically open tools based on permissions and task status;
• Narrow the exposure window for high-risk tools.

Automatic model fallback after a classifier is triggered

The API can automatically switch to another model after a security classifier flags the request. The default settings select the best alternative model currently available, and fallback strategies can also be configured based on business needs.

When accessing this feature, the “actual response model” should be incorporated into observability. Otherwise the application sees the request succeed but has no idea why there are differences in output style, latency or capabilities for the same test set.

How will security mechanisms affect developers?

Anthropic said Opus 5 had an overall misconduct score of 2.3 in automated alignment audits, the lowest among recent models. At the same time, officials believe it is not pushing the forefront of high-risk dual-use capabilities, lagging behind Mythos 5 in biological and offensive cybersecurity.

The boundaries of cybersecurity scenarios are particularly noteworthy:

• Source code vulnerability discovery can be allowed;
• Binary vulnerability scanning, penetration testing and exploit generation may be blocked;
• Opus 5’s vulnerability discovery capabilities have improved, but vulnerability exploitation development is still significantly behind Mythos 5;
• The new classifier is expected to require approximately 85% less intervention than Fable 5.

In Claude.ai, Claude Code, and Cowork, flagged requests fall back to Opus 4.8 by default. API users can also enable fallback. Users in the Claude Verified Participants program can access capabilities with fewer restrictions.

The most important thing for the average development team is not to try to bypass classifiers, but to distinguish legitimate defensive tasks and provide clear user prompts and manual processing paths for blocked or rolled back requests.

How to choose Claude Pro, Max, Claude Code and API?

If you are just evaluating output quality, you can first create a test case in the Claude application; if you want to measure tokens, tool calls, error rates, and costs, you should use an API or an existing engineering evaluation framework.

Pre-launch checklist

• The model ID has been changed to claude-opus-5, and other environments have not been changed by mistake;
• API Key is provided through environment variables or key management services;
• Build a regression test set using real, desensitized production tasks;
• Record input and output tokens, delays, tool calls and success rates;
• Compare costs by “per successful task” instead of just unit price;
• Fast Mode has independent budget and monitoring;
• effort starts with low or medium settings and escalates by failure conditions;
• High-risk tools are still controlled by permissions and manual confirmation;
• Automatic model rollback is visible in the log;
• Preserve Opus 4.8 fallback path during grayscale release.

FAQ

What is the API model name for Claude Opus 5?

The official model ID is claude-opus-5.

Is Opus 5 more expensive than Opus 4.8?

The unit price of the basic API has not been increased and remains US$5 per million input tokens and US$25 per million output tokens. Actual billing however also depends on output length, retries, caching, tool looping and whether Fast Mode is enabled.

Will Fast Mode improve model quality?

The official emphasis is on speed improvement, not higher intelligence. It’s about 2.5x faster than the default mode and costs 2x the base rate. Whether it is worth using should be measured by the business value brought by interaction latency.

Can existing Opus 4.8 prompts be used as-is?

It can often be used as a starting point for migration, but regression testing should not be skipped. Opus 5 is more proactive, and old prompt words may contain redundant steps; tool calls, safety boundaries, and fallback behaviors also need to be revalidated.

Is Opus 5 suitable for cybersecurity jobs?

It can support legitimate source code vulnerability discovery and defensive analysis, but the official classifier limits high-risk requests such as binary scanning, penetration testing, and exploit generation. Relevant teams should design workflows based on authorization scope and anticipate that some requests may be blocked or rolled back.

Summary

The core value of Claude Opus 5 is to provide stronger agent execution, programming, computer operation and scientific research capabilities at the same basic price as Opus 4.8. The gap between it and Fable 5 is already small in some programming reviews, but the task cost is lower; at the same time, Anthropic limits high-risk network security capabilities through classifiers and automatic fallback.

For existing users, the most reasonable action is not to switch in full immediately, but to complete a controlled migration using real tasks: fix the test set, only change the model ID, compare the success rate, delay and cost of each successful task, and then gradually adjust the effort, Fast Mode and prompt words. Only in this way can we judge whether Opus 5 brings higher benchmark scores or quantifiable productivity improvements.

References

• Anthropic: Introducing Claude Opus 5