OTRouter

Doubao Seed 2.1 Turbo

ByteDance · TextModel ID:doubao-seed-2.1-turbo
Open ConsoleExplore the API

Doubao Seed 2.1 Turbo 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: 93c84464-36ec-47b8-b4a1-51043a9eddf1Input / Output$0.44824959 / $2.24124793per 1,000,000 tokensPrice conditions

Line ID: 93c84464-36ec-47b8-b4a1-51043a9eddf1

InputOTRouter price: $0.44825

Cache writeOTRouter price: $0.448069

Cached inputOTRouter price: $0.08965

OutputOTRouter price: $2.241248

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 / ResponsesCompatible 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
256,000 tokens
Max input
256,000 tokens
Max output
256,000 tokens

Effective routing limits

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

Context window
256,000 tokens
Max input
256,000 tokens
Max output
256,000 tokens
Responses / ResponsesNative

Baseline request forms: JSON · Stream

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

Function tools
Supported
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
Supported

Declared entry limits

Context window
256,000 tokens
Max input
256,000 tokens
Max output
256,000 tokens

Effective routing limits

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

Context window
256,000 tokens
Max input
256,000 tokens
Max output
256,000 tokens
Messages / ResponsesCompatible 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
Messages token counting
Not supported

Declared entry limits

Context window
256,000 tokens
Max input
256,000 tokens
Max output
256,000 tokens

Effective routing limits

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

Context window
256,000 tokens
Max input
256,000 tokens
Max output
256,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": "doubao-seed-2.1-turbo",
  "messages": [
    {
      "role": "user",
      "content": "Hello, please introduce yourself."
    }
  ],
  "max_completion_tokens": 160
}'

Model capabilities

Router request protocols
Chat CompletionsResponsesMessages
Routing configuration
Configured routes: 1Configured upstream systems: 1No 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: ByteDance

Protocol documentation