Model comparison
1-bit Bonsai 1.7B vs Inkling
Head-to-head evidence from 0 shared benchmark results across 0 categories. Overall scores shown here use the public BenchAlign v5 ranking lane.
Public leaderboard positions: 1-bit Bonsai 1.7B unranked (Not scored); Inkling #20 (Supported). Intervals and evidence labels describe ranking uncertainty, not a guarantee for a specific workload.
Evidence parity. 1-bit Bonsai 1.7B and Inkling share 0 comparable benchmark results. 0 of 8 categories are comparable. 0 results are unique to 1-bit Bonsai 1.7B; 32 to Inkling.
Updated July 21, 2026- Shared results
- 0
- 1-bit Bonsai 1.7B only
- 0
- Inkling only
- 32
- Comparable categories
- 0 / 8
Benchmark data for 1-bit Bonsai 1.7B and Inkling is coming soon on BenchLM.
Confidence note. This is a partial-evidence comparison with 0 shared benchmark results across 0 evidence categories; 0 of 8 categories currently have scoreable aggregates for both models. Treat the verdict as directional until coverage is more balanced.
Why this result
BenchLM does not have sourced benchmark coverage for 1-bit Bonsai 1.7B yet. This comparison is currently limited to metadata such as context window, reasoning mode, and pricing where available.
Inkling is priced at $1.87 input / $4.68 output per 1M tokens, versus $0.00 input / $0.00 output per 1M tokens for 1-bit Bonsai 1.7B. Inkling has the larger context window at 1M, compared with 32K for 1-bit Bonsai 1.7B.
Operational comparison
Runtime and commercial metrics are compared only when both models have a complete sourced value.
| Metric | 1-bit Bonsai 1.7B | Inkling | Comparison |
|---|---|---|---|
| Input / output priceUSD per 1M tokens | 1-bit Bonsai 1.7B$0 input / $0 output | Inkling$1.87 input / $4.68 output | 1-bit Bonsai 1.7B has the lower combined listed price. |
| Generation speedtokens per second | 1-bit Bonsai 1.7BNot available | InklingNot available | A complete speed comparison is not available. |
| First-answer latencyseconds to first token | 1-bit Bonsai 1.7BNot available | InklingNot available | A complete latency comparison is not available. |
| Context windowmaximum listed tokens | 1-bit Bonsai 1.7B32K | Inkling1M | Inkling lists the larger context window. |
Benchmark Deep Dive
Agentic9 benchmarks
| Benchmark | 1-bit Bonsai 1.7B | Inkling | Result |
|---|---|---|---|
| Terminal-Bench 2.0Source | — | 63.8% | Not comparable |
| BrowseCompSource | — | 77.1% | Not comparable |
| MCP AtlasSource | — | 74.1% | Not comparable |
| Design Arena Agentic Web DevSource | — | 1257 | Not comparable |
| AA Agentic IndexSource | — | 32.3% | Not comparable |
| GDPval-AASource | — | 36.9% | Not comparable |
| GDPval-AASource | — | 1239 | Not comparable |
| AA BriefcaseSource | — | 836 | Not comparable |
| AA Tau3 BankingSource | — | 23.7% | Not comparable |
Coding5 benchmarks
Reasoning2 benchmarks
Knowledge10 benchmarks
| Benchmark | 1-bit Bonsai 1.7B | Inkling | Result |
|---|---|---|---|
| GPQASource | — | 87.9% | Not comparable |
| GPQA-DSource | — | 87.9% | Not comparable |
| HLESource | — | 46% | Not comparable |
| HLE w/o toolsSource | — | 30% | Not comparable |
| Artificial Analysis Intelligence IndexSource | — | 40.7% | Not comparable |
| AA-GPQA DiamondSource | — | 87.2% | Not comparable |
| AA-HLESource | — | 29.7% | Not comparable |
| AA-Omniscience IndexSource | — | 2.1% | Not comparable |
| AA-Omniscience AccuracySource | — | 40.0% | Not comparable |
| AA-Omniscience Hallucination RateSource | — | 63.1% | Not comparable |
Math1 benchmarks
| Benchmark | 1-bit Bonsai 1.7B | Inkling | Result |
|---|---|---|---|
| AIME26Source | — | 97.1% | Not comparable |
Multimodal4 benchmarks
Inst. Following1 benchmarks
| Benchmark | 1-bit Bonsai 1.7B | Inkling | Result |
|---|---|---|---|
| IFBenchSource | — | 79.8% | Not comparable |
Frequently Asked Questions (3)
Can I compare 1-bit Bonsai 1.7B and Inkling on BenchLM yet?
Not fully yet. BenchLM is tracking both models, but the sourced benchmark breakdown for this comparison is still coming soon.
Why does this comparison show “coming soon”?
BenchLM only shows category winners and benchmark-level calls when we have sourced results that can be compared fairly. For these models, the public benchmark coverage is not complete enough yet.
What data is available for 1-bit Bonsai 1.7B and Inkling today?
1-bit Bonsai 1.7B: $0.00 input / $0.00 output per 1M tokens Inkling: $1.87 input / $4.68 output per 1M tokens Both model pages still include creator, context window, reasoning mode, and other metadata while benchmark coverage fills in.
Related Comparisons
Explore More
Choose a model with this week’s evidence
Join 2,000+ readers for ranking moves, pricing changes, and the claims that still need proof.
One email each week. Unsubscribe anytime.