Claude
Anthropic · 2 models · Text, Image, File → Text
https://onerouter.com/v1/chat/completionsHow to call
Pass any model ID from this series in the model field, e.g. anthropic/claude-opus-4.8. The example on the right uses Claude Opus 4.8.
Overview
Anthropic's Claude family combines advanced reasoning and agentic coding with very large context windows.
This series includes 2 models: anthropic/claude-opus-4.8, anthropic/claude-sonnet-4.6. They share the same request shape — switching between them is a one-line change to the model field of the Chat Completions API.
Models in this series
Switch tabs to compare each model's ID, context window, inputs, outputs, and capabilities. Check the Models page for current availability and pricing before use.
anthropic/claude-opus-4.8| Provider | Anthropic |
| Context window | 1M |
| Max output | 128K |
| Input | Text, Image, File |
| Output | Text |
| Summary | Claude Opus 4.8 is an advanced Anthropic model for reasoning, agentic coding, and long-context analysis with a 1M-token window. |
| Strengths | Suited to complex reasoning, multi-step agentic tasks, and large-document analysis where accuracy is important. |
| Supported parameters | `max_tokens`, `reasoning`, `response_format`, `stop`, `structured_outputs`, `tool_choice`, `tools` |
Request headers
| Parameter | Type | Required | Description |
|---|---|---|---|
| Authorization | string · required | required | Bearer token, formatted as `Bearer YOUR_API_KEY`. |
| Content-Type | string · required | required | Must be `application/json`. |
Request body
These models use the OpenAI-compatible Chat Completions schema. Full field reference:
| Parameter | Type | Required | Description | Values |
|---|---|---|---|---|
| model | string | required | Model ID from this series (see the tabs above). | |
| messages | array | required | Conversation so far. Each item has `role` (`system`/`user`/`assistant`/`tool`) and `content`. | |
| max_tokens | integer | optional | Maximum tokens to generate. Newer models use `max_completion_tokens`. | |
| temperature | number | optional | Sampling temperature, typically 0–2. Higher is more random. | |
| top_p | number | optional | Nucleus sampling, 0–1. | |
| stop | string | array | optional | Up to 4 sequences where generation stops. | |
| frequency_penalty | number | optional | −2 to 2. Discourages repeating tokens. | |
| presence_penalty | number | optional | −2 to 2. Encourages new topics. | |
| seed | integer | optional | Best-effort deterministic sampling. | |
| tools | array | optional | Function/tool definitions the model may call. | |
| tool_choice | string | object | optional | Control tool use: `auto`, `none`, `required`, or a specific tool. | autononerequired |
| response_format | object | optional | Constrain output to `json_object` or `json_schema`. | |
| reasoning_effort | string | optional | For reasoning models: `low`, `medium`, or `high`. | lowmediumhigh |
| stream | boolean | optional | Return SSE deltas instead of one JSON response. | truefalse |
Response fields
A non-streaming call returns a chat.completion object (see the panel on the right).
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | optional | Unique identifier for the completion. |
| choices | array | optional | Generated choices. `choices[0].message.content` holds the reply. |
| choices[].finish_reason | string | optional | Why generation stopped: `stop`, `length`, `tool_calls`, or `content_filter`. |
| usage | object | optional | Token accounting: `prompt_tokens`, `completion_tokens`, `total_tokens`. |
| model | string | optional | The model that produced the response. |
Native Claude Messages API
Besides Chat Completions, Claude models can be called through the native Anthropic Messages API at /v1/messages — useful for Claude-native SDKs and tools. There the system prompt is a top-level system field, max_tokens is required, and extended thinking uses the thinking parameter. See the Claude Messages reference.
Model-dependent features
OneRouter keeps protocol compatibility and forwards model-specific parameters where supported. Features such as tool calling, structured output, reasoning, prompt caching, web search, image input, audio input, video generation, and provider-specific options depend on the selected model and upstream provider. Check the model detail page before relying on a feature in production.