Claude Opus 4.6

anthropic/claude-opus-4.6

Claude Opus 4.6 is an earlier Opus-generation model built for coding and long-running professional work, with a 1M-token window and text, image and file input. It is priced identically to the newer Opus entries in this catalog.

Input · Account credit
$5.00

per 1M tokens

Cash equivalent $0.50

Output · Account credit
$25.00

per 1M tokens

Cash equivalent $2.50

Context window
1,000,000

tokens · OpenRouter

Input → Output
Text · Image · File→ Text
Model specifications
Sources reviewed: Y-API catalog snapshot:

Choosing this model

Selection advice by Y-API. The checks below are suggested evaluations, not published test results.

Where to start

Use it for workflows that span many steps rather than a single prompt: a repository-wide change, a migration plan that has to stay consistent, or an agent that has to hold context across a long session.

What to watch for

Anthropic publishes no open weights for this model, so there is no model card to cite and no way to inspect the checkpoint behind the API. The catalog price matches newer Opus entries, which makes the older version hard to justify on cost alone.

Model specifications

These are OpenRouter model-level specifications, not a Y-API compatibility test. A particular route may accept fewer input formats, parameters or tokens. Verify the features you need with a small request; a successful text response does not validate vision or tool calling.

Context window
1,000,000 tokens
Input
Text · Image · File
Output
Text
Listed on OpenRouter
Parameters listed by OpenRouter
include_reasoningmax_completion_tokensmax_tokensreasoningreasoning_effortresponse_formatstopstructured_outputstemperaturetool_choicetoolstop_ktop_pverbosity
OpenRouter model page & specifications

API pricing & cost estimate

Estimated credit consumed
$17.50
Estimated cash equivalent
$1.75

Illustrative token budget, not measured usage or a quote. Includes input and output; excludes separate media charges, cache discounts and retries. Include billed reasoning tokens in your output budget where applicable. Actual billing follows usage returned by the service.

$1 paid adds $10 of credit. Cash equivalent = credit consumed ÷ 10; this is not the model publisher’s list price.

Same token budget, different models
ModelEstimated credit consumedEstimated cash equivalent
Claude Opus 4.6$17.50$1.75
Claude Opus 4.7$17.50$1.75
Claude Opus 5$17.50$1.75
View LLM API pricing & billing

API integration examples

These minimal, text-only requests use the exact Y-API model ID. They do not demonstrate image, audio, video, file or tool support. The output limit also needs room for reasoning; an empty answer with finish_reason=length can mean the budget was exhausted.

A task to try

Here is a failing integration test and the module it exercises. Identify the root cause before proposing a fix, and say what evidence would confirm your diagnosis.

Set the TOKEN environment variable to a key from your console. Run this on your server or locally; never expose a key in browser code or a public repository.

cURL · Claude Opus 4.6
curl --fail-with-body --silent --show-error --max-time 120 \
  'https://api.y-api.bestvirtualgoods.com/v1/chat/completions' \
  -H "Authorization: Bearer ${TOKEN:?Set TOKEN first}" \
  -H 'Content-Type: application/json' \
  --data-binary @- <<'JSON'
{
  "model": "anthropic/claude-opus-4.6",
  "messages": [
    {
      "role": "user",
      "content": "Here is a failing integration test and the module it exercises. Identify the root cause before proposing a fix, and say what evidence would confirm your diagnosis."
    }
  ],
  "max_tokens": 4096
}
JSON

How to evaluate the result

The diagnosis should point at a specific line and predict an observable consequence. A fix that makes the test pass without explaining the cause is not a pass.

Before you choose

Is there a model card for this Opus version?

No. Anthropic distributes Claude under closed weights, so the catalog records no publisher card rather than linking an unrelated repository. The OpenRouter model page is the specification source cited here.

Sources & scope

Technical facts come from the cited model page and, where available, its linked publisher card. A card describes that checkpoint; it is not proof of the weights a gateway serves. Prices come only from the Y-API catalog. We do not claim measured latency, uptime or benchmark scores for this endpoint.