DeepSeek R1 vs Bonsai 1.7B
At a Glance
| Compare | DeepSeek R1DeepSeek | Bonsai 1.7BPrismML |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.70Openrouter ↗ · Aug 28, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $2.50Openrouter ↗ · Aug 28, 2026 | Not reported |
| Context windowMaximum documented tokens | 164K | 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 | DeepSeek-R1 | Bonsai 1.7B |
|---|---|---|
| Developer | DeepSeek | PrismML |
| Family | Deepseek R1 | Bonsai 1 7b |
| Model | DeepSeek-R1 | Bonsai 1.7B |
| Version | DeepSeek-R1 | Bonsai 1.7B |
| Lifecycle | active | active |
| Released | 2025-01-20 | 2026-03-29 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Text |
| Context window | 164K | 33K |
| Total parameters | 684.5B | 1.7B |
| Active parameters | 37B | Unknown |
| License | mit | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | No |
| Self-hostable | Yes | Yes |
| Provider access | Hugging Face (Standard), Openrouter (Standard) | Unknown |
| Capabilities | chat, generation, reasoning | chat, generation |
| Effective bit width | Unknown | 1 bit per weight |
| Weight size | Unknown | 0.25 GB |
| Weight format | Unknown | Binary Q1_0 |
DeepSeek R1 Capabilities
Bonsai 1.7B Capabilities
Primary Evidence
Sources and Freshness
Questions
DeepSeek R1 vs Bonsai 1.7B FAQs
Is DeepSeek R1 or Bonsai 1.7B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both DeepSeek R1 and Bonsai 1.7B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, DeepSeek R1 or Bonsai 1.7B?+
Only DeepSeek R1 has a directly sourced input price: $0.70 per million tokens. Only DeepSeek R1 has a directly sourced output price: $2.50 per million tokens.
Which has a larger context window, DeepSeek R1 or Bonsai 1.7B?+
DeepSeek R1 has the larger sourced context window. DeepSeek R1 supports 164K and Bonsai 1.7B supports 33K.
Which performs better in benchmarks, DeepSeek R1 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 DeepSeek R1 or Bonsai 1.7B be self-hosted?+
Both models have the same recorded self-hosting status: supported. DeepSeek R1 is open weight; Bonsai 1.7B is open weight.
Can DeepSeek R1 and Bonsai 1.7B understand images?+
DeepSeek R1 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, DeepSeek R1 or Bonsai 1.7B?+
Neither has a larger sourced maximum output. DeepSeek R1 is 33K and Bonsai 1.7B is —.
Do DeepSeek R1 and Bonsai 1.7B support reasoning and tool use?+
DeepSeek R1: reasoning. Bonsai 1.7B: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, DeepSeek R1 or Bonsai 1.7B?+
DeepSeek R1 has 2 sourced provider routes; Bonsai 1.7B has 0, so DeepSeek R1 has broader tracked availability.
Which offers better value, DeepSeek R1 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.