Devstral 2 123B Instruct 2512 vs Bonsai 1.7B
At a Glance
| Compare | Devstral 2 123B Instruct 2512Mistral AI | Bonsai 1.7BPrismML |
|---|---|---|
| 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 | 33K |
| Model facts checked | Aug 28, 2026View model evidence → | Sep 18, 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 | Bonsai 1.7B |
|---|---|---|
| Developer | Mistral AI | PrismML |
| Family | Devstral 2 123b Instruct 2512 | Bonsai 1 7b |
| Model | Devstral-2-123B-Instruct-2512 | Bonsai 1.7B |
| Version | Devstral-2-123B-Instruct-2512 | Bonsai 1.7B |
| Lifecycle | active | active |
| Released | Unknown | 2026-03-29 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Text |
| Context window | 262K | 33K |
| Total parameters | 125B | 1.7B |
| 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 | chat, generation |
| Effective bit width | Unknown | 1 bit per weight |
| Weight size | Unknown | 0.25 GB |
| Weight format | Unknown | Binary Q1_0 |
Devstral 2 123B Instruct 2512 Capabilities
Bonsai 1.7B Capabilities
Primary Evidence
Sources and Freshness
Questions
Devstral 2 123B Instruct 2512 vs Bonsai 1.7B FAQs
Is Devstral 2 123B Instruct 2512 or Bonsai 1.7B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Devstral 2 123B Instruct 2512 and Bonsai 1.7B, 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 Bonsai 1.7B?+
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 Bonsai 1.7B?+
Devstral 2 123B Instruct 2512 has the larger sourced context window. Devstral 2 123B Instruct 2512 supports 262K and Bonsai 1.7B supports 33K.
Which performs better in benchmarks, Devstral 2 123B Instruct 2512 or Bonsai 1.7B?+
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 Bonsai 1.7B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Devstral 2 123B Instruct 2512 is open weight; Bonsai 1.7B is open weight.
Can Devstral 2 123B Instruct 2512 and Bonsai 1.7B understand images?+
Devstral 2 123B Instruct 2512 is not documented with image input; Bonsai 1.7B 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 Bonsai 1.7B?+
Neither has a larger sourced maximum output. Devstral 2 123B Instruct 2512 is — and Bonsai 1.7B is —.
Do Devstral 2 123B Instruct 2512 and Bonsai 1.7B support reasoning and tool use?+
Devstral 2 123B Instruct 2512: tool calling. Bonsai 1.7B: 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 Bonsai 1.7B?+
Devstral 2 123B Instruct 2512 has 1 sourced provider route; Bonsai 1.7B has 0, so Devstral 2 123B Instruct 2512 has broader tracked availability.
Which offers better value, Devstral 2 123B Instruct 2512 or Bonsai 1.7B?+
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.