Opus 4.7 is the next generation of Anthropic's Opus family, built for long-running, asynchronous agents. Building on the coding and agentic strengths of Opus 4.6, it delivers stronger performance on complex, multi-step tasks and more reliable agentic execution across extended workflows. It is especially effective for asynchronous agent pipelines where tasks unfold over time - large codebases, multi-stage debugging, and end-to-end project orchestration.
- By:
- Anthropic
- Input:
- Output:
- Context length:
- 1M
- Max output:
- 128K
- Published:
- 2026-04-16
Providers
Same model, different providers. Automatic routing picks the cheapest healthy one within the same quality tier.
| Provider | ||||
|---|---|---|---|---|
| amazon-bedrock | $5/1M tokens | $25/1M tokens | Read$0.5/1M tokensWrite 5m$6.25/1M tokensWrite 1h$10/1M tokens | 1M |
| 30% offanthropic | $5$3.5/1M tokens | $25$17.5/1M tokens | Read$0.5$0.35/1M tokensWrite 5m$6.25$4.375/1M tokensWrite 1h$10$7/1M tokens | 1M |
| 90% offLowestamazon-kiro | $5$0.5/1M tokens | $25$2.5/1M tokens | Read$0.5$0.05/1M tokensWrite 5m$6.25$0.625/1M tokensWrite 1h$10$1/1M tokens | 1M |
Availability
24 hoursSuccess rate of the requests Amux actually sent to each provider. Client errors are excluded from the denominator — a malformed request isn't the provider's fault.
Throughput
24 hoursAverage output speed on streaming requests, in tokens per second (TPS).
Latency
24 hoursAverage time to first token (TTFT) on streaming requests — how long from sending a request to receiving its first token.
Activity
24 hoursToken usage and cost for this model over time, split by the provider that served each request.
Related models
More models from Anthropic