Skip to main content
Claude Sonnet 5.5 balances response speed and reasoning capability for coding, knowledge work, and multistep tool workflows. Use the exact MixRoute ID claude-sonnet-5-5.

Model Information

These are model specifications. Actual limits, pricing, and hosted-tool availability depend on your account and route. Prefer the native Messages API for Claude-specific settings.

Messages API

Thinking Settings

Omitting thinking enables adaptive thinking. To turn off thinking before the initial response, use thinking: {"type":"between_tools"} with low, medium, or high effort. Inter-tool progress updates may still appear as thinking blocks; this is not a promise of zero thinking throughout a tool workflow.
Do not combine between_tools with xhigh/max, display, budget_tokens, or block_binding. Use adaptive thinking for the two highest effort levels. Omit non-default sampling settings (temperature, top_p, top_k) and legacy manual thinking budgets.

Tool Use and Responses

With auto selection, the model may either call a tool or answer directly. State when a tool is needed in the prompt. If strict tools are unavailable on the selected route, omit strict and validate the returned input in your application. When stop_reason is tool_use, handle every tool_use block, then send a user tool_result block with the matching tool_use_id. Append the complete assistant content array unchanged, including empty thinking blocks and their signatures. Do not reuse thinking blocks with another model or an unrelated conversation. Thinking text is omitted by default, so a content array can contain an empty thinking block before text. Read blocks by type instead of assuming content[0] is text:

OpenAI-Compatible Chat

Read text from choices[0].message.content. Do not assume Claude-specific thinking settings map to identically named Chat Completions fields; use Messages when those controls are needed.

Migrating from Sonnet 5

  1. Use claude-sonnet-5-5 without a date suffix.
  2. Replace disabled thinking with between_tools at high effort or below.
  3. Replace forced tool selection with auto; keep thinking blocks and signatures intact.
  4. Remove assistant prefills, manual thinking budgets, and non-default sampling settings.
  5. Re-evaluate token budgets and effort levels; hosted computer-use/advisor tools have separate platform-specific compatibility requirements.
Messages API | Chat Completions API