Qwen3.5 397B A17B vs Ternary Bonsai 27B
At a Glance
| Compare | Ternary Bonsai 27BPrismML | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.45Deepinfra ↗ · Sep 21, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $3.00Deepinfra ↗ · Sep 21, 2026 | Not reported |
| Context windowMaximum documented tokens | 262K | 262K |
| 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 | Qwen3.5-397B-A17B | Ternary Bonsai 27B |
|---|---|---|
| Developer | Qwen | PrismML |
| Family | Qwen3 5 397b A17b | Bonsai 27b |
| Model | Qwen3.5-397B-A17B | Ternary Bonsai 27B |
| Version | Qwen3.5-397B-A17B | Ternary Bonsai 27B |
| Lifecycle | active | active |
| Released | 2026-02-15 | 2026-07-04 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text, Image |
| Output modalities | Text | Text |
| Context window | 262K | 262K |
| Total parameters | 403.4B | 27B |
| Active parameters | 17B | Unknown |
| License | apache-2.0 | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard), Together Ai (Standard) | Together Ai (Standard) |
| Capabilities | chat, generation, reasoning, tools | 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 |
Qwen3.5 397B A17B Capabilities
Ternary Bonsai 27B Capabilities
Primary Evidence
Sources and Freshness
Questions
Qwen3.5 397B A17B vs Ternary Bonsai 27B FAQs
Is Qwen3.5 397B A17B or Ternary Bonsai 27B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Qwen3.5 397B A17B and Ternary Bonsai 27B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Qwen3.5 397B A17B or Ternary Bonsai 27B?+
Only Qwen3.5 397B A17B has a directly sourced input price: $0.45 per million tokens. Only Qwen3.5 397B A17B has a directly sourced output price: $3.00 per million tokens.
Which has a larger context window, Qwen3.5 397B A17B or Ternary Bonsai 27B?+
Neither model has a larger sourced context window in this comparison. Qwen3.5 397B A17B is 262K and Ternary Bonsai 27B is 262K.
Which performs better in benchmarks, Qwen3.5 397B A17B 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 Qwen3.5 397B A17B or Ternary Bonsai 27B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Qwen3.5 397B A17B is open weight; Ternary Bonsai 27B is open weight.
Can Qwen3.5 397B A17B and Ternary Bonsai 27B understand images?+
Qwen3.5 397B A17B 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, Qwen3.5 397B A17B or Ternary Bonsai 27B?+
Neither has a larger sourced maximum output. Qwen3.5 397B A17B is — and Ternary Bonsai 27B is —.
Do Qwen3.5 397B A17B and Ternary Bonsai 27B support reasoning and tool use?+
Qwen3.5 397B A17B: reasoning, 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, Qwen3.5 397B A17B or Ternary Bonsai 27B?+
Qwen3.5 397B A17B has 4 sourced provider routes; Ternary Bonsai 27B has 1, so Qwen3.5 397B A17B has broader tracked availability.
Which offers better value, Qwen3.5 397B A17B 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.