Directory · Model comparison
Grok Build 0.1 vs Kimi K2.7 Code
Side-by-side API economics and benchmarks. Per-1M input and output rates, context window, and verified metrics.
Tale of the tape
Head-to-head specs pulled from each model profile.
| Metric | Grok Build 0.1 | Kimi K2.7 Code |
|---|---|---|
| Input cost / 1M | $1.00 | $0.95 |
| Output cost / 1M | $2.00 | $4.00 |
| Context window | 256,000 tokens | 262,144 tokens |
| MMLU score | — | — |
Cost verdict
Enter monthly input and output volumes to see total cost savings.
Grok Build 0.1
- Input: 1M × $1.00 = $1.00
- Output: 1M × $2.00 = $2.00
- Total
- $3.00
Kimi K2.7 Code
- Input: 1M × $0.95 = $0.95
- Output: 1M × $4.00 = $4.00
- Total
- $4.95
Total cost savings
$1.95
Grok Build 0.1 saves $1.95 per month vs the other model at this volume.
Model routing savings
Uses this page's verified rates. Kimi K2.7 Code is the premium route (higher combined per-1M cost); Grok Build 0.1 handles routine traffic.
All premium
Kimi K2.7 Code
$247.50
100% of input and output on the premium route
Routed stack
80% → Grok Build 0.1
20% → Kimi K2.7 Code
$169.50
- Routine slice
- $120.00
- Premium slice
- $49.50
Monthly savings
$78.00
31.5% lower
Rates pulled from this page's model database entries (kimi-k2-7-code, grok-build-0-1) — same per-1M input/output figures as Tale of the tape. Production routing needs quality gates and monitoring.
Related comparisons
More head-to-head model matchups.