Deepseek V3.2 Thinking costs $0.620/1M input tokens and $1.85/1M output tokens as of 2026-06-27. Deepseek publishes this model with a 128K tokens context window. o10 lists Deepseek V3.2 Thinking on DeepSeek at routing band C4.
Deepseek V3.2 Thinking pricing — input/output per 1M tokens
AnswersSelf-contained
How much does Deepseek V3.2 Thinking cost per million tokens?
Deepseek V3.2 Thinking costs $0.620/1M input tokens and $1.85/1M output tokens in the gateway catalog snapshot (2026-06-27). Endpoint pricing may differ by fulfillment host.
Sourced from gateway catalog snapshot.
Where can you run Deepseek V3.2 Thinking?
Deepseek V3.2 Thinking is configured on DeepSeek. Each host maps to an upstream model ID listed in the fulfillment routes table. This model is routable through o10 eval-gated routing.
What is Deepseek V3.2 Thinking's context window?
Deepseek V3.2 Thinking supports a 128K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.
01Deep dive
Token pricing
Gateway snapshot pricing for Deepseek V3.2 Thinking.
Deepseek V3.2 Thinking token pricing
Unit
Price
Input
$0.62/1M tokens
Output
$1.85/1M tokens
02Deep dive
Fulfillment hosts
Upstream venues configured for Deepseek V3.2 Thinking.
Deepseek V3.2 Thinking costs $0.620/1M input tokens and $1.85/1M output tokens in the gateway snapshot (2026-06-27). Verify against your provider's published pricing.
What is Deepseek V3.2 Thinking's context window?
Deepseek V3.2 Thinking supports 128K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.
Which hosts serve Deepseek V3.2 Thinking?
Deepseek V3.2 Thinking (deepseek-v3.2-thinking) is configured on: DeepSeek. Upstream model IDs are listed in the fulfillment routes section.
Is Deepseek V3.2 Thinking routable through o10?
Yes. Deepseek V3.2 Thinking is routable at band C4. Send model: "deepseek-v3.2-thinking" or use an o10 smart routing alias.
How do I call Deepseek V3.2 Thinking via o10?
Use o10 slug "deepseek-v3.2-thinking" or gateway ID "deepseek/deepseek-v3.2-thinking" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.
How does o10 route this model?
o10 routes Deepseek V3.2 Thinking only when per-use-case evals clear at your quality floor. Band C4 indicates cost tier. See /kyi for governance and /models/routing for smart aliases.