Mistral Large 3 vs Ternary Bonsai 27B
At a Glance
| Compare | Mistral Large 3Mistral AI | Ternary Bonsai 27BPrismML |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.25Openrouter ↗ · Sep 22, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $0.75Openrouter ↗ · Sep 22, 2026 | Not reported |
| Context windowMaximum documented tokens | 262K | 262K |
| Model facts checked | Aug 29, 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 | Mistral Large 3 | Ternary Bonsai 27B |
|---|---|---|
| Developer | Mistral AI | PrismML |
| Family | Mistral Large 3 | Bonsai 27b |
| Model | Mistral Large 3 | Ternary Bonsai 27B |
| Version | Mistral Large 3 | Ternary Bonsai 27B |
| Lifecycle | active | active |
| Released | 2025-12-02 | 2026-07-04 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image, Document | Text, Image |
| Output modalities | Text | Text |
| Context window | 262K | 262K |
| Total parameters | 675B | 27B |
| Active parameters | 41B | Unknown |
| License | Apache-2.0 | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Mistral AI (Standard), Openrouter (Standard) | Together Ai (Standard) |
| Capabilities | agents, chat, generation, structured_outputs, tools, vision | chat, generation, reasoning, tools, vision |
| Base model | Unknown | Qwen3.6 27B |
| Effective bit width | Unknown | 1.58 bits per weight |
| Language model size | Unknown | 6.66 GiB |
| Weight format | Unknown | Ternary Q2_0 |
Mistral Large 3 Capabilities
Ternary Bonsai 27B Capabilities
Primary Evidence
Sources and Freshness
Questions
Mistral Large 3 vs Ternary Bonsai 27B FAQs
Is Mistral Large 3 or Ternary Bonsai 27B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Mistral Large 3 and Ternary Bonsai 27B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Mistral Large 3 or Ternary Bonsai 27B?+
Only Mistral Large 3 has a directly sourced input price: $0.25 per million tokens. Only Mistral Large 3 has a directly sourced output price: $0.75 per million tokens.
Which has a larger context window, Mistral Large 3 or Ternary Bonsai 27B?+
Neither model has a larger sourced context window in this comparison. Mistral Large 3 is 262K and Ternary Bonsai 27B is 262K.
Which performs better in benchmarks, Mistral Large 3 or Ternary Bonsai 27B?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Mistral Large 3 or Ternary Bonsai 27B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Mistral Large 3 is open weight; Ternary Bonsai 27B is open weight.
Can Mistral Large 3 and Ternary Bonsai 27B understand images?+
Mistral Large 3 is documented with image input; Ternary Bonsai 27B is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Mistral Large 3 or Ternary Bonsai 27B?+
Neither has a larger sourced maximum output. Mistral Large 3 is — and Ternary Bonsai 27B is —.
Do Mistral Large 3 and Ternary Bonsai 27B support reasoning and tool use?+
Mistral Large 3: tool calling and image input. Ternary Bonsai 27B: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Mistral Large 3 or Ternary Bonsai 27B?+
Mistral Large 3 has 2 sourced provider routes; Ternary Bonsai 27B has 1, so Mistral Large 3 has broader tracked availability.
Which offers better value, Mistral Large 3 or Ternary Bonsai 27B?+
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.