Kimi K3 (k3)
Observed throughTokscale Model Report
Kimi K3 (k3) model details and observed coding usage from Tokscale.
Reality Snapshot
Observed tokens
41.2B>+999%
over 30 days
Estimated tracked spend
$15.8K
Invoices may differ
Active developers
72+71
this month
30-day momentum
>+999%
Compared with the prior 30-day window
Most-used client
Kimi48%
of observed tokens
Observed Usage
Tokens observedDaily active developers
How developers use it
Usage by coding client
Sharevs 30 daysToken composition
Share of observed tokens
97%cache read
Cache read39.8B97%
Input1.3B3.1%
Output159.8M<1%
Reasoning3.5M<1%
Cache-heavy workloadMost observed tokens reuse cached context across requests.
Observed Variants
default
k341.2B$15.8K$0.3899.95%via kimi
kimi/k311.6M$0$0.000.03%high
k3-high6.9M$0$0.000.02%max
k3-max2.4M$0$0.000.01%Token Economics
Estimated spend profile
Kimi$8.7K54.79%
OpenCode$3.4K21.66%
Pi$1.9K12.08%
Senpi$1.7K10.85%
Gajae-Code$0.000%
Claude Code$250.16%
Hermes Agent$710.45%
Codex CLI$2.650.02%
Observed cost signals
Estimated spend per 1M tracked tokens$0.38
Cache-read share96.5%
Estimated cache savingsNot available
Typical workloadcontext-heavy
Estimated tracked spend calculated from Tokscale model and provider pricing data. Actual invoices may differ.
Model Momentum
>+999%30-day growthRank: Observed model
Compared with the prior non-overlapping window
Fastest-growing client: Kimi
Official Model Details
Tokscale Insight
Kimi K3 (k3) recorded 41.2B coding tokens across 72 developers during the latest 30-day Tokscale window.
Observed confidenceHigh





