Claude Opus 5.5

anthropic/claude-opus-5.5

Claude Opus 5.5 is the successor entry to Opus 5 in Anthropic’s flagship line, listed with a 1,000,000-token window and text, image and file input. The reference positions it at multi-step changes in large codebases and long-horizon agent work.

Input · Account credit
$4.00

per 1M tokens

Cash equivalent $0.40

Output · Account credit
$20.00

per 1M tokens

Cash equivalent $2.00

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 where a change spans several files and the failure mode is a plausible-looking edit that breaks a distant caller. Give it the full diff plus the call sites, and ask it to name what it checked.

What to watch for

This entry lists only the `openai` endpoint upstream, so an Anthropic-native client pointed at `/v1/messages` is not the path the catalog advertises here. Successor positioning is also not a measured improvement over Opus 5 — treat it as a hypothesis to test.

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_outputstool_choicetoolsverbosity
OpenRouter model page & specifications

API pricing & cost estimate

Estimated credit consumed
$14.00
Estimated cash equivalent
$1.40

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 5.5$14.00$1.40
Claude Opus 5$17.50$1.75
Claude Sonnet 5$7.00$0.70
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

This refactor moves a retry helper into a shared module. List every caller that still imports the old path, then show the import change and the test that proves nothing else broke.

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 5.5
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-5.5",
  "messages": [
    {
      "role": "user",
      "content": "This refactor moves a retry helper into a shared module. List every caller that still imports the old path, then show the import change and the test that proves nothing else broke."
    }
  ],
  "max_tokens": 4096
}
JSON

How to evaluate the result

The answer should be reproducible: a search that finds the stale imports, a diff, and a test run. An edit that only compiles, with no call-site inventory, is the failure this check is designed to catch.

Before you choose

Is Opus 5.5 cheaper than Opus 5 on this catalog?

Check the price table on this page rather than assuming. The two are separate catalog entries with their own rates, and the newer version number does not by itself tell you which one costs less per token.

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.