Tokscale
Open console
Menu

Kimi For Coding

Observed through

Tokscale Model Report

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

Official details Browse models

Reality Snapshot

Observed tokens

7.6B-64.4%

over 30 days

Estimated tracked spend

$930

Invoices may differ

Active developers

29-13

this month

30-day momentum

-64.4%

Compared with the prior 30-day window

Most-used client

Kimi89%

of observed tokens

Observed Usage

Tokens observedDaily active developers
Observed coding tokens over 30 daysDaily observed usage from Jun 30 through Jul 29, with active developer activity for context.1.2B960M720M480M240M0129.67.24.82.40Jun 30Jul 3Jul 6Jul 9Jul 12Jul 15Jul 17Jul 20Jul 23Jul 26Jul 29

How developers use it

Usage by coding client

Sharevs 30 days
Kimi
89%0%
Pi
9%0%
OpenCode
<1%0%
Gajae-Code
<1%0%
Hermes Agent
<1%0%

Token composition

Share of observed tokens

97%cache read
Cache read7.4B97%
Input185.6M2.4%
Output28.4M<1%
Reasoning41.1K0%
Cache-heavy workloadMost observed tokens reuse cached context across requests.

Token Economics

Estimated spend profile

Kimi$81687.79%
Pi$10210.93%
OpenCode$9.321%
Gajae-Code$0.000%
Hermes Agent$2.590.28%

Observed cost signals

Estimated spend per 1M tracked tokens$0.12
Cache-read share97.2%
Estimated cache savingsNot available
Typical workloadcontext-heavy

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

Model Momentum

-64.4%30-day growthRank: Observed model

Compared with the prior non-overlapping window

Fastest-growing client: Kimi

1.5B1B500M0Jun 30Jul 15Jul 29

Official Model Details

ProviderMoonshotai

Tokscale Insight

Kimi For Coding recorded 7.6B coding tokens across 29 developers during the latest 30-day Tokscale window.

Observed confidenceHigh