Skip to main content

Claude Sonnet 5 chat from Anthropic through an OpenAI-compatible endpoint. It takes up to 1,000,000 tokens of text and image context and returns up to 64,000, with low, medium or high reasoning effort, up to 128 tool definitions and SSE streaming.

Input $1.90Output $9.50per 1 million tokens5% below the publisher's list priceCached input $0.19Cache write $2.375Anthropic official priceInput $2Output $10

Workbench

Claude Sonnet 5

What can Claude Sonnet 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 high-volume Claude work over a million-token window

Sonnet 5 costs roughly 42% of the Opus 5 rate per million tokens here, and it keeps the full million-token window and the reasoning_effort dial. The concession is the reply ceiling: 64,000 tokens per turn rather than 128,000.

Open the chat playground
Build stable message flows for high-volume Claude work over a million-token window
Model
Claude Sonnet 5
Good for
high-volume Claude work over a million-token window
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 high-volume Claude work over a million-token window

Sonnet 5 costs roughly 42% of the Opus 5 rate per million tokens here, and it keeps the full million-token window and the reasoning_effort dial. The concession is the reply ceiling: 64,000 tokens per turn rather than 128,000.

  • Sonnet-tier rate

    About 42% of Opus 5 per million

    The same effort dial and the same window, at a rate that changes what is affordable at volume.

  • Full window kept

    1,000,000 tokens in

    The saving is not taken out of the context. Long transcripts and document sets fit exactly as they do on the Opus routes.

  • 64,000 per reply

    Half the Opus ceiling

    Enough for a long structured answer; a 100,000-token document needs a route with a 128,000 ceiling, or a second turn.

Where Claude Sonnet 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. Choose Sonnet 5

    Volume with a long context

    High-frequency work over large inputs, where the Opus rate would decide the budget before the quality does.

  2. Choose Opus 5

    A single reply must exceed 64,000

    Same window and same dial, twice the reply ceiling, at roughly 2.4× the rate.

  3. Choose Sonnet 4.6

    You want temperature instead

    The same window and the same family rate, with temperature and top_p in place of the effort dial.

Turn Claude Sonnet 5 into concrete work, not generic labels

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

  • Cost per conversation decides the design

    Production chat at volume

    Cost per conversation decides the design

    Long histories stay in context without the rate making every turn expensive.

  • Many long inputs, ordinary answers

    Bulk document work

    Many long inputs, ordinary answers

    Reading large documents and returning a page of findings is where the lower rate compounds.

  • Many calls, short replies

    Agent loops

    Many calls, short replies

    Tool-using loops spend most of their tokens on input. A lower input rate is felt on every iteration.

  • Adult characters, clear boundaries

    Unrestricted narrative work

    Adult characters, clear boundaries

    Sustained long-form continuity at a rate that makes long sessions practical. We add no content filter.

Organize context into an inspectable Claude Sonnet 5 input

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

  1. Effort

    Start at low and raise where it shows

    On this route most turns do not need deliberation; the ones that do are usually obvious from the task, not from the prompt.

  2. History

    Trim what the answer cannot use

    A long window is not a reason to resend everything. Input is still the larger half of most bills.

  3. Caching

    Put the variable part last

    The stable prefix at a tenth of the input rate is where the saving on this route actually lands.

  4. Output

    Design for 64,000, not 128,000

    Ask for a structure that fits one turn, or split the deliverable deliberately rather than discovering the ceiling.

Prove a repeatable Claude Sonnet 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 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 API boundaries to confirm before integration

All Claude models10