Anthropic: Claude Opus 4.7

anthropic/claude-opus-4.7

Released Apr 16, 20261,000,000 context$5/M input tokens$25/M output tokens

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.

Beyond coding, Opus 4.7 brings improved knowledge work capabilities - from drafting documents and building presentations to analyzing data. It maintains coherence across very long outputs and extended sessions, making it a strong default for tasks that require persistence, judgment, and follow-through.

For users upgrading from earlier Opus versions, see our official migration guide here

Providers for Claude Opus 4.7

OpenRouter routes requests to the best providers that are able to handle your prompt size and parameters, with fallbacks to maximize uptime.

Performance for Claude Opus 4.7

Compare different providers across OpenRouter

Effective Pricing for Claude Opus 4.7

Actual cost per million tokens across providers over the past hour

Apps using Claude Opus 4.7

Top public apps this month

Recent activity on Claude Opus 4.7

Total usage per day on OpenRouter

Prompt

2.99B

Completion

48.9M

Reasoning

1.21M

Prompt tokens measure input size. Reasoning tokens show internal thinking before a response. Completion tokens reflect total output length.

Uptime stats for Claude Opus 4.7

Uptime stats for Claude Opus 4.7 across all providers

Sample code and API for Claude Opus 4.7

OpenRouter normalizes requests and responses across providers for you.

OpenRouter supports reasoning-enabled models that can show their step-by-step thinking process. Use the reasoning parameter in your request to enable reasoning, and access the reasoning_details array in the response to see the model's internal reasoning before the final answer. When continuing a conversation, preserve the complete reasoning_details when passing messages back to the model so it can continue reasoning from where it left off. Learn more about reasoning tokens.

In the examples below, the OpenRouter-specific headers are optional. Setting them allows your app to appear on the OpenRouter leaderboards.

Using third-party SDKs

For information about using third-party SDKs and frameworks with OpenRouter, please see our frameworks documentation.

See the Request docs for all possible fields, and Parameters for explanations of specific sampling parameters.