Claude Opus 5.5 vs Claude Sonnet 5.5

vs

Quale scegliere e quando

Sono due livelli della stessa linea Claude, non gemelli: Anthropic posiziona claude-opus-5-5 come livello superiore, pensato per il coding agentico di lunga durata e il lavoro di conoscenza, e claude-sonnet-5-5 come livello inferiore, indicato come più veloce. Sulla carta condividono un contesto da 1000000 token, un output massimo di 128000 e input di testo e immagini, quindi è il listino a segnare il divario: claude-opus-5-5 costa $4 in input, $20 in output e $0.2 per le letture dalla cache, cioè 2x claude-sonnet-5-5 a $2, $10 e $0.1. Metti il traffico ad alto volume e sensibile alla latenza su claude-sonnet-5-5 e affida i compiti agentici lunghi e difficili a claude-opus-5-5.

Benchmark

Claude Sonnet 5.5: 10 pubblicati, ma nessun benchmark in comune con abbastanza altri modelli per fare un confronto.

Sopra la mediaNessuno miglioreClaude Opus 5.515 / 218 / 21
Claude Opus 5.5 Claude Sonnet 5.5 altri modelli misurati media dei modelli confrontati ★ nessun altro modello ha fatto meglio
Terminal-bench 4.0
nessun altro modello ha fatto meglio 66.4%
N/A
OSWorld 2.0 partial
nessun altro modello ha fatto meglio 81.8%
N/A
Terminal-Bench-Science 0.1
58.7%
N/A
Humanity's Last Exam with tools
nessun altro modello ha fatto meglio 67.7%
N/A
Blueprint-Bench 2 Similarity score, Andon Labs leaderboard
51.2%
N/A
AutomationBench
40%
N/A
Chartography with tools
nessun altro modello ha fatto meglio 89%
N/A

Dati pubblicati dai provider: Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Anthropic Anthropic Anthropic Anthropic DeepSeek DeepSeek Google Google Google Google Moonshot OpenAI OpenAI OpenAI OpenAI Z.ai Z.ai Z.ai

Prezzi

Claude Opus 5.5 Claude Sonnet 5.5 Δ
Input / 1M token $4 $2 2×
Output / 1M token $20 $10 2×
Lettura cache / 1M token $0.2 $0.1 2×
Scrittura in cache 1.25x (5m) / 2x (1h) 1.25x (5m) / 2x (1h) -

Tariffe lette dal catalogo live al momento della build; il listino aggiornato è sulla pagina di ciascun modello.

Dove si collocano: prezzo di input per 1M di token tra tutti i modelli di chat con questa unità di fatturazione (86, scala logaritmica)

Funzionalità

Claude Opus 5.5 Claude Sonnet 5.5
Tool use sì sì
Controllo del ragionamento sempre attivo sempre attivo
Output strutturato sì sì
Prompt caching esplicito (contrassegni tu il prefisso) esplicito (contrassegni tu il prefisso)
Durata della cache 5m default, 1h option 5m default, 1h option
Prefisso minimo in cache 512 token 512 token

Specifiche

Claude Opus 5.5 Claude Sonnet 5.5
Modalità di input testo immagine testo immagine
Modalità di output testo testo
Rilascio 2026-09-22 2026-09-28
Knowledge cutoff 2026-06 2026-06
Finestra di contesto 1.000.000 1.000.000
Output massimo 128.000 128.000
Parametro di ragionamento output_config.effort thinking.type
Valori accettati
output_config.effort
  • low
  • medium
  • high
  • xhigh
  • max
thinking.type
  • adaptive (default)
  • between_tools
Valore di default medium adaptive, effort high

Le specifiche sono riprese dalla documentazione di ciascun provider; se un provider non pubblica un dato, la riga viene omessa e non dedotta. Fonti complete: Claude Opus 5.5 · Claude Sonnet 5.5

Un solo prompt, entrambi i modelli, misurati attraverso il gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. VERIFICA esattamente 3 frasi

Claude Opus 5.5 superato · 3 sentences

When we turned on reasoning, the model began "thinking out loud" before each answer, generating thousands of internal working tokens that users never see but that we are billed for just like the final response. Those hidden tokens are charged at the output rate, typically the most expensive rate, so the same question with the same visible answer now costs roughly twice as much or more. We can bring the bill back down without losing the quality gains by capping the reasoning budget and reserving reasoning mode for the complex tasks that actually benefit from it.

out 263 tok (+102 ragionamento) latenza 5.7 s

Claude Sonnet 5.5 superato · 3 sentences

Enabling reasoning makes the model "think" before it answers, and that internal thinking is generated as extra text (reasoning tokens) that we are billed for at the same rate as output tokens, even though users never see it. Output tokens also cost several times more than input tokens, so a single request that used to produce a short answer can now generate many times more billable text behind the scenes. Because our request volume and prompts didn't change, the doubling comes almost entirely from this hidden thinking, and we can bring it down by limiting reasoning effort, turning it off for simple tasks, and reserving it for the workloads where the accuracy gain justifies the cost.

out 205 tok latenza 3.6 s

Rispetto delle istruzioni (esattamente tre frasi: si contano), adattamento al destinatario (registro da CFO) e lo scarto di fatturazione dovuto al ragionamento nascosto, che i contatori di token qui sotto mettono in luce.

PROMPT This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. VERIFICA la correzione supera i test

Claude Opus 5.5 superato · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 best = max(best, cur) else: cur = 1 return best ``` **Explanation:** The original code counted *matching adjacent pairs* rather than *items in a run*. Both `cur` and `best` started at 0, and `cur` reset to 0 on a mismatch, so a run of length *n* was reported as *n − 1*. For a single-element list the loop never executes, so it returned 0 instead of 1. For `[5, 5]` it returned 1 instead of 2. The fix treats every element as the start of a run of length 1: `best` and `cur` start at 1, and `cur` resets to 1 (not 0) when the value changes. An explicit check returns 0 for an empty list. The "misses runs at the last index" reports are the same off-by-one bug rather than a separate one. […]

out 723 tok (+303 ragionamento) latenza 10.4 s

Claude Sonnet 5.5 superato · 8/8 cases

**The bug:** `cur` counts the number of *adjacent equal pairs* rather than the number of items in the run. A run of length k contains only k−1 such pairs, so every result is one too small. The counter also starts at 0 and the loop starts at index 1, so a single-element list never updates `best` and returns 0 instead of 1. (An empty list should return 0.) In addition, `cur` resets to 0 on a mismatch, when it should reset to 1, because the item at `xs[i]` begins a new run of length 1. The claim that it "misses runs ending at the last index" is really the same off-by-one: the final run is counted, but as one less than its true length. Because `best` is updated inside the loop on every extension, the last run isn't skipped. […]

out 444 tok latenza 6.7 s

Se la correzione è davvero giusta (si può eseguire), quanto è densa la spiegazione e quanti token servono per un compito circoscritto.

PROMPT Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. VERIFICA JSON valido, schema esatto

Claude Opus 5.5 superato · 5/5 fields, guidance "Withheld pending Q4 close"

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "Withheld pending Q4 close" } ``` **Judgment calls to check:** - **quarter**: Kept as "September quarter" rather than "Q3", since the fiscal calendar isn't stated. The text mentions an upcoming "Q4 close," so it may be fiscal Q3, but that's not certain. - **revenue_usd_m**: The text says only "412 for the topline." It doesn't state currency or units, and the figure is on a constant-currency basis, not reported USD. USD millions is an assumption. Use `null` if you need strictly stated values. - **growth_pct**: The source says "eleven and change," so the true figure is slightly above 11. 11 is an approximation. - **guidance**: Guidance was explicitly withheld. I recorded that rather than `null`, since the text addresses it directly.

out 829 tok (+488 ragionamento) latenza 10.9 s

Claude Sonnet 5.5 superato · 5/5 fields, guidance null

Here is the extracted JSON: ```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null } ``` Notes on the choices: - **quarter**: The text says "September quarter" without specifying a fiscal year or Q-number, so I kept the wording as stated. - **revenue_usd_m**: The text gives "412" for the topline, with no currency or unit stated explicitly. I've taken it as 412 million USD per the field definition, but the text does not confirm that, and the figure is constant-currency. - **growth_pct**: "Eleven and change" means slightly above 11, so 11 is an approximation. The exact figure isn't given. - **guidance**: Guidance is withheld pending the Q4 close, so no guidance is stated, hence null.

out 300 tok latenza 3.5 s

Aderenza allo schema (nessun campo inventato), tentazione di allucinare (il testo dice espressamente che la guidance non viene comunicata) e differenze tra i percorsi di output strutturato.

PROMPT Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. VERIFICA 120 parole, 0 parole vietate

Claude Opus 5.5 superato · 120 words, 0 banned, 1 question

Today we're launching Cross-Provider Prompt Caching for our API gateway. Why pay twice for the same context? Our gateway now stores repeated prompt prefixes, system instructions, and document chunks, then reuses them whether your request goes to OpenAI, Anthropic, Google, or an open-source model. Teams running retrieval pipelines or long agent loops can cut token costs by up to 60 percent and trim latency on every cached call. Setup takes one configuration flag; no code changes are required. Cache rules respect tenant boundaries, expire on your schedule, and log every hit for audit review. Dashboards show savings by provider, route, and application in real time. Cross-Provider Prompt Caching is available on all Pro and Enterprise plans. Turn it on today.

out 1263 tok (+1007 ragionamento) latenza 13.5 s

Claude Sonnet 5.5 superato · 122 words, 0 banned, 1 question

**Introducing Cross-Provider Prompt Caching** Your API gateway now caches prompts across every connected LLM provider, whether you route traffic to OpenAI, Anthropic, Google, or a self-hosted model. Here's how it works: the gateway fingerprints each prompt prefix, stores it centrally, and applies the right provider-specific caching mechanism automatically. When you switch providers or fail over during an outage, your cached context follows you. Early testing shows input token costs dropping by up to 70% on repeated system prompts and long documents, with latency improvements of 40% or more on cache hits. Tired of paying to send the same instructions thousands of times a day? Enable it with one configuration flag. Cache rules, TTLs, and per-team isolation are available in the dashboard today.

out 266 tok latenza 3.8 s

Rispetto dei vincoli (budget di parole, elenco di parole vietate, l'unica domanda), impronta stilistica e controllo della lunghezza.

Passa dall'uno all'altro cambiando una sola riga

In ogni scheda qui sotto ci sono entrambi gli id: le due righe evidenziate sono l'unica modifica. Stesso endpoint, stessa chiave, stessa struttura della richiesta.

from openai import OpenAI

client = OpenAI(
    base_url="https://synthorai.io/v1",
    api_key="sk-syn-...",
)

resp = client.chat.completions.create(
    model="claude-opus-5-5",
    # model="claude-sonnet-5-5",  # decommenta questa riga, commenta quella sopra
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Ottieni la tua chiave API →

FAQ

Qual è il più economico, Claude Opus 5.5 o Claude Sonnet 5.5?

Claude Sonnet 5.5 costa meno alla voce Input / 1M token ($2 contro $4, 2.0× di differenza). Altre voci potrebbero dire il contrario: la tabella qui sopra riporta il listino completo, e il costo reale dipende dal tuo mix di utilizzo.

Posso fare un A/B test di Claude Opus 5.5 contro Claude Sonnet 5.5 senza due integrazioni?

Sì. Si chiamano entrambi dallo stesso endpoint compatibile con OpenAI, con una sola chiave API. Per passare dall'uno all'altro basta cambiare la stringa del modello in una riga, quindi puoi mandare una parte del traffico a ciascuno e confrontare direttamente i costi.

Claude Opus 5.5 e Claude Sonnet 5.5 supportano il prompt caching?

Sì: entrambi fanno pagare le letture dalla cache meno della tariffa di input, quindi i carichi di lavoro con un prefisso già in cache costano meno di quanto facciano pensare le tariffe di listino. Le voci esatte per la lettura dalla cache sono nella tabella dei prezzi qui sopra.

Confronti correlati

Dai nostri studi con dati misurati