Model comparison
DeepSeek-V3.1-Terminus vs DeepSeek-V3.1
- Input
- $0.27 / 1M tokens
- Output
- $0.95 / 1M tokens
- Context
- 128K
- Released
- 2025-09-22
- Input
- $0.21 / 1M tokens
- Output
- $0.79 / 1M tokens
- Context
- 128K
- Released
- 2025-08-21
DeepSeek-V3.1-Terminus scores higher on 8 of the 9 benchmarks both models report (the other leads on 1); DeepSeek-V3.1 is cheaper on input tokens ($0.2 vs $0.3 per 1M, 1.3×).
Specs and pricing side by side
| Spec | DeepSeek-V3.1-Terminus | DeepSeek-V3.1 |
|---|---|---|
| Maker | DeepSeek | DeepSeeksame |
| Released | 2025-09-22 | 2025-08-21 |
| Context window | 128K | 128Ksame |
| Max output | 32K | not published |
| Input price | $0.27 / 1M tokens | $0.21 / 1M tokens |
| Output price | $0.95 / 1M tokens | $0.79 / 1M tokens |
| Parameters | 685B total, 37B active (MoE) | 671B total / 37B active (MoE) |
| License | MIT | MITsame |
| Weights | Open weights | Open weightssame |
| Modalities | Text | Textsame |
Not published by either maker: knowledge cutoff.
Benchmarks both models report
| Benchmark | DeepSeek-V3.1-Terminus | DeepSeek-V3.1 |
|---|---|---|
| MMLU-Pro | 85% | 84.8% |
| GPQA-Diamond | 80.7% | 80.1% |
| Humanity's Last Exam | 21.7% | 15.9% |
| LiveCodeBench | 74.9% | 74.8% |
| Aider-Polyglot | 76.1% | 76.3% |
| SWE-bench Verified | 68.4% | 66% |
| SWE-bench Multilingual | 57.8% | 54.5% |
| Terminal-bench | 36.7% | 31.3% |
| BrowseComp | 38.5% | 30% |
Scores are as published by each maker or its cited source; harness, reasoning effort and date can differ between rows, so treat small gaps as ties. Sources are listed on each model page.
Which one should you pick?
Pick DeepSeek-V3.1-Terminus if…
- You care about MMLU-Pro, GPQA-Diamond, Humanity's Last Exam (it scores higher on 8 shared benchmarks).
- Your use case is: agentic coding assistants and autonomous software-engineering loops (SWE-bench-style tasks).
Pick DeepSeek-V3.1 if…
- You care about Aider-Polyglot (it scores higher on 1 shared benchmark).
- Cost matters: input tokens cost 1.3× less ($0.2 vs $0.3 per 1M).
- Your use case is: coding agents and software-engineering tasks (SWE-bench-style fix/patch workflows).
FAQ
Which is better, DeepSeek-V3.1-Terminus or DeepSeek-V3.1?
DeepSeek-V3.1-Terminus scores higher on 8 of the 9 benchmarks both models report (the other leads on 1); DeepSeek-V3.1 is cheaper on input tokens ($0.2 vs $0.3 per 1M, 1.3×). The better pick depends on whether you value benchmark scores, price per token, context length or openness for your workload.
How much cheaper is DeepSeek-V3.1?
DeepSeek-V3.1-Terminus: $0.27 / 1M tokens input, $0.95 / 1M tokens output. DeepSeek-V3.1: $0.21 / 1M tokens input, $0.79 / 1M tokens output (list API prices as published by each maker).
What are the context windows of DeepSeek-V3.1-Terminus and DeepSeek-V3.1?
DeepSeek-V3.1-Terminus offers 128K with up to 32K output; DeepSeek-V3.1 offers 128K.
Is DeepSeek-V3.1-Terminus newer than DeepSeek-V3.1?
DeepSeek-V3.1-Terminus was released 2025-09-22; DeepSeek-V3.1 was released 2025-08-21.
Go deeper
- DeepSeek-V3.1-Terminus: full specs, pricing and benchmarks
- DeepSeek-V3.1: full specs, pricing and benchmarks
- deepseek v3 2 exp vs deepseek v3 1 terminus
- kimi k2 thinking vs deepseek v3 1
- deepseek v3 1 vs minimax m1
- deepseek v3 1 terminus vs gemini 2 5 flash lite
- minimax m2 1 vs deepseek v3 1
- kimi k2 thinking vs deepseek v3 1 terminus
- All model comparisons
