Devstral 2 123B Instruct 2512 vs SOMA X v0.3.0
At a Glance
| Compare | Devstral 2 123B Instruct 2512Mistral AI | SOMA X v0.3.0NVIDIA |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.44Openrouter ↗ · Aug 29, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $2.20Openrouter ↗ · Aug 29, 2026 | Not reported |
| Context windowMaximum documented tokens | 262K | Not reported |
| Model facts checked | Aug 28, 2026View model evidence → | Sep 2, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | Devstral-2-123B-Instruct-2512 | SOMA-X v0.3.0 |
|---|---|---|
| Developer | Mistral AI | NVIDIA |
| Family | Devstral 2 123b Instruct 2512 | Soma X |
| Model | Devstral-2-123B-Instruct-2512 | SOMA-X v0.3.0 |
| Version | Devstral-2-123B-Instruct-2512 | SOMA-X v0.3.0 |
| Lifecycle | active | active |
| Released | Unknown | 2026-09-02 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Model-specific input |
| Output modalities | Text | 3D |
| Context window | 262K | Unknown |
| Total parameters | 125B | Unknown |
| Active parameters | Unknown | Unknown |
| License | other | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | No |
| Self-hostable | Yes | Yes |
| Provider access | Openrouter (Standard) | Unknown |
| Capabilities | chat, generation, tools | animation, hand-modeling, human-body-modeling, motion-retargeting, pose-inversion, simulation |
Devstral 2 123B Instruct 2512 Capabilities
SOMA X v0.3.0 Capabilities
Primary Evidence
Sources and Freshness
Questions
Devstral 2 123B Instruct 2512 vs SOMA X v0.3.0 FAQs
Is Devstral 2 123B Instruct 2512 or SOMA X v0.3.0 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Devstral 2 123B Instruct 2512 and SOMA X v0.3.0, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Devstral 2 123B Instruct 2512 or SOMA X v0.3.0?+
Only Devstral 2 123B Instruct 2512 has a directly sourced input price: $0.44 per million tokens. Only Devstral 2 123B Instruct 2512 has a directly sourced output price: $2.20 per million tokens.
Which has a larger context window, Devstral 2 123B Instruct 2512 or SOMA X v0.3.0?+
Neither model has a larger sourced context window in this comparison. Devstral 2 123B Instruct 2512 is 262K and SOMA X v0.3.0 is —.
Which performs better in benchmarks, Devstral 2 123B Instruct 2512 or SOMA X v0.3.0?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Devstral 2 123B Instruct 2512 or SOMA X v0.3.0 be self-hosted?+
Both models have the same recorded self-hosting status: supported. Devstral 2 123B Instruct 2512 is open weight; SOMA X v0.3.0 is open weight.
Can Devstral 2 123B Instruct 2512 and SOMA X v0.3.0 understand images?+
Devstral 2 123B Instruct 2512 is not documented with image input; SOMA X v0.3.0 is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Devstral 2 123B Instruct 2512 or SOMA X v0.3.0?+
Neither has a larger sourced maximum output. Devstral 2 123B Instruct 2512 is — and SOMA X v0.3.0 is —.
Do Devstral 2 123B Instruct 2512 and SOMA X v0.3.0 support reasoning and tool use?+
Devstral 2 123B Instruct 2512: tool calling. SOMA X v0.3.0: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, Devstral 2 123B Instruct 2512 or SOMA X v0.3.0?+
Devstral 2 123B Instruct 2512 has 1 sourced provider route; SOMA X v0.3.0 has 0, so Devstral 2 123B Instruct 2512 has broader tracked availability.
Which offers better value, Devstral 2 123B Instruct 2512 or SOMA X v0.3.0?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.