Loading the catalogue…
Loading the catalogue…
DeepSeek's open-weight MoE model with optional reasoning, a 164K-token context window and solid tool use. Released under the MIT licence.
Overview. DeepSeek-V3.2 is a text model from DeepSeek, released in December 2025 under the MIT licence. It is a sparse Mixture-of-Experts model with 685 billion parameters in total and about 37 billion active per token. It accepts up to 163,840 tokens of context and can return up to 65,536 tokens. One model covers both modes: it answers directly, or it reasons first when you set a reasoning effort.
Key strengths. - Strong on agentic and coding benchmarks for an open-weight model - Reasoning on demand, with adjustable effort - Tool calling and structured output - Open weights under MIT, so the same model can be served by several providers
When to use it. Use it for agentic work and coding where the model has to call tools, return structured output or work through a task in several steps. It also suits long-document analysis. If a task does not need deliberate reasoning, set the reasoning effort to none to cut latency and output cost.
Limitations. The model accepts text only, with no image or audio input. Reasoning adds output tokens and latency, so higher effort costs more per request. The reasoning levels each endpoint accepts can differ.
Sovereignty note. The model is developed by DeepSeek, based in China, and published as open weights. The weights can be run anywhere, so the creator never sees your prompts. Where your data is processed, and under which retention and training terms, depends on the endpoint that serves the request, not on the model.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.67 / 2.01+3 rates | Online |
13 use cases classified by the curator. The note says why.
A 163,840-token context window accommodates very long documents in a single pass, a clear advantage for document Q&A over shorter-context alternatives.
Tool-calling support is a listed core capability, making it a direct match for function-calling application patterns.
The 163,840-token window allows many sources to be synthesised in one context, supported by extended-thinking mode for reasoning across them.
Native tool-calling combined with extended-thinking mode and a 163,840-token window suits multi-tool orchestration, though no published agent benchmarks exist yet for this draft record.
Tool-calling and extended thinking are the relevant primitives for agentic coding loops, but no SWE-style evaluation is recorded to confirm performance.
Extended-thinking mode supports multi-step planning, but the absence of benchmarks and curated strengths leaves the planning-quality claim unverified.
Long-context retrieval over large policy corpora is well supported, and open-weights status allows on-premise deployment, but the draft record lacks grounding or accuracy evidence.
Tool-calling gives a path to schema-constrained output, though no extraction benchmark is recorded for this variant.
The large context window handles long-input summarisation, but the record has no quality benchmark to differentiate it from peers.
No vision capability is listed, so the model cannot perform OCR on document images.
No vision capability is listed for this variant, so image input is unsupported.
No audio output capability is listed, so the model cannot generate speech.
No audio input capability is listed, so the model cannot process speech for transcription.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, ifbench, aa-multilingual-index, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-ai/deepseek-v3-2",
"reasoning_effort": "high",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at