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. | 8B/70B/405B | 123B |
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 | 256k |
| 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.02DeepInfra | $0.40Mistral |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $0.04DeepInfra | $2.00Mistral |
| $6.00DeepInfra · fp8 | $180Mistral | |
| These models have no shared benchmark scores. | ||
BullshitBench v2Nonsense detection — Given a confidently-worded but nonsensical prompt, does the AI spot that it makes no sense and push back — instead of playing along and inventing an answer? The score is how often it clearly called out the nonsense. Higher is better. | 14% | — |
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. | — | 72.2% |
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. | — | 61.3% |
Terminal-Bench 2.0Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? (Version 2.0 of the test.) Higher is better. | — | 32.6% |
| Overview | ||
| Company | Meta | Mistral |
| Release date | Jul 23 2024 | Dec 9 2025 |
| Access | Open Weight | Open Weight |
| Model details | View model | View model |
Other comparisons
LLaMA 3.1vsClaude Haiku 5.5Devstral 2 (123B)vsClaude Haiku 5.5LLaMA 3.1vsGPT-6.1 SolDevstral 2 (123B)vsGPT-6.1 SolLLaMA 3.1vsGemini 4 ArgonDevstral 2 (123B)vsGemini 4 ArgonLLaMA 3.1vsGrok 4.7Devstral 2 (123B)vsGrok 4.7LLaMA 3.1vsDeepSeek-V4.1-Flash-1017Devstral 2 (123B)vsDeepSeek-V4.1-Flash-1017LLaMA 3.1vsKimi K3Devstral 2 (123B)vsKimi K3Frequently asked questions
LLaMA 3.1 and Devstral 2 (123B) don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. LLaMA 3.1 shipped 504 days before Devstral 2 (123B), so benchmark comparisons should account for the intervening progress.
LLaMA 3.1 has 8B/70B/405B parameters, while Devstral 2 (123B) has 123B. Context windows are 128k (LLaMA 3.1) vs 256k (Devstral 2 (123B)).
Direct benchmark comparisons are unavailable — LLaMA 3.1 and Devstral 2 (123B) don't publish scores on any of the same benchmarks.