Claude Opus 5.5

Claude Opus 5.5 is Anthropic's model for long-running agentic coding and knowledge work. Send the official Anthropic Messages request to TokLab: change the base URL and the API key, keep the body. The same model also answers the OpenAI Chat Completions and Responses formats.

Model ID

See the pricing page for current prices.

Quick example

curl https://api.toklab.ai/v1/messages \
  -H "x-api-key: $TOKLAB_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-opus-5-5",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Summarize the trade-offs of event sourcing in three bullet points."}]
  }'

Endpoints

The Messages endpoint forwards your request body as sent, including optional fields, and returns the official response. An anthropic-beta header is passed on as well. Keep the API key in server-side code.

Parameters

Thinking and effort

Claude Opus 5.5 always uses adaptive thinking: the model decides how much to think, and output_config.effort steers it. Higher effort usually means more output tokens, a longer wait and a higher cost. With thinking.display set to summarized, the response includes thinking blocks you can show; with omitted, they are left out. Thinking tokens are billed as output tokens.

Media inputs

Images and PDFs go in a user turn's content as image and document blocks, with a url source or, as in the official API, a base64 source:

{"role": "user", "content": [
  {"type": "image", "source": {"type": "url", "url": "https://example.com/chart.png"}},
  {"type": "text", "text": "What does this chart show?"}
]}

Replace the example URL with a publicly reachable file of your own.

Billing dimensions

See the current rates on the pricing page. A request is billed by the tokens it uses:

• input tokens,
• output tokens, including thinking,
• prompt-cache reads, and
• prompt-cache writes, with separate 5-minute and 1-hour rates.

The charge is taken from the usage reported with the finished response. A request that fails is not charged. Your account's usage records show the exact charge for every request.

Output

A non-streaming request returns the official message object:

{
  "id": "msg_...",
  "type": "message",
  "role": "assistant",
  "model": "claude-opus-5-5",
  "content": [{"type": "text", "text": "..."}],
  "stop_reason": "end_turn",
  "usage": {"input_tokens": 18, "output_tokens": 4, "cache_read_input_tokens": 0, "cache_creation_input_tokens": 0}
}

With "stream": true the response is a stream of the official events: message_start, content_block_start, content_block_delta, content_block_stop, message_delta and message_stop. The final message_delta carries the output token count.

OpenAI-compatible formats

The same model answers the OpenAI formats, so existing OpenAI code only needs a new base URL and model ID:

from openai import OpenAI

client = OpenAI(api_key="YOUR_TOKLAB_KEY", base_url="https://api.toklab.ai/v1")

chat = client.chat.completions.create(
    model="claude-opus-5-5",
    messages=[{"role": "user", "content": "Hello"}],
)
response = client.responses.create(model="claude-opus-5-5", input="Hello")

These requests are converted to the Messages format, so a field with no Messages counterpart has no effect. Their responses carry the official OpenAI fields and may include a few extra usage fields; read usage.total_tokens and the official fields.

Errors

Errors on /v1/messages use the Anthropic shape, {"type": "error", "error": {"type": "...", "message": "..."}}; the other formats use {"error": {"code": ..., "message": "..."}}. The code is a code from the common error catalog. Failed requests are not charged.

Tips

• Start with the default effort and raise it only for tasks that need more thinking; effort changes both quality and cost.
• Set max_tokens high enough for the thinking as well as the answer: it is one budget for both.
• Put long, reused context first and mark it with cache_control so later requests read it from the cache at the lower rate.

Related

• Claude Opus 5.5 pricing
• Download OpenAPI
• Copyable Markdown

Optional LLM group

The groups you can use depend on your account permissions and the model. The pricing page lists each group's prices.

API calls keep your API key and model ID. To select a group, send its exact name in the optional X-SeedRouter-Group request header, or append it to the model ID as model:<group> (see Model tiers). Replace GROUP_NAME below with one of your groups. Omit the header or use auto to keep the key's default behavior.

X-SeedRouter-Group: GROUP_NAME

A restricted API key may have fewer group options than your account. Requests use the selected group's pricing and do not switch to another group if it is unavailable. This option supports HTTP LLM calls, including SSE; it does not apply to WebSocket, image or video calls.

To see the groups your key can use, call GET /v1/models: it lists model:<group> next to the model ID for every model your key can call in more than one group.