Reasoning Tokens

For models that support it, the OpenRouter API can return Reasoning Tokens, also known as thinking tokens. OpenRouter normalizes the different ways of customizing the amount of reasoning tokens that the model will use, providing a unified interface across different providers.

Reasoning tokens provide a transparent look into the reasoning steps taken by a model. Reasoning tokens are considered output tokens and charged accordingly.

Reasoning tokens are included in the response by default if the model decides to output them. Reasoning tokens will appear in the reasoning field of each message, unless you decide to exclude them.

Controlling Reasoning Tokens

You can control reasoning tokens in your requests using the reasoning parameter:

The reasoning config object consolidates settings for controlling reasoning strength across different models. See the Note for each option below to see which models are supported and how other models will behave.

Max Tokens for Reasoning

For models that support reasoning token allocation, you can control it like this:

• "max_tokens": 2000 - Directly specifies the maximum number of tokens to use for reasoning

For models that only support reasoning.effort (see below), the max_tokens value will be used to determine the effort level.

Reasoning Effort Level

• "effort": "xhigh" - Allocates the largest portion of tokens for reasoning (approximately 95% of max_tokens)
• "effort": "high" - Allocates a large portion of tokens for reasoning (approximately 80% of max_tokens)
• "effort": "medium" - Allocates a moderate portion of tokens (approximately 50% of max_tokens)
• "effort": "low" - Allocates a smaller portion of tokens (approximately 20% of max_tokens)
• "effort": "minimal" - Allocates an even smaller portion of tokens (approximately 10% of max_tokens)
• "effort": "none" - Disables reasoning entirely

For models that only support reasoning.max_tokens, the effort level will be set based on the percentages above.

Excluding Reasoning Tokens

If you want the model to use reasoning internally but not include it in the response:

• "exclude": true - The model will still use reasoning, but it won’t be returned in the response

Reasoning tokens will appear in the reasoning field of each message.

Enable Reasoning with Default Config

To enable reasoning with the default parameters:

• "enabled": true - Enables reasoning at the “medium” effort level with no exclusions.

Legacy Parameters

For backward compatibility, OpenRouter still supports the following legacy parameters:

• include_reasoning: true - Equivalent to reasoning: {}
• include_reasoning: false - Equivalent to reasoning: { exclude: true }

However, we recommend using the new unified reasoning parameter for better control and future compatibility.

Examples

Basic Usage with Reasoning Tokens

Using Max Tokens for Reasoning

For models that support direct token allocation (like Anthropic models), you can specify the exact number of tokens to use for reasoning:

Excluding Reasoning Tokens from Response

If you want the model to use reasoning internally but not include it in the response:

Advanced Usage: Reasoning Chain-of-Thought

This example shows how to use reasoning tokens in a more complex workflow. It injects one model’s reasoning into another model to improve its response quality:

Provider-Specific Reasoning Implementation

Anthropic Models with Reasoning Tokens

The latest Claude models, such as anthropic/claude-3.7-sonnet, support working with and returning reasoning tokens.

You can enable reasoning on Anthropic models only using the unified reasoning parameter with either effort or max_tokens.

Note: The :thinking variant is no longer supported for Anthropic models. Use the reasoning parameter instead.

Reasoning Max Tokens for Anthropic Models

When using Anthropic models with reasoning:

• When using the reasoning.max_tokens parameter, that value is used directly with a minimum of 1024 tokens.
• When using the reasoning.effort parameter, the budget_tokens are calculated based on the max_tokens value.

The reasoning token allocation is capped at 128,000 tokens maximum and 1024 tokens minimum. The formula for calculating the budget_tokens is: budget_tokens = max(min(max_tokens * {effort_ratio}, 128000), 1024)

effort_ratio is 0.95 for xhigh effort, 0.8 for high effort, 0.5 for medium effort, 0.2 for low effort, and 0.1 for minimal effort.

Important: max_tokens must be strictly higher than the reasoning budget to ensure there are tokens available for the final response after thinking.

Example: Streaming with Anthropic Reasoning Tokens

