. Text version | o10
View formatted page → Copied to clipboard

DeepSeek V3.2. Price, context, and routing

Source page: https://www.o10.io/models/deepseek-v3-2

Plain-text reference for reading, copying, and citation. Examples are illustrative; use your own credentials for API requests.

Model data: https://www.o10.io/api/models.json
Content index: https://www.o10.io/llms.txt
Prices are dated references, not live quotes. Check the current endpoint rate before use.

# DeepSeek V3.2. Price, context, and routing

DeepSeek V3.2 costs $0.280/1M input tokens and $0.420/1M output tokens as of 2026-06-27. DeepSeek publishes this model with a 128K tokens context window. o10 lists DeepSeek V3.2 on AWS Bedrock and SambaNova at routing band C1. API slug deepseek-v3-2. Verify list prices against the venue you call.

## Key takeaways

### What is DeepSeek V3.2?

DeepSeek V3.2 is a chat model from deepseek (slug: deepseek-v3-2). Pick DeepSeek V3.2 for high-volume DeepSeek chat at aggregator prices. It is the V-line, not R1 reasoning. Published input pricing starts at $0.280/1M tokens. Context window: 128K tokens.

*Catalog snapshot 2026-06-27.*

### When should you pick DeepSeek V3.2?

Pick DeepSeek V3.2 for high-volume DeepSeek chat at aggregator prices. It is the V-line, not R1 reasoning. DeepSeek V3.2 is cheaper than most closed flagships. Escalate to DeepSeek R1 or a closed lab only when evals fail.

### How does DeepSeek V3.2 differ from sibling models?

DeepSeek V3.2 is cheaper than most closed flagships. Escalate to DeepSeek R1 or a closed lab only when evals fail.

### How much does DeepSeek V3.2 cost per million tokens?

DeepSeek V3.2 costs $0.280/1M input tokens and $0.420/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?

DeepSeek V3.2 is configured on AWS Bedrock and SambaNova. Known host IDs: bedrock: bedrock/deepseek.v3.2; bedrock: sambanova/DeepSeek-V3.2. This model is routable through o10 eval-gated routing.

### What is DeepSeek V3.2's context window?

DeepSeek V3.2 supports a 128K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.

### What o10 routing band is DeepSeek V3.2?

DeepSeek V3.2 is classified at o10 routing band C1. Bands group models by cost tier and eval profile: C0 (economy), C1 (standard), C2 (capable), C3/C4 (frontier). Production routing is enabled for this slug.

### Who makes DeepSeek V3.2?

DeepSeek V3.2 is attributed to source provider deepseek in the o10 catalog. Fulfillment hosts (AWS Bedrock and SambaNova) supply API access; list pricing may differ by venue.

## Citation
DeepSeek V3.2 costs $0.280/1M input tokens and $0.420/1M output tokens as of 2026-06-27. DeepSeek publishes this model with a 128K tokens context window. o10 lists DeepSeek V3.2 on AWS Bedrock and SambaNova at routing band C1. API slug deepseek-v3-2. Verify list prices against the venue you call.
## Methodology

Fulfillment catalog 2026-06-27. Gateway pricing joined where slug match exists.

## FAQ

### How much does DeepSeek V3.2 cost?

DeepSeek V3.2 costs $0.280/1M input tokens and $0.420/1M output tokens in the gateway snapshot (2026-06-27). Verify against your provider's published pricing.

### What is DeepSeek V3.2's context window?

DeepSeek V3.2 supports 128K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.

### Which hosts serve DeepSeek V3.2?

DeepSeek V3.2 (deepseek-v3-2) is configured on: AWS Bedrock and SambaNova. Upstream model IDs are listed in the fulfillment routes section.

### Is DeepSeek V3.2 routable through o10?

Yes. DeepSeek V3.2 is routable at band C1. Send model: "deepseek-v3-2" or use an o10 smart routing alias.

### How do I call DeepSeek V3.2 via o10?

Use o10 slug "deepseek-v3-2" or gateway ID "deepseek/deepseek-v3.2" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.

### How does o10 route this model?

o10 routes DeepSeek V3.2 only when per-use-case evals clear at your quality floor. Band C1 indicates cost tier. See /kyi for governance and /models/routing for smart aliases.

## Related links

- [DeepSeek V3.2 HTML](https://www.o10.io/models/deepseek-v3-2)
- [DeepSeek V3.2 pricing](https://www.o10.io/pricing/deepseek/deepseek-v3-2)
- [Model catalog](https://www.o10.io/models)
- [llms-models.txt](https://www.o10.io/llms-models.txt)

## Source URL

https://www.o10.io/models/deepseek-v3-2