Skip to main content

Model comparison

Grok TTS vs Kimi K2.7 Code

Updated August 4, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload.

Grok TTS

xAI

Evidence status unavailable

90% interval unavailable

Kimi K2.7 Code

Moonshot AI

54.1/100

Estimated · Public rank #94

90% interval 42.2–65.9

The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. Use the documented cost, context, and runtime rows instead.

0 results are shared. Category rows based on different benchmark sets are marked directional and do not name a winner.

Which one for your work

Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.

No workload recommendation clears the current evidence threshold.

Use the matched evidence, workload costs, and sourced specifications below instead of treating a point score as a universal answer.

Show secondary and unsupported calls
  • Coding work

    Code generation, repair, and software-engineering tasks

    Not enough matched evidence

    No shared weighted benchmark basis supports a winner.

    Confidence: limited

  • Agentic work

    Tool use, computer use, and multi-step task completion

    Not enough matched evidence

    No shared weighted benchmark basis supports a winner.

    Confidence: limited

  • Long documents

    Prompts that approach the documented context limit

    Not enough matched evidence

    A complete context comparison is not sourced.

    Confidence: limited

  • Chat turn cost

    1K fresh input + 500 output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates

  • Cache-heavy agent loop cost

    200K cached + 20K fresh input + 10K output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: rate-fallback

  • Repository review cost

    50K fresh input + 3K output tokens

    Not enough matched evidence

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates

What is actually comparable

Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.

Shared results
0
Grok TTS only
0
Kimi K2.7 Code only
7
Like-for-like categories
0 / 8

Category results, on a stated basis

Each row states whether both averages use the same weighted benchmark set. Directional and not-comparable rows remain visible, but they never receive a winner in this template.

Agentic

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Coding

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Reasoning

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Knowledge

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Math

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Multilingual

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Multimodal

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Instruction following

Not comparable
Grok TTS
Not measured
Kimi K2.7 Code
Not measured
Weighted basis
0 vs 0 rows
Reading
Not comparable

Shape of the matched evidence

Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.

A shared-evidence shape is not available.

BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.

What each workload costs

Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.

Chat turn

1K fresh input + 500 output tokens

Grok TTS
API rate not published
Fit state unavailable
Kimi K2.7 Code
$0.00295
Fits in one request

Grok TTS has no comparable published API token rate.

Repository review

50K fresh input + 3K output tokens

Grok TTS
API rate not published
Fit state unavailable
Kimi K2.7 Code
$0.0595
Fits in one request

Grok TTS has no comparable published API token rate.

Cache-heavy agent loop

200K cached + 20K fresh input + 10K output tokens

Grok TTS
API rate not published
Fit state unavailable
Cached-input rate unavailable
Kimi K2.7 Code
$0.249
Fits in one request
Cached input priced at the published list-input rate

Kimi K2.7 Code has no published cached-input rate, so cached tokens use its listed input rate. Grok TTS has no comparable published API token rate.

Specification differences

Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.

Context window

Maximum documented context; output-token limits may be lower.

Grok TTS

N/A

Kimi K2.7 Code

256K

API model ID

Grok TTS

Not sourced

Kimi K2.7 Code

Not sourced

Cached-input rate

A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.

Grok TTS

No comparable hosted API rate

Kimi K2.7 Code

Not published

Documented inputs

Grok TTS

Not sourced

Kimi K2.7 Code

Not sourced

Documented outputs

Grok TTS

Not sourced

Kimi K2.7 Code

Not sourced

Provider availability

Grok TTS

Not sourced

Kimi K2.7 Code

Not sourced

Reasoning profile

Grok TTS

Non-Reasoning

Kimi K2.7 Code

Reasoning

Weight access

Grok TTS

Proprietary

Kimi K2.7 Code

Open Weight

License

Grok TTS

Proprietary

Kimi K2.7 Code

Open Weight

Release date

Grok TTS

2026-04-17

Kimi K2.7 Code

2026-06-12

If you already use one of these models
Deployment change
The models list different providers, so authentication, endpoint behavior, limits, and feature support may change.
Quality signal
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict.
Workload cost
A complete comparable API-rate estimate is not available for both models.
Context tradeoff
A complete documented context comparison is not available.

Run the same representative tasks against both endpoints before changing production traffic.

Self-host vs API cost

Estimates at 50,000 req/day · 1000 tokens/req average.

Grok TTS
API / mo$0
Self-host / moNot listed
Break-even
Proprietary model — self-hosting not applicable.
Kimi K2.7 Code
API / mo$3,713
Self-host / mo$18,221
Break-even326M/day
Model the full break-even

Benchmark evidence

The full public result ledger is available for audit without forcing a wide desktop table onto a phone.

Browse raw public benchmark evidence7 rows

Agentic

  • Kimi Claw 24/7

    Grok TTS
    Kimi K2.7 Code46.9%
    Source

    Not directly comparable

  • MCP Atlas

    Grok TTS
    Kimi K2.7 Code76%
    Source

    Not directly comparable

  • MCP Mark Verified

    Grok TTS
    Kimi K2.7 Code81.1%
    Source

    Not directly comparable

Coding

  • Kimi Code Bench v2

    Grok TTS
    Kimi K2.7 Code62.0%
    Source

    Not directly comparable

  • ProgramBench

    Grok TTS
    Kimi K2.7 Code53.6%
    Source

    Not directly comparable

  • MLS-Bench Lite

    Grok TTS
    Kimi K2.7 Code35.1%
    Source

    Not directly comparable

  • cursorBench32

    Grok TTS
    Kimi K2.7 Code49.7%
    Source

    Not directly comparable

Frequently asked questions

Which is better, Grok TTS or Kimi K2.7 Code?

The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. The page therefore keeps the decision tied to the specific documented workload.

Which is better for coding, Grok TTS or Kimi K2.7 Code?

The published evidence does not provide a shared weighted coding basis for both models, so BenchLM does not name a coding winner.

Which is better for agentic tasks, Grok TTS or Kimi K2.7 Code?

The published evidence does not provide a shared weighted agentic tasks basis for both models, so BenchLM does not name a agentic tasks winner.

Which costs less, Grok TTS or Kimi K2.7 Code?

Both models do not have comparable published API token rates, so this page does not name a universal price winner.

Which has the larger context window, Grok TTS or Kimi K2.7 Code?

A complete documented context-window comparison is not available.

Related comparisons

Last updated August 4, 2026

Watch Grok TTS vs Kimi K2.7 Code

One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.

Read a sample issue

Join 2,000+ readers.