Seed 2.0 Code vs Ternary Bonsai 1.7B
At a Glance
| Compare | Seed 2.0 CodeByteDance Seed | Ternary Bonsai 1.7BPrismML |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.50Openrouter ↗ · Sep 22, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $3.00Openrouter ↗ · Sep 22, 2026 | Not reported |
| Context windowMaximum documented tokens | Not reported | 33K |
| Model facts checked | Sep 3, 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 | Seed 2.0 Code | Ternary Bonsai 1.7B |
|---|---|---|
| Developer | ByteDance Seed | PrismML |
| Family | Seed 2 0 | Bonsai 1 7b |
| Model | Seed 2.0 Code | Ternary Bonsai 1.7B |
| Version | Seed 2.0 Code | Ternary Bonsai 1.7B |
| Lifecycle | active | active |
| Released | 2026-02-14 | 2026-04-18 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Text |
| Context window | Unknown | 33K |
| Total parameters | Unknown | 1.7B |
| Active parameters | Unknown | Unknown |
| License | Unknown | apache-2.0 |
| Open weights | No | Yes |
| API available | Yes | No |
| Self-hostable | No | Yes |
| Provider access | Openrouter (Standard) | Unknown |
| Capabilities | agents, chat, generation, reasoning, structured_outputs, tools | chat, generation |
| Effective bit width | Unknown | 1.58 bits per weight |
| Weight size | Unknown | 0.46 GB |
| Weight format | Unknown | Ternary Q2_0 |
Seed 2.0 Code Capabilities
Ternary Bonsai 1.7B Capabilities
Primary Evidence
Sources and Freshness
Questions
Seed 2.0 Code vs Ternary Bonsai 1.7B FAQs
Is Seed 2.0 Code or Ternary Bonsai 1.7B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Seed 2.0 Code and Ternary Bonsai 1.7B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Seed 2.0 Code or Ternary Bonsai 1.7B?+
Only Seed 2.0 Code has a directly sourced input price: $0.50 per million tokens. Only Seed 2.0 Code has a directly sourced output price: $3.00 per million tokens.
Which has a larger context window, Seed 2.0 Code or Ternary Bonsai 1.7B?+
Neither model has a larger sourced context window in this comparison. Seed 2.0 Code is — and Ternary Bonsai 1.7B is 33K.
Which performs better in benchmarks, Seed 2.0 Code or Ternary Bonsai 1.7B?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Seed 2.0 Code or Ternary Bonsai 1.7B be self-hosted?+
Ternary Bonsai 1.7B is the only model in this pair currently marked as self-hostable. Seed 2.0 Code is not marked open weight; Ternary Bonsai 1.7B is open weight.
Can Seed 2.0 Code and Ternary Bonsai 1.7B understand images?+
Seed 2.0 Code is not documented with image input; Ternary Bonsai 1.7B is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Seed 2.0 Code or Ternary Bonsai 1.7B?+
Neither has a larger sourced maximum output. Seed 2.0 Code is — and Ternary Bonsai 1.7B is —.
Do Seed 2.0 Code and Ternary Bonsai 1.7B support reasoning and tool use?+
Seed 2.0 Code: reasoning and tool calling. Ternary Bonsai 1.7B: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, Seed 2.0 Code or Ternary Bonsai 1.7B?+
Seed 2.0 Code has 1 sourced provider route; Ternary Bonsai 1.7B has 0, so Seed 2.0 Code has broader tracked availability.
Which offers better value, Seed 2.0 Code or Ternary 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.