Skip to main content

Claude Sonnet 5.5 chat from Anthropic, released 28 September 2026, through an OpenAI-compatible endpoint. It takes up to 1,000,000 tokens and returns up to 128,000, with reasoning effort from none to max and up to 128 tool definitions.

Input $2Output $10per 1 million tokensCached input $0.20Cache write $2.50

Workbench

Claude Sonnet 5.5

What can Claude Sonnet 5.5 help with?

Related models and next tasks

Missing the model you need?

Tell us what to add and where you would use it. Requests go to the people who decide what gets onboarded next.

Build stable message flows for long-context roleplay and fiction, with thinking you can switch off

Sonnet 5.5 is Anthropic's newest Sonnet, released on 28 September 2026, with a 1,000,000-token window and replies of up to 128,000 tokens — twice Sonnet 5's ceiling. On 1 October we sent it 24 content probes across three prompt styles and every one came back written in full: no refusals, nothing toned down, the Very strong level included. It costs Anthropic's list price, $2 in and $10 out per million tokens — the same list price as Sonnet 5. We add no filter of our own.

Open the chat playground
Build stable message flows for long-context roleplay and fiction, with thinking you can switch off
Model
Claude Sonnet 5.5
Good for
long-context roleplay and fiction, with thinking you can switch off
Message shape
System rules → evidence and state → current task → output contract
Fact boundary
Capabilities, controls, and price come from the live schema

Integration principle

Validate with the smallest message set, then add necessary context. Separate facts, assumptions, and constraints, and design interruption, retry, settlement, and review paths.

Build repeatable workflows for long-context roleplay and fiction, with thinking you can switch off

Sonnet 5.5 is Anthropic's newest Sonnet, released on 28 September 2026, with a 1,000,000-token window and replies of up to 128,000 tokens — twice Sonnet 5's ceiling. On 1 October we sent it 24 content probes across three prompt styles and every one came back written in full: no refusals, nothing toned down, the Very strong level included. It costs Anthropic's list price, $2 in and $10 out per million tokens — the same list price as Sonnet 5. We add no filter of our own.

  • Measured, not assumed

    24 probes, 24 written in full

    Every level from Mild to Maximum came back complete, all nine Very strong requests across the three ways of asking included. Nothing was refused and nothing was toned down.

  • No special framing

    Direct, novel chapter or system prompt

    All three ways of asking produced complete scenes, so you do not have to build a frame first. On the same probes Opus 5.5 finished two of six direct and in-story Very strong requests, and Sonnet 5 refused all six.

  • Thinking is optional

    Six effort settings, from none to max

    reasoning_effort runs none, low, medium, high, xhigh and max, with medium as the default here; xhigh and max also return their reasoning. none skips the thinking pass, but now and then the model works its deliberation into the reply — use low when you need a clean answer. Reasoning is billed as output.

  • Room at both ends

    1,000,000 in, 128,000 out

    About 555,000 English words of context, so a long chat history or a folder of documents goes in whole, and a full chapter or report comes back in one turn. Raise max_tokens yourself: the 4,096 default also has to cover any thinking.

Where Claude Sonnet 5.5 wins on task cost and interaction shape

Test one real task for quality, verifiability, latency, and sale-price fit instead of relying on a general leaderboard.

  1. Pick this

    Roleplay and fiction that Sonnet 5 turns down

    When the story goes where Sonnet 5 refuses. Ask directly, frame it as a novel chapter or set the scene in the system message — all three wrote complete scenes in our probes. Keep the whole conversation in context and run dialogue at low.

  2. Pick Opus 5.5 instead

    One hard answer matters more than cost

    Opus 5.5 lists at twice the price. It earns that when a single reply has to reconcile a long, conflicting brief. For fiction, our probes found Sonnet 5.5 wrote complete scenes where Opus 5.5 usually toned them down.

  3. Not the pick

    Pipelines that force a tool or tune temperature

    tool_choice takes auto or none only, and temperature and top_p are not accepted. If your integration pins one function every turn or leans on a calibrated temperature, rework that part first.

Turn Claude Sonnet 5.5 into concrete work, not generic labels

Every scenario needs input boundaries, verification, and recovery; official capabilities, benchmarks, and tool support are never invented.

  • A character that stays in voice for hours

    Companions and roleplay

    A character that stays in voice for hours

    Send the whole exchange verbatim: a million tokens means no summary layer, and a summary is where a character's names, promises and running jokes get lost. A fantasy campaign, a locked-room mystery or a daily companion all read livelier at low.

  • Branching stories the reader steers

    Interactive fiction

    Branching stories the reader steers

    Put the world rules, point of view and pacing in one system message and let each choice arrive as a user turn. When the reader asks for the whole chapter, 128,000 output tokens let it land in one reply.

  • Many calls, quick decisions

    Agents and tools

    Many calls, quick decisions

    Up to 128 tools with tool_choice on auto; the model decides when to call them. Anthropic suggests starting multi-step agents at medium and raising effort only on the steps that stall.

  • Read the whole set, answer at length

    Long documents

    Read the whole set, answer at length

    A contract bundle, a codebase or a research folder fits in one call, and the answer can run to a full report. Ask it to name the section behind each claim, so a gap shows up in the material rather than in the pipeline.

Organize context into an inspectable Claude Sonnet 5.5 input

Objective, evidence, state, constraints, and output contract need distinct jobs so requests can be compressed, debugged, and reproduced.

  1. Effort

    none or low for chat, medium for agents

    Anthropic's own advice is to start chat at medium or low; none goes one step further and skips thinking. Raise effort per request, not across all traffic — reasoning is billed as output.

  2. Frame

    Set the story once, at the top

    Genre, characters, point of view, tone and the limits of the scene belong in one system message — or present the request as a chapter of a novel, which in our probes was enough for complete scenes. Restating the frame every turn burns context and reads like a negotiation.

  3. Budget

    Leave room in max_tokens

    Thinking comes out of max_tokens. At high and above, give it generous headroom, or the thinking can use up the budget before the visible answer is complete.

  4. Structure

    Ask for a tool call, don't force one

    For structured output, define a tool with the schema you want and name it in the prompt, with tool_choice on auto. This route has no response_format, and a forced tool_choice is not accepted.

Prove a repeatable Claude Sonnet 5.5 case before product integration

Confirm live schema, quote, streaming, and error behavior before reusing the normalized request.

  1. 01 · Baseline

    Validate the smallest request in Playground

    Check message layers, output shape, streaming, and current controls.

  2. 02 · Boundaries

    Exercise failure, cancellation, and retry

    Verify timeouts, interrupted streams, oversized input, regeneration, and duplicate submission.

  3. 03 · Integrate

    Copy the normalized API request

    Use the public model id and messages contract; read model controls from the live schema.

  4. 04 · Operate

    Meter usage and keep evaluating

    Store state, final usage, failure reasons, and quality feedback; quote expensive calls first.

Bring Claude Sonnet 5.5 into a clear API contract

Playground, API examples, request states, and usage records stay aligned from evaluation through production integration.

  • Unified contract

    One shape for messages, streams, and errors

    Keep request structure, state handling, and error recovery consistent when changing models.

  • Live schema

    Use the current endpoint controls

    Playground and API examples expose available fields, limits, and default behavior together.

  • Observable lifecycle

    Every request has a clear state

    Submission, streaming, failure, cancellation, and usage use inspectable public semantics.

  • Portable integration

    Reduce work when models evolve

    A clear contract keeps product code focused on inputs, results, and user experience.

Claude Sonnet 5.5 API boundaries to confirm before integration

All Claude models10