GPT-6.1 Sol
One model, automatic routing. Use the model ID in every request.
Model pricing
No verified discountEach 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: 400c5323-def9-42f1-933d-4e36daee2375Input / Output$0.16 / $0.80per 1,000,000 tokensPrice conditions
Line ID: 400c5323-def9-42f1-933d-4e36daee2375
InputOTRouter price: $0.16
Cache writeOTRouter price: $0.20
Cached inputOTRouter price: $0.008
OutputOTRouter price: $0.80
per 1,000,000 tokens
Input tiers
Total input includes uncached and cached tokens. The matching tier applies to all input and output.
| Input tiers | Input | Cache write | Cached input | Output |
|---|---|---|---|---|
| 0–272,000 | $0.16 | $0.20 | $0.008 | $0.80 |
| 272,001–1,050,000 | $0.32 | $0.40 | $0.016 | $1.20 |
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.
- 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
- 272,000 tokens
- Max input
- 272,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
- 272,000 tokens
- Max input
- 272,000 tokens
- Max output
- 128,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
- 272,000 tokens
- Max input
- 272,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
- 272,000 tokens
- Max input
- 272,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
- Supported
- Serial tool control
- Not supported
- Reasoning
- Not supported
- Image input
- 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
- 272,000 tokens
- Max input
- 272,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
- 272,000 tokens
- Max input
- 272,000 tokens
- Max output
- 128,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
- 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
- 272,000 tokens
- Max input
- 272,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
- 272,000 tokens
- Max input
- 272,000 tokens
- Max output
- 128,000 tokens
Line: 673d2ca0-d2af-4bda-bcda-f7a8440f8a6aInput / Output$1.47 / $7.35per 1,000,000 tokensPrice conditions
Line ID: 673d2ca0-d2af-4bda-bcda-f7a8440f8a6a
InputOTRouter price: $1.47
Cache writeOTRouter price: $1.8375
Cached inputOTRouter price: $0.0735
OutputOTRouter price: $7.35
per 1,000,000 tokens
Input tiers
Total input includes uncached and cached tokens. The matching tier applies to all input and output.
| Input tiers | Input | Cache write | Cached input | Output |
|---|---|---|---|---|
| 0–272,000 | $1.47 | $1.8375 | $0.0735 | $7.35 |
| 272,001–1,050,000 | $2.94 | $3.675 | $0.147 | $11.025 |
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.
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 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
- 1,050,000 tokens
- Max input
- 1,050,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
- 272,000 tokens
- Max input
- 272,000 tokens
- Max output
- 128,000 tokens
- No baseline text path is published for Chat Completions.
- No baseline text path is published for Messages.
Line observations
UnavailablePublic 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.
curl https://router.omnitools.ai/v1/chat/completions \
-H "Authorization: Bearer $OTRouter_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-6.1-sol",
"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: 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: OpenAI
Protocol documentation