Grok Build vs. Kimi Code CLI

Comparison between Grok Build and Kimi Code CLI across the Artificial Analysis Coding Agent Index, including benchmark scores, cost, execution time, and token usage.

For details relating to our methodology, see our methodology page.

Explore other comparisons
vs

Highlights

Coding Agent Index

Artificial Analysis Coding Agent Index · Higher is better

Time per Task

Average agent wall time per task · Lower is better

Cost per Task

Average API cost per task (USD) · Lower is better

Comparison

Side-by-side comparison of Grok Build and Kimi Code CLI.

Coding Agent Comparison

Metric
Grok Build
Grok 4.5 (high)
Kimi Code CLI
Kimi K3
Analysis
Agent Harness
Grok Build
Kimi Code CLI
Representative Model
Grok 4.5 (high)
Kimi K3
Coding Agent Index
58
57
Grok Build has a higher Coding Agent Index than Kimi Code CLI
DeepSWE
60%
64%
Kimi Code CLI has a higher DeepSWE score than Grok Build
Terminal-Bench v2
85%
84%
Grok Build has a higher Terminal-Bench v2 score than Kimi Code CLI
SWE-Atlas-QnA
28%
23%
Grok Build has a higher SWE-Atlas-QnA score than Kimi Code CLI
Cost per Task
$2.59
$3.18
Grok Build has a lower cost per task than Kimi Code CLI
Time per Task
16.5m
23.8m
Grok Build has a lower time per task than Kimi Code CLI
Turns per Task
60.9
124.6
Grok Build has a lower turns per task than Kimi Code CLI
Token Usage per Task
3.6M
10.6M
Grok Build has a lower token usage per task than Kimi Code CLI
Cache Hit Rate
93%
95%
Kimi Code CLI has a higher cache hit rate than Grok Build

Model Variants

Evaluated model variants for Grok Build and Kimi Code CLI.

Model Variants

Grok Build
Grok 4.5 (high)
58
60%
85%
28%
$2.59
16.5m
3.6M
Kimi Code CLI
Kimi K3
57
64%
84%
23%
$3.18
23.8m
10.6M

Performance

Performance across the Artificial Analysis Coding Agent Index.

Artificial Analysis Coding Agent Index

Composite average pass@1 across DeepSWE, Terminal-Bench v2, and SWE-Atlas-QnA · Higher is better

The Artificial Analysis Coding Agent Index is a composite score built from DeepSWE, Terminal-Bench v2, and SWE-Atlas-QnA.

It is useful for quick comparison, but it should be read alongside the per-eval breakdowns. Two agents with similar index values can still have different strengths across repository tasks, terminal workflows, and rubric-based evaluations.

Token Usage

Token consumption across the Artificial Analysis Coding Agent Index.

Token Usage per Task

Average input, cache, and output tokens per task
Prompt cache hit rates can vary significantly by provider routing, which can materially change effective cost.

Non-cached input tokens sent to the model, including prompts, instructions, tool context, and task context that were not served from prompt cache.

Reused prompt tokens billed through provider prompt caching when that telemetry is available, rather than being processed as a fully fresh input each time.

Some providers route repeated requests across different backend replicas. When prompt cache state is not shared consistently across those replicas, a model may receive fewer cache hits even when the benchmark task flow is otherwise identical.

We do not add custom relay headers or provider-specific affinity controls to force higher cache reuse, because that would make the benchmark less representative of a typical user setup. As a result, reported costs reflect the cache behavior observed through the configured provider path, not an optimized best-case cache scenario.

Tokens returned by the model in its visible response during the task.

Artificial Analysis Coding Agent Index vs. Total Tokens

Artificial Analysis Coding Agent Index vs. average total tokens per task
Most attractive quadrant

Each point represents a coding-agent variant. Farther right means higher benchmark performance, while lower token usage appears farther left. Agents toward the upper-left use fewer tokens for a given level of performance.

Cost

Pay-per-token API cost across the Artificial Analysis Coding Agent Index, based on current per-token pricing.

Cost per Task

Average pay-per-token API cost per task (USD) · Lower is better

This chart shows the average pay-per-token API cost per task across the Artificial Analysis Coding Agent Index, spanning DeepSWE, Terminal-Bench v2, and SWE-Atlas-QnA.

Where applicable, that cost model includes standard input pricing, discounted cached-input pricing, separate cache-write charges, and output pricing rather than treating all prompt tokens as if they were billed at the same uncached input rate.

It is intended to show pay-per-token API cost, not consumer plan pricing or the full operational cost of deploying the system in production. Infrastructure, engineering, and supervision costs are not the focus of this metric.

Artificial Analysis Coding Agent Index vs. Cost per Task

Artificial Analysis Coding Agent Index vs. average pay-per-token API cost per task (USD)
Most attractive quadrant

Each point represents a coding-agent variant. Farther right means higher benchmark performance, while lower on the chart means lower average cost per task. The most efficient agents sit toward the lower-right: stronger results at lower cost.

Execution Time

Active agent runtime across the Artificial Analysis Coding Agent Index.

Time per Task

Average agent wall time per task · Lower is better

This chart uses agent wall time: how long the agent process was actively running on each task.

It does not include environment startup, verifier or judge time, or other harness overhead, so it is a cleaner comparison of how long the agent itself was working.

Artificial Analysis Coding Agent Index vs. Execution Time

Artificial Analysis Coding Agent Index vs. average agent wall time per task
Most attractive quadrant

Each point represents a coding-agent variant. Farther right means higher benchmark performance, while lower on the chart means shorter average agent runtime per task. Agents toward the lower-right deliver stronger results in less active agent time.