OTRouter

MiniMax M2.5

MiniMax · TextModel ID:minimax-m2.5
Open ConsoleExplore the API

MiniMax M2.5 language model.

One model, automatic routing. Use the model ID in every request.

Multiple request protocols

Model pricing

No verified discount

Each line has its own published sales rates. Automatic routing chooses the supply used; fallback can change the price charged. Use the same model ID in every request. No credit is reserved; admitted requests may overdraw the balance, blocking new requests.

Line: d845ceef-ae87-49ee-8dfa-8ba26165b3e3Input / Output$0.304 / $1.213per 1,000,000 tokensPrice conditions

Line ID: d845ceef-ae87-49ee-8dfa-8ba26165b3e3

InputOTRouter price: $0.304

Cache writeOTRouter price: $0.304

Cached inputOTRouter price: $0.061

OutputOTRouter price: $1.213

per 1,000,000 tokens

Rate effective from:

Protocols and limits

These are published baseline text paths. Routing prefers an applicable native path and also considers cooldowns and each request’s features. This configuration does not show the path chosen for a request or current line health.

Chat Completions / Chat CompletionsNative

Baseline request forms: JSON · Stream

Native features describe the entry declarations; they do not indicate live verification.

Native features are not declared for this path.

Function tools
Not declared
Serial tool control
Not declared
Reasoning
Not declared
Image input
Not declared
Stop sequences
Not declared
JSON object output
Not declared
JSON schema output
Not declared
Streaming
Not declared

Declared entry limits

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Responses / Chat CompletionsCompatible conversion

Baseline request forms: JSON · Stream

Conversion features describe the supported conversion scope. Additional request fields and history must preserve their meaning.

Function tools
Supported
Serial tool control
Not supported
Reasoning
Not supported
Image input
Not supported
Stop sequences
Not supported
JSON object output
Not supported
JSON schema output
Not supported
Streaming
Supported

Declared entry limits

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Responses / MessagesCompatible conversion

Baseline request forms: JSON · Stream

Conversion features describe the supported conversion scope. Additional request fields and history must preserve their meaning.

Function tools
Supported
Serial tool control
Not supported
Reasoning
Not supported
Image input
Not supported
Stop sequences
Not supported
JSON object output
Not supported
JSON schema output
Not supported
Streaming
Supported

Declared entry limits

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Messages / MessagesNative

Baseline request forms: JSON · Stream

Native features describe the entry declarations; they do not indicate live verification.

Native features are not declared for this path.

Function tools
Not declared
Serial tool control
Not declared
Reasoning
Not declared
Image input
Not declared
Stop sequences
Not declared
JSON object output
Not declared
JSON schema output
Not declared
Streaming
Not declared
Messages token counting
Not declared

Declared entry limits

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Full pricing guide
Line: fd2deebb-f6f2-450a-8ab0-595ac0458ef6Input / Output$0.31377471 / $1.25509884per 1,000,000 tokensPrice conditions

Line ID: fd2deebb-f6f2-450a-8ab0-595ac0458ef6

InputOTRouter price: $0.313775

Cache writeOTRouter price: $0.308873

Cached inputOTRouter price: $0.062755

OutputOTRouter price: $1.255099

per 1,000,000 tokens

Rate effective from:

Protocols and limits

These are published baseline text paths. Routing prefers an applicable native path and also considers cooldowns and each request’s features. This configuration does not show the path chosen for a request or current line health.

Chat Completions / Chat CompletionsNative

Baseline request forms: JSON · Stream

Native features describe the entry declarations; they do not indicate live verification.

Native features are not declared for this path.

Function tools
Not declared
Serial tool control
Not declared
Reasoning
Not declared
Image input
Not declared
Stop sequences
Not declared
JSON object output
Not declared
JSON schema output
Not declared
Streaming
Not declared

Declared entry limits

Context window
—
Max input
—
Max output
—

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Responses / Chat CompletionsCompatible conversion

Baseline request forms: JSON · Stream

Conversion features describe the supported conversion scope. Additional request fields and history must preserve their meaning.

Function tools
Not supported
Serial tool control
Not supported
Reasoning
Not supported
Image input
Not supported
Stop sequences
Not supported
JSON object output
Not supported
JSON schema output
Not supported
Streaming
Supported

Declared entry limits

Context window
—
Max input
—
Max output
—

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Messages / Chat CompletionsCompatible conversion

Baseline request forms: JSON · Stream

Conversion features describe the supported conversion scope. Additional request fields and history must preserve their meaning.

Function tools
Not supported
Serial tool control
Not supported
Reasoning
Not supported
Image input
Not supported
Stop sequences
Not supported
JSON object output
Not supported
JSON schema output
Not supported
Streaming
Supported
Messages token counting
Not supported

Declared entry limits

Context window
—
Max input
—
Max output
—

Effective routing limits

Effective limits combine the model and this entry. An undeclared entry limit remains unknown.

Context window
200,000 tokens
Max input
200,000 tokens
Max output
128,000 tokens
Full pricing guide

Line observations

Unavailable

Public line observations are not available yet. Missing values do not indicate a healthy or failed line.

Historical delivery success
—
Completion latency
—
Published snapshot
—

Historical observations are not an SLA. Completion latency is not time to first token (TTFT).

Request examples

Use the same model ID; no line parameter is required.

bash
curl https://router.omnitools.ai/v1/chat/completions \
  -H "Authorization: Bearer $OTRouter_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "minimax-m2.5",
  "messages": [
    {
      "role": "user",
      "content": "Hello, please introduce yourself."
    }
  ],
  "max_completion_tokens": 160
}'

Model capabilities

Router request protocols
Chat CompletionsResponsesMessages
Routing configuration
Configured routes: 2Configured upstream systems: 2No baseline HA

Capabilities and limits depend on the line and protocol path. Review the published configuration with each line’s price.

These are Router request protocols. Routing prefers an applicable native line; otherwise, compatible conversion may be used. Requests whose meaning cannot be preserved are rejected. This list does not establish native upstream support.

Baseline HA means plain-text JSON and streaming requests have cross-provider safe-fallback candidates on Chat, Responses, and Messages. It is not live health or an SLA, and does not cover extra capabilities such as tools or stop sequences.

Model company: MiniMax

Protocol documentation