Models
Comparison
DeepSeek V3.1 vs DeepSeek V3.2
DeepSeek V3.1 and DeepSeek V3.2 side by side on Silicon Network: context length, capabilities, parameters, and the per-token price of each.
| DeepSeek V3.1 | DeepSeek V3.2 | |
|---|---|---|
| API model id | deepseek-v3.1 | deepseek-v3.2 |
| Base model | DeepSeek V3.1 | DeepSeek V3.2 |
| Family | DeepSeek | DeepSeek |
| Parameters | 671B MoE | 671B MoE |
| Size class | Very large (200B and up) | Very large (200B and up) |
| Context length | 131,072 tokens (128K) | 131,072 tokens (128K) |
| Capabilities | Text, Reasoning, and Reasoning can be switched off | Text, Reasoning, and Reasoning can be switched off |
| Served weights | 4-bit | 4-bit |
| Weights size | 406 GB | 378 GB |
| Input price | Unavailable | Unavailable |
| Output price | Unavailable | Unavailable |
The published rates could not be loaded just now. The pricing page reads them live.
Differences
- Both have a context window of 131,072 tokens.
- Both have 671B MoE parameters in total.
- Both support the same capabilities: Text, Reasoning, and Reasoning can be switched off.
Whether a model is loaded on a node right now changes through the day; the pricing page shows it live. A model that is not loaded answers 404 until an operator loads it.
About these figures
Context length, capabilities, and weights size come from the model card each id is served with. Rates are the published per-token prices, refreshed every few minutes. There are no speed figures here: the network does not publish per-model throughput yet.
Silicon Network›Models›DeepSeek V3.1 vs DeepSeek V3.213 items