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. | 236B | — |
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 | 128k |
| 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.40Mistral |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | — | $2.00Mistral |
| — | $180Mistral · zdr | |
| Overview | ||
| Company | DeepSeek | Mistral |
| Release date | Sep 5 2024 | May 7 2025 |
| Access | Open Weight | Closed |
| Model details | View model | View model |
Other comparisons
DeepSeek V2.5vsClaude Haiku 5.5Mistral Medium 3vsClaude Haiku 5.5DeepSeek V2.5vsGPT-6.1 SolMistral Medium 3vsGPT-6.1 SolDeepSeek V2.5vsGemini 4 ArgonMistral Medium 3vsGemini 4 ArgonDeepSeek V2.5vsMuse Spark OpenMistral Medium 3vsMuse Spark OpenDeepSeek V2.5vsGrok 4.7Mistral Medium 3vsGrok 4.7DeepSeek V2.5vsKimi K3Mistral Medium 3vsKimi K3Frequently asked questions
DeepSeek V2.5 and Mistral Medium 3 don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. DeepSeek V2.5 shipped 244 days before Mistral Medium 3, so benchmark comparisons should account for the intervening progress.
Context windows are 128k (DeepSeek V2.5) vs 128k (Mistral Medium 3). DeepSeek V2.5 is open weight, while Mistral Medium 3 is closed.
Direct benchmark comparisons are unavailable — DeepSeek V2.5 and Mistral Medium 3 don't publish scores on any of the same benchmarks.