Model comparison

Kimi K2.7 Code vs Kimi K3

Compare published specifications, vendor API list prices and measured Borg performance. Both models are included in Borg.

Kimi K2.7 Code

262,144 tokensContext window
4780 msMedian time to first token (gateway proxy)
24.2Output tokens per second (whole turn)
—Request success
$0.95 / $4Vendor API price in / out · per 1M

Kimi K3

1,048,576 tokensContext window
8627 msMedian time to first token (gateway proxy)
18.1Output tokens per second (whole turn)
—Request success
$3 / $15Vendor API price in / out · per 1M

Included in Borg

At a glance

SpecificationKimi K2.7 CodeKimi K3
ProviderMoonshot AIMoonshot AI
Release—2026-07-16 Vendor source
Context262,144 tokens Vendor source1,048,576 tokens Vendor source
ModalitiesInput: text, image, video; output: Not publishedInput: text, image, video; output: Not published
Reasoning / thinking modesYes / Not publishedYes / Not published
Open weightsYesYes
Vendor API list price / 1M tokens$0.95 input / $4 output$3 input / $15 output
BorgIncluded in Borg subscriptionIncluded in Borg subscription

Not published by the vendor: release.

Measured on Borg

Metrics are not directly comparable to vendor benchmark claims. Models served different requests; this is observed gateway traffic, not a controlled head-to-head test.

Time to first token (gateway proxy)

Output tokens per second (whole turn)

MetricKimi K2.7 CodeKimi K3
Time to first token (gateway proxy) p504780 ms (119 samples)8627 ms (7633 samples)
Tokens per second (end to end) p5024.2 output tokens per second (1894 samples)18.1 output tokens per second (152924 samples)
Request success rateNot publishedNot published
Coding bench pass rateNot publishedNot published
Measurement window, samples and methodology

The fleet reference is the median of published model medians, not a request-weighted result. Prompt lengths, reasoning settings and traffic differ between models.

Kimi K2.7 Code: Measured on Borg: SearchAtlas AI Gateway production request logs. 30-day window ending 2026-10-08; 2583 requests. Minimum 100 samples per published request metric.

Kimi K3: Measured on Borg: SearchAtlas AI Gateway production request logs. 30-day window ending 2026-10-08; 183015 requests. Minimum 100 samples per published request metric.

Completion speed covers the whole turn including queueing and reasoning time; it is not a streaming tokens-per-second figure.

  • Time to first token (gateway proxy): time until the first streamed response event reaches the gateway; our closest available measure of time to first token
  • Tokens per second (end to end): tokens per second, end to end: provider-reported output tokens divided by the whole turn's elapsed time, including queueing and reasoning; not a streaming per-token rate

How to choose

Kimi K2.7 Code is listed for multi-file coding with iterative test runs, whereas Kimi K3 is listed for long-horizon coding across large repositories. Choosing between Kimi K2.7 Code and Kimi K3 requires checking published specifications against observed Borg traffic for your workflow.

Key differences

SpecKimi K2.7 CodeKimi K3
Context window262,144 tokens Vendor source1,048,576 tokens Vendor source Larger context
Reasoning modesYes / Not publishedYes / Not published
Release dateNot published2026-07-16 Vendor source
API price input / 1M0.95 Lower listed rate3
API price output / 1M4 Lower listed rate15
Time to first token (gateway proxy)4780 ms (119 samples) Lower median8627 ms (7633 samples)
Output tokens per second (whole turn)24.2 output tokens/s (whole turn) (1894 samples) Higher measured rate18.1 output tokens/s (whole turn) (152924 samples)
Request successNot publishedNot published
Coding benchNot publishedNot published

FAQ

How do Kimi K2.7 Code and Kimi K3 compare for coding?

Kimi K2.7 Code has a Borg coding benchmark of not published; Kimi K3 has not published. The Kimi K2.7 Code–Kimi K3 coding comparison cannot establish an overall winner from this small test alone.

How quickly do Kimi K2.7 Code and Kimi K3 start responding on Borg?

Borg median first response for Kimi K2.7 Code is 4,780 ms; for Kimi K3 it is 8,627 ms. The Kimi K2.7 Code–Kimi K3 gateway medians are observations, not guaranteed latency for individual requests.

What are the API prices for Kimi K2.7 Code and Kimi K3?

The listed API rate for Kimi K2.7 Code is $0.95 input / $4 output per 1M tokens; for Kimi K3 it is $3 input / $15 output per 1M tokens. Neither Kimi K2.7 Code nor Kimi K3 has its Borg subscription charge represented by those provider API rates. Kimi K2.7 Code vendor source · Kimi K3 vendor source

Explore both models

Kimi K2.7 Code · Kimi K3 · Borg pricing

More comparisons

All comparisons