Primary use stated or inferred cautiously from official documentation.
A
ANTHROPIC / claude-opus-4-5-20251101
Claude Opus 4.5
Previous Opus version focused on code, agents, and computer use, retained for migration and historical comparison.
01 / SUMMARY
The essential
Maximum input capacity when published by the source.
Documented maximum generation limit.
Verified availability channels.
Primary functional family and verified specialties.
Declared terms for API access, model weights, or self-hosting.
02 / TECHNICAL SHEET
Limits and integration
| API ID | claude-opus-4-5-20251101 |
|---|---|
| Model type | Text and reasoning · Code |
| Access model | Paid proprietary |
| License | Proprietary |
| Deployment | Hosted API |
| Release | 24 NOV 2025 |
| Knowledge cutoff | Not published |
| Entrance | Text · Image |
| Exit | Text |
| Context window | 200.000 tokens |
| maximum output | Not published |
| Reasoning | Configurable effort |
| Published tools | Use of tools · Computer use |
| Structured Outings | Not applicable or not published |
| Batch processing | Not published |
| Prompt cache | Not published |
| Fine-tuning | Not published |
| Verified platforms | Claude API · Amazon Bedrock · Google Cloud |
Audit regressions when migrating from the Claude 4 generation.
Check the retirement schedule and use current models for new projects.
03 / CAPABILITIES
What it can do
Orientation
Audit regressions when migrating from the Claude 4 generation.
Context
200,000 tokens · Not published
Tools and integration
Tool use · Computer use
Access
Claude API and associated clouds
Input modalities
TextImage
04 / PRICES
Documented cost
| Concept | Worth | Unit/condition |
|---|---|---|
| Standard input | Not published | Standard API rate |
| Cached input | Not published | Reading reused prefixes |
| Cache write or storage | Not published | The condition varies by provider |
| Standard output | Not published | May include reasoning tokens |
| Batch input | Not published | Asynchronous processing |
| Batch output | Not published | Asynchronous processing |
Consult the primary source: the billing unit depends on the model type and access channel.
i Prices change and may depend on level, region or context length. Check the source before making a decision.
05 / EVALUATIONS
How to read the results
“
A public benchmark provides guidance, but does not replace an evaluation with your data, tools, budget, and error tolerance.
| Benchmark | Result | Metric | Source |
|---|---|---|---|
| Evaluaciones Claude Opus 4.5 | Published | Code, agents, and computer | View source ↗ |
Inferama only highlights a “best result” when the metric, test set, configuration, and date allow for an equivalent comparison. The supplier's figures are presented as claims from its own source.
06 / VERSIONS
Chronology
Claude Opus 4.5
Version added to Inferama's verified catalog.
ANALYSIS
Related analysis
Claude Opus 4.5 for Long Tasks: Calculate the Cost per Completed Job
A price per million tokens is not enough to budget a multi-step workflow. Learn how to add up input, output, cache, retries, and review, and set limits before you run it.
25 Sep 2026 ↗
Claude Opus 4.5: How to Attribute an Improvement in Long Tasks to the Model Rather Than the Harness
An observed improvement with Claude Opus 4.5 may come from the model, but it may also result from changes to context, tools, retries, or the verifier. This protocol helps separate those causes before expanding a deployment.
23 Sep 2026 ↗
Claude Opus 4.5 vs Claude Sonnet 4.5: when to pay more to fix code issues—and when not to
The useful comparison between Claude Opus 4.5 and Claude Sonnet 4.5 is not a general verdict on capability. It is an operational decision: which one lowers the total cost per correctly resolved, reviewed, and accepted issue in a specific repository. This guide proposes a reproducible protocol for measuring that outcome with frozen tickets, tests, blind human review, and complete costs.
22 Sep 2026 ↗07 / SOURCES