Tokscale
Start Now
Menu

Kimi for Coding

Observed through

Tokscale Model Report

Kimi for Coding model details and observed coding usage from Tokscale.

Browse models

Reality Snapshot

Observed tokens

3.1B-86.2%

over 30 days

Estimated tracked spend

$549

Invoices may differ

Active developers

39+3

this month

30-day momentum

-86.2%

Compared with the prior 30-day window

Most-used client

Kimi59%

of observed tokens

Observed Usage

Tokens observedDaily active developers
Observed coding tokens over 30 daysDaily observed usage from Jul 12 through Aug 10, with active developer activity for context.1B800M600M400M200M0129.67.24.82.40Jul 12Jul 15Jul 18Jul 21Jul 24Jul 27Jul 29Aug 1Aug 4Aug 7Aug 10

How developers use it

Usage by coding client

Sharevs 30 days
Kimi
59%0%
OpenCode
22%0%
Gajae-Code
16%0%
Pi
3%0%
Claude Code
<1%0%

Token composition

Share of observed tokens

97%cache read
Cache read3B97%
Input85.3M2.8%
Output15.1M<1%
Reasoning00%
Cache-heavy workloadMost observed tokens reuse cached context across requests.

Observed Variants

defaultkimi-for-coding1.8B$238.1$0.1259.84%
highspeedkimi-for-coding-highspeed1.2B$310.6$0.2540.16%
highspeed, unlockedkimi-for-coding-highspeed-unlocked0$0$0.000%

Token Economics

Estimated spend profile

Kimi$44581.02%
OpenCode$9316.87%
Gajae-Code$0.000%
Pi$112.01%
Claude Code$0.000%
Senpi$0.520.1%

Observed cost signals

Estimated spend per 1M tracked tokens$0.18
Cache-read share96.7%
Estimated cache savingsNot available
Typical workloadcontext-heavy

Estimated tracked spend calculated from Tokscale model and provider pricing data. Actual invoices may differ.

Model Momentum

-86.2%30-day growthRank: Observed model

Compared with the prior non-overlapping window

Fastest-growing client: Kimi

800M533M267M0Jul 12Jul 27Aug 10

Official Model Details

ProviderMoonshotai

Tokscale Insight

Kimi for Coding recorded 3.1B coding tokens across 39 developers during the latest 30-day Tokscale window.

Observed confidenceHigh