Compare AI models
| Specifications | ||
ParametersThe learned values that shape how a model responds. B means billion and T means trillion. For mixture-of-experts models, the total count is larger than the number active for each token. Parameter count alone does not measure quality. | 671B | 7B |
Context windowHow much information the model can work with in one request, measured in tokens — pieces of words or other data. This includes your question, attachments, conversation and reply. Limits can vary by model variant and provider. | 128k | 64k |
| API pricingUSD per 1M tokens · lower wins | ||
Cheapest inputLowest input rate across every provider on OpenRouter, the lab included. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $0.27SiliconFlow | — |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $1.00SiliconFlow | — |
| $104SiliconFlow · fp8 | — | |
| These models have no shared benchmark scores. | ||
SWE-Bench VerifiedCoding — Real coding tasks pulled from open-source projects — the AI has to find and fix actual bugs. A human-checked version of the original SWE-Bench. Higher is better. | 68.4% | — |
SWE-Bench MultilingualMultilingual coding — Like SWE-Bench, but the coding problems span many programming languages, not just one. Tests how broadly the AI can code. Higher is better. | 57.8% | — |
LiveCodeBenchCompetitive coding — Coding problems published so recently the AI can't have seen them in training — a contamination-free test of raw programming skill. Higher is better. | 74.9% | — |
HumanEvalFunction synthesis — 164 small Python problems: the AI is given a function's description and has to write the working function. This was the coding benchmark of the GPT-3.5 and GPT-4 era, before the field moved to fixing real bugs in real repositories. Higher is better. | — | 83.5% |
BrowseCompWeb browsing — Can the AI browse the web and track down hard-to-find answers? Higher is better. | 38.5% | — |
AIME 2025Reasoning — single-answer accuracy on the 2025 invitational mathematics exam without tools | 88.4% | — |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | 80.7% | — |
MMLU-ProKnowledge — accuracy on the ten-option MMLU-Pro benchmark | 85% | — |
| Overview | ||
| Company | DeepSeek | Qwen |
| Release date | Sep 22 2025 | Apr 16 2024 |
| Access | Open Weight | Open Weight |
| Model details | View model | View model |
Other comparisons
DeepSeek V3.1 TerminusvsClaude Fable 5.2CodeQwen1.5vsClaude Fable 5.2DeepSeek V3.1 TerminusvsGPT-6.2 AstraCodeQwen1.5vsGPT-6.2 AstraDeepSeek V3.1 TerminusvsGemini 4 NeonCodeQwen1.5vsGemini 4 NeonDeepSeek V3.1 TerminusvsMuse EmberCodeQwen1.5vsMuse EmberDeepSeek V3.1 TerminusvsGrok 4.7CodeQwen1.5vsGrok 4.7DeepSeek V3.1 TerminusvsMistral Large 4CodeQwen1.5vsMistral Large 4Frequently asked questions
DeepSeek V3.1 Terminus and CodeQwen1.5 don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. CodeQwen1.5 shipped 524 days before DeepSeek V3.1 Terminus, so benchmark comparisons should account for the intervening progress.
DeepSeek V3.1 Terminus has 671B parameters, while CodeQwen1.5 has 7B. Context windows are 128k (DeepSeek V3.1 Terminus) vs 64k (CodeQwen1.5).
Direct benchmark comparisons are unavailable — DeepSeek V3.1 Terminus and CodeQwen1.5 don't publish scores on any of the same benchmarks.