xAI's coding model for agentic coding and tool calling, and the model that powers Grok Build. It bills half Grok 4.7's input rate and a third of its output rate, on a 256K window instead of 500K.
Pick it if
you run agentic coding, debugging or tool-calling loops on a budget
you want xAI coding at a third of Grok 4.7's output rate
your prompts repeat, so cached input bills at a fifth of input
Skip it if
you need more than 256K tokens of context; Grok 4.7 offers 500K
Moonshot AI's coding-focused Kimi model, built on Kimi K2.6 with the same architecture and the same price. An open-weights 1T-parameter MoE (32B active) that always reasons; Moonshot says it uses about 30% fewer thinking tokens than K2.6.
Pick it if
you want Moonshot's coding model at the same rate as Kimi 2.6
you run long agentic coding sessions over a 256K context
you need open weights you could later self-host
Skip it if
you want general writing or analysis; Moonshot points those at K2.6
you need replies without a thinking pass; reasoning cannot be disabled
FAQ
Which is cheaper, Grok Build 0.1 or Kimi 2.7 Code?
Kimi 2.7 Code lists the lower input price, while Grok Build 0.1 lists the lower output price. On a coding-agent session (2M tokens in, 60,000 out) Grok Build 0.1 costs $2.12 and Kimi 2.7 Code $2.14.
Can I switch between Grok Build 0.1 and Kimi 2.7 Code mid-task?
Yes. In an Octomind session, /model octohub:grok-build-0.1 and /model octohub:kimi-2.7-code switch models without losing the conversation, so you can draft on one and review on the other.
Try either model
Switch between models inside the same Octomind session.