Google Gemini 3 Models with Thinking Levels

Gemini 3 models (such as google/gemini-3-pro-preview and google/gemini-3-flash-preview) use Google’s thinkingLevel API instead of the older thinkingBudget API used by Gemini 2.5 models.

OpenRouter maps the reasoning.effort parameter directly to Google’s thinkingLevel values:

If a model doesn’t support a specific effort level (for example, if a model only supports low and high), OpenRouter will map your requested effort to the nearest supported level.

Using max_tokens with Gemini 3

If you specify reasoning.max_tokens explicitly, OpenRouter will pass it through as thinkingBudget to Google’s API. However, for Gemini 3 models, Google internally maps this budget value to a thinkingLevel, so you will not get precise token control. The actual token consumption is still determined by Google’s thinkingLevel implementation, not by the specific budget value you provide.

Example: Using Thinking Levels with Gemini 3

Preserving Reasoning Blocks

The reasoning_details functionality works identically across all supported reasoning models. You can easily switch between OpenAI reasoning models (like openai/gpt-5.2) and Anthropic reasoning models (like anthropic/claude-sonnet-4.5) without changing your code structure.

If you want to pass reasoning back in context, you must pass reasoning blocks back to the API. This is useful for maintaining the model’s reasoning flow and conversation integrity.

Preserving reasoning blocks is useful specifically for tool calling. When models like Claude invoke tools, it is pausing its construction of a response to await external information. When tool results are returned, the model will continue building that existing response. This necessitates preserving reasoning blocks during tool use, for a couple of reasons:

Reasoning continuity: The reasoning blocks capture the model’s step-by-step reasoning that led to tool requests. When you post tool results, including the original reasoning ensures the model can continue its reasoning from where it left off.

Context maintenance: While tool results appear as user messages in the API structure, they’re part of a continuous reasoning flow. Preserving reasoning blocks maintains this conceptual flow across multiple API calls.

Example: Preserving Reasoning Blocks with OpenRouter and Claude

For more detailed information about thinking encryption, redacted blocks, and advanced use cases, see Anthropic’s documentation on extended thinking.

For more information about OpenAI reasoning models, see OpenAI’s reasoning documentation.

Responses API Shape

When reasoning models generate responses, the reasoning information is structured in a standardized format through the reasoning_details array. This section documents the API response structure for reasoning details in both streaming and non-streaming responses.

reasoning_details Array Structure

The reasoning_details field contains an array of reasoning detail objects. Each object in the array represents a specific piece of reasoning information and follows one of three possible types. The location of this array differs between streaming and non-streaming responses:

• Non-streaming responses: reasoning_details appears in choices[].message.reasoning_details
• Streaming responses: reasoning_details appears in choices[].delta.reasoning_details for each chunk

Common Fields

All reasoning detail objects share these common fields:

• id (string | null): Unique identifier for the reasoning detail
• format (string): The format of the reasoning detail, with possible values:
  • "unknown" - Format is not specified
  • "openai-responses-v1" - OpenAI responses format version 1
  • "xai-responses-v1" - xAI responses format version 1
  • "anthropic-claude-v1" - Anthropic Claude format version 1 (default)
• index (number, optional): Sequential index of the reasoning detail

Reasoning Detail Types

1. Summary Type (reasoning.summary)

Contains a high-level summary of the reasoning process:

2. Encrypted Type (reasoning.encrypted)

Contains encrypted reasoning data that may be redacted or protected:

3. Text Type (reasoning.text)

Contains raw text reasoning with optional signature verification:

Response Examples

Non-Streaming Response

In non-streaming responses, reasoning_details appears in the message:

Streaming Response

In streaming responses, reasoning_details appears in delta chunks as the reasoning is generated:

Streaming Behavior Notes:

• Each reasoning detail chunk is sent as it becomes available
• The reasoning_details array in each chunk may contain one or more reasoning objects
• For encrypted reasoning, the content may appear as [REDACTED] in streaming responses
• The complete reasoning sequence is built by concatenating all chunks in order