Grok Build 0.1 vs Kimi K2.7-Code
Grok Build 0.1 and Kimi K2.7-Code both operate at the terminal-agent level. xAI's Grok Build emphasizes plan-first execution with up to eight parallel sub-agents in isolated Git worktrees. Moonshot's Kimi K2.7-Code emphasizes open weights, MCP tool-use evidence, multimodal input, and low-cost hosted or self-hosted deployment.
Pick Grok Build 0.1 when the product workflow needs xAI's CLI-native multi-agent orchestration and human-in-the-loop plan review. Pick Kimi K2.7-Code when open-weight deployment, MCP-heavy tool invocation, multimodal input, and lower input token cost matter more. Treat benchmark claims carefully: Grok Build's often-cited SWE-bench Verified 70.8% belongs to the retired grok-code-fast-1 predecessor, while Kimi K2.7-Code has no public SWE-bench or Terminal-Bench entry.
Decision scorecard
Local evidence first| Signal | Grok Build 0.1 | Kimi K2.7-Code |
|---|---|---|
| Best for | custom coding agents, code generation, and tool loops | custom coding agents, code generation, and tool loops |
| Decision fit | Coding, RAG, and Agents | Coding, RAG, and Agents |
| Context window | 256k | 262k |
| Cheapest output | $2/1M tokens | $4/1M tokens |
| Provider routes | 3 tracked | 1 tracked |
| Shared benchmarks | 0 shared | 0 shared |
Decision tradeoffs
- Grok Build 0.1 has the lower cheapest tracked output price at $2/1M tokens.
- Grok Build 0.1 has broader tracked provider coverage for fallback and procurement flexibility.
- Local decision data tags Grok Build 0.1 for Coding, RAG, and Agents.
- Kimi K2.7-Code has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Local decision data tags Kimi K2.7-Code for Coding, RAG, and Agents.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Grok Build 0.1
$1,300
Cheapest tracked route/tier: xAI Console
Kimi K2.7-Code
$1,760
Cheapest tracked route/tier: Moonshot AI Kimi
Estimated monthly gap: $460. Batch, cache, alternate speed tiers, and negotiated pricing are excluded from this local estimate.
Switch friction
- No overlapping tracked provider route is sourced for Grok Build 0.1 and Kimi K2.7-Code; plan for SDK, billing, or endpoint changes.
- Kimi K2.7-Code is $2/1M tokens higher on cheapest tracked output pricing, so quality gains need to justify the spend.
- No overlapping tracked provider route is sourced for Kimi K2.7-Code and Grok Build 0.1; plan for SDK, billing, or endpoint changes.
- Grok Build 0.1 is $2/1M tokens lower on cheapest tracked output pricing before cache, batch, or negotiated discounts.
Specs
| Specification | ||
|---|---|---|
| Released | 2026-05-14 | 2026-06-12 |
| Context window | 256k | 262k |
| Parameters | — | 1T |
| Architecture | - | Mixture of Experts |
| License | Proprietary | MITOSI-approved |
| Openness | Proprietary | Open source |
| Commercial use | Commercial use: conditional | Commercial use: permitted |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Grok Build 0.1 | Kimi K2.7-Code |
|---|---|---|
| Input price |
| $0.95/1M tokens |
| Output price |
| $4/1M tokens |
| Providers |
Capabilities
| Capability | Grok Build 0.1 | Kimi K2.7-Code |
|---|---|---|
| Vision | Yes | Yes |
| Multimodal | Yes | Yes |
| Reasoning | Yes | Yes |
| Function calling | Yes | Yes |
| Tool use | Yes | Yes |
| Structured outputs | Yes | Yes |
| Code execution | No | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark scores are currently available for this pair.
Deep dive
The comparison is primarily workflow and deployment fit, not a public leaderboard shootout. Neither side has a clean shared public coding benchmark in the current handoff.
Grok Build's differentiator is orchestration. The documented surface is a CLI coding-agent product with planning and parallel sub-agents, not just a raw model endpoint.
Kimi's differentiator is portability. It has open weights, direct Kimi API pricing at $0.95/M input and $4/M output, MCP Mark Verified evidence, and image/video input support for broader agent pipelines.
FAQ
Which has a larger context window, Grok Build 0.1 or Kimi K2.7-Code?
Kimi K2.7-Code supports 262k tokens, while Grok Build 0.1 supports 256k tokens. That gap matters most for long documents, large codebases, retrieval-heavy agents, and conversations where earlier context must remain visible.
Which is cheaper, Grok Build 0.1 or Kimi K2.7-Code?
Grok Build 0.1 lists tiered pricing: 0-200,001t is $1/1M input and $2/1M output; 200,001t+ is $2/1M input and $4/1M output. Kimi K2.7-Code lists $0.95/1M input and $4/1M output tokens on the cheapest tracked provider. Compare the tier you will actually use; cheap async pricing can overstate savings for interactive workflows. Provider discounts or batch pricing can still change the final bill.
Is Grok Build 0.1 or Kimi K2.7-Code open source?
Grok Build 0.1 is listed under Proprietary. Kimi K2.7-Code is listed under MIT. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Which is better for vision, Grok Build 0.1 or Kimi K2.7-Code?
Both Grok Build 0.1 and Kimi K2.7-Code expose vision. The better choice depends on benchmark fit, context budget, pricing, and whether your provider route exposes the same capability surface. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.
Which is better for multimodal input, Grok Build 0.1 or Kimi K2.7-Code?
Both Grok Build 0.1 and Kimi K2.7-Code expose multimodal input. The better choice depends on benchmark fit, context budget, pricing, and whether your provider route exposes the same capability surface.
Where can I run Grok Build 0.1 and Kimi K2.7-Code?
Grok Build 0.1 is available on xAI Console, Vercel AI Gateway, and OpenRouter. Kimi K2.7-Code is available on Moonshot AI Kimi. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
Continue comparing
Last reviewed: 2026-06-15. Data sourced from public model cards and provider documentation.