TokenMix Research Lab · 2026-07-17

Kimi K3 Review 2026: 2.8T Params, $3/$15 API, Benchmarks

Kimi K3 Review 2026: 2.8T Params, $3/$15 API, Benchmarks

Last Updated: 2026-07-17 Author: TokenMix Research Lab Data verified: 2026-07-17 - Kimi K3 technical blog, Kimi API pricing and quickstart documentation, live TokenMix model catalog, Artificial Analysis, Axios, and Xinhua

Kimi K3 is live with 2.8T parameters, 1M context, and a $3/$15 API. The launch is substantial, but not a clean victory: only max reasoning is available, the weights are promised by July 27, and independent testing finds high intelligence alongside slower-than-average, unusually verbose output.

Moonshot AI released Kimi K3 on July 16, 2026 across Kimi, Kimi Work, Kimi Code, and the official API. The model uses Kimi Delta Attention, Attention Residuals, and a sparse MoE design that activates 16 of 896 experts; Moonshot has not disclosed the active parameter count. Official API pricing is $0.30 per million cache-hit input tokens, $3 per million uncached input tokens, and $15 per million output tokens (Kimi technical blog, Kimi pricing docs). Moonshot's benchmark table puts K3 ahead of the compared models on BrowseComp, Program Bench, and OmniDocBench, but behind GPT-5.6 Sol on DeepSWE, Terminal-Bench 2.1, GPQA Diamond, and MMMU-Pro. An early independent run from Artificial Analysis scores K3 at 57 on its Intelligence Index, measures 62 output tokens per second, and flags 130M evaluation output tokens versus a 63M comparison median. That last number matters: K3's token price is attractive, but verbosity can erase part of the cost advantage.

Table of Contents

Quick Verdict

Kimi K3 is a credible frontier API today, but it is not yet a downloadable open-weight release.

Claim Status Source
Kimi K3 launched on July 16, 2026 Confirmed Kimi release, Xinhua report
Total parameter count is 2.8T Confirmed Kimi technical blog
The old 3-4T or 4T parameter rumor was accurate False Official value is 2.8T
Context window is 1,048,576 tokens Confirmed Kimi API pricing
API ID is kimi-k3 Confirmed Kimi quickstart
API price is $3 input and $15 output per 1M tokens Confirmed Kimi release
Cache-hit input costs $0.30 per 1M tokens Confirmed Kimi release
Full weights are downloadable now False as of 2026-07-17 Moonshot promises release by July 27
K3 beats every proprietary frontier model False Moonshot's own table shows several losses
K3 is cheap per successful task Likely, workload-dependent Token price is low; independent testing finds high verbosity

The most important correction is the open-weight label. Moonshot calls K3 an open model and has committed to release the full weights by July 27. Until a real repository, license, checksums, and loadable files exist, the accurate status is weights announced, not yet published.

What Actually Shipped

The release is broader than a chat model: K3 ships across four products and one production API, while lower reasoning modes and the technical report remain pending.

Surface or feature Launch status Verified detail Confidence
Kimi web and mobile Available Kimi.com plus iOS, Android, HarmonyOS Confirmed
Kimi Work Available Desktop version 3.1.0 or later Confirmed
Kimi Code Available Select K3 with /model Confirmed
Kimi API Available Model ID kimi-k3 Confirmed
Native vision Available Text and image input, text output Confirmed
1M context Available 1,048,576-token billing tier Confirmed
Reasoning effort max only Low and high are planned later Confirmed
Full model weights Not yet available Promised by 2026-07-27 Confirmed commitment
Technical report Not yet published Architecture and training details pending Confirmed
Independent safety evaluation Not found at publication time Do not infer from K2.5 studies Unconfirmed

This matters for procurement. API users can evaluate K3 now. Self-hosters cannot yet inspect the license or estimate real serving performance from released weights. The Kimi K3 integration guide should therefore be read as an API integration path until the promised repository exists.

Architecture and Deployment Reality

K3's 2.8T headline describes stored parameters, not per-token compute, because Moonshot disclosed expert routing but not active parameter count.

Architecture field Kimi K3 value What it means Status
Total parameters 2.8T Very large checkpoint and optimizer footprint Confirmed
Expert pool 896 experts High-sparsity MoE Confirmed
Experts activated 16 per routing layer Only a subset runs for each token Confirmed
Active parameters Not disclosed Cannot compare dense-equivalent compute honestly Unknown
Attention KDA plus Gated MLA Hybrid long-context attention Confirmed
Residual path Attention Residuals Selective retrieval across model depth Confirmed
Weight format MXFP4-aware training Targets lower-memory inference Confirmed
Activation format MXFP8 Vendor's serving design Confirmed
Recommended deployment Supernode with 64+ accelerators Not a normal workstation model Confirmed recommendation
Claimed scaling gain vs K2 About 2.5x Moonshot internal scaling result Vendor-reported

The raw storage floor is easy to calculate. At four bits per parameter, 2.8T x 4 / 8 equals about 1.4 TB decimal of weight data before quantization metadata, runtime buffers, expert routing, and the 1M-context KV state. That does not prove the final checkpoint size, but it explains why Moonshot recommends 64 or more accelerators.

KDA and Attention Residuals are more important than the parameter headline. Moonshot says KDA reduces long-sequence attention cost, while AttnRes retrieves earlier representations selectively instead of accumulating them uniformly. The architecture is plausible and technically specific. Real throughput, memory use, and hardware compatibility remain Likely, not Confirmed, until weights and serving code are public.

Kimi K3 API Pricing

K3 costs $3/$15 per million uncached input/output tokens, with a 90% cache-hit discount, but it is 3.1-3.7x more expensive than K2.6 on official RMB rates.

Kimi API item Kimi K2.6 Kimi K3 K3 / K2.6 Status
Cache-hit input / 1M RMB 1.10 RMB 2.00 / $0.30 1.82x Confirmed
Cache-miss input / 1M RMB 6.50 RMB 20.00 / $3.00 3.08x Confirmed
Output / 1M RMB 27.00 RMB 100.00 / $15.00 3.70x Confirmed
Context 262,144 1,048,576 4x Confirmed
Reasoning mode Thinking and non-thinking Always on, max only Different contract Confirmed

The dollar and RMB columns come from Moonshot's English launch page and Chinese API documentation. They are not currency conversions calculated by TokenMix. K3 does not use long-context price tiers: the same token rate applies across the 1M window.

Frontier API Cache-hit input / 1M Uncached input / 1M Output / 1M Price position Status
Kimi K3 direct $0.30 $3.00 $15.00 Mid-priced frontier Confirmed
GPT-5.6 Terra $0.25 $2.50 $15.00 Slightly cheaper input Confirmed
Claude Opus 4.8 $0.50 $5.00 $25.00 1.67x K3 output Confirmed
Claude Fable 5 $1.00 $10.00 $50.00 3.33x K3 output Confirmed
TokenMix Kimi K3 route Not separately listed $2.65 $13.24 Below direct list rate at verification Confirmed live catalog, may change

The TokenMix row was read from the live model catalog on July 17 and should be checked again before production. Current availability is moonshot/kimi-k3; a catalog price is not a promise that future rates or cache accounting stay unchanged. For the older family, see the Kimi API pricing guide.

Kimi K3 Benchmarks

Moonshot's table shows a strong but uneven model: K3 wins three selected rows below and loses four to GPT-5.6 Sol or Fable 5.

Benchmark Kimi K3 max Fable 5 max GPT-5.6 Sol max Opus 4.8 max Winner in table Evidence
DeepSWE 67.5 70.0 73.0 59.0 GPT-5.6 Sol Vendor compilation
Program Bench 77.8 76.8 77.6 71.9 Kimi K3 Vendor compilation
Terminal-Bench 2.1 88.3 84.6 88.8 84.6 GPT-5.6 Sol Mixed harnesses
FrontierSWE 81.2 86.6 71.3 66.7 Fable 5 Mixed harnesses
BrowseComp 91.2 88.0 90.4 84.3 Kimi K3 Vendor compilation
GPQA Diamond 93.5 92.6 94.1 91.0 GPT-5.6 Sol Vendor compilation
MMMU-Pro 81.6 81.2 83.0 78.9 GPT-5.6 Sol Vendor compilation
OmniDocBench 91.1 89.8 85.8 87.9 Kimi K3 Vendor compilation

Every number in this table is Vendor-reported, even where Moonshot cites an external leaderboard. The footnotes disclose different agent harnesses: KimiCode, Claude Code, and Codex are used depending on model and benchmark. That makes the table useful for direction, not a controlled one-variable comparison.

The honest verdict is narrower than the launch headlines. K3 looks especially competitive in browsing, document understanding, program synthesis, and long-horizon coding. It does not sweep scientific reasoning, terminal work, or general coding. Axios reached a similar boundary: the launch is important, but hours-old benchmark claims can overstate production reliability (Axios).

Independent Reality Check

Artificial Analysis independently places K3 near the frontier, but also measures two practical costs that Moonshot's benchmark chart does not foreground: speed and verbosity.

Independent metric Kimi K3 result Comparison Interpretation Status
Intelligence Index v4.1 57 Comparable-model average 30 Frontier-level result Independent
Output speed 62.0 tokens/s Comparable median 72.2 Slower than median Independent
Time to first token 1.99s Comparable median 2.62s Faster initial token Independent
Evaluation output tokens 130M Comparable median 63M About 2.06x median Independent
Input price $3.00/M Comparable median $1.75/M Above median Confirmed price, independent comparison
Output price $15.00/M Comparable median $8.40/M Above median Confirmed price, independent comparison
Weight status label Proprietary Weights absent today Temporary until files ship Independent classification

The 130M-token result is the cost warning. A model that generates roughly twice the median output can be cheap per token and still expensive per completed task. That does not mean K3 is wasteful on every workload; it means cost projections must use real usage logs rather than list prices alone.

Artificial Analysis currently labels K3 proprietary because no weights are public. Moonshot's July 27 commitment could change that classification. Until then, both statements can be true: Moonshot intends an open-weight release; the model is API-only today.

Cost Per Workload

At official rates, K3 costs $60 for 10M uncached input plus 2M output tokens and $384 for a 100M/20M workload with 80% cache hits.

Monthly workload Kimi K3 GPT-5.6 Terra Opus 4.8 Fable 5
10M input + 2M output, uncached $60 $55 $100 $200
100M input + 20M output, uncached $600 $550 $1,000 $2,000
100M input + 20M output, 80% cached input $384 $370 $640 $1,280
1B input + 200M output, uncached $6,000 $5,500 $10,000 $20,000

Cost calculation 1: 10 x $3 + 2 x $15 = $60 for a small uncached K3 workload.

Cost calculation 2: with 80M cache hits and 20M fresh input, 80 x $0.30 + 20 x $3 + 20 x $15 = $384.

Cost calculation 3: a 1B-input, 200M-output uncached month is 1,000 x $3 + 200 x $15 = $6,000. If 90% of input hits cache, it falls to 900 x $0.30 + 100 x $3 + 200 x $15 = $3,570.

Those calculations still assume equal token consumption. If K3 emits twice as many tokens as another model on your workload, output cost can reverse the list-price advantage. Production evaluation should track cost per accepted task, not cost per million tokens.

API Contract and Migration

K3 is OpenAI-SDK compatible, but it is not a drop-in K2.6 session switch because reasoning history and sampling rules changed.

import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["TOKENMIX_API_KEY"],
    base_url="https://api.tokenmix.ai/v1",
)

response = client.chat.completions.create(
    model="moonshot/kimi-k3",
    reasoning_effort="max",
    messages=[
        {"role": "user", "content": "Review this migration plan and list three failure modes."}
    ],
)

print(response.choices[0].message.content)
curl https://api.tokenmix.ai/v1/chat/completions \
  -H "Authorization: Bearer $TOKENMIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "moonshot/kimi-k3",
    "reasoning_effort": "max",
    "messages": [{"role": "user", "content": "Return a five-step canary plan."}]
  }'
Migration check K2.6 behavior K3 behavior Required action Status
Model ID kimi-k2.6 kimi-k3 Change explicitly Confirmed
Reasoning parameter thinking supported Use reasoning_effort Remove K2.x parameter Confirmed
Effort levels Thinking/non-thinking max only today Do not send low/high yet Confirmed
Assistant history Standard history Full assistant message required Preserve reasoning/tool fields Confirmed
Sampling Configurable in older flows Fixed recommended values Do not override Confirmed
Vision URL Workflow-dependent Public image URL unsupported Use base64 or ms:// Confirmed
Web search Previously documented Being updated Keep out of production path Confirmed warning
Context cache Automatic Automatic, stable prefix needed Keep prefix byte-stable Confirmed

Moonshot warns that K3 was trained with preserved thinking history. If a harness drops that history, or if a session switches from another model to K3 mid-conversation, quality can become unstable. Start a fresh K3 session and canary 100-300 real tasks before replacing the Kimi K2.6 route.

Where Kimi K3 Wins and Loses

K3 is strongest for long, tool-heavy work where 1M context and cache reuse matter; it is a poor default for short, latency-sensitive, tightly bounded tasks.

Use case K3 verdict Better alternative when needed Why Confidence
Large-repository coding Strong candidate Fable 5 or GPT-5.6 Sol for hardest cases Strong coding and 1M context Likely
Web research and browsing Strong candidate Human verification for final claims BrowseComp lead in vendor table Vendor-reported
Document and visual analysis Strong candidate GPT-5.6 Sol for top multimodal score OmniDocBench strength Vendor-reported
Long-running tool agent Strong candidate K2.7 Code for faster coding loops Tool choice and dynamic loading Confirmed features
Short autocomplete Poor fit K2.7 Code HighSpeed or smaller model Always-on max reasoning Confirmed
Bulk classification Poor fit K2.6 or budget model Price and verbosity overhead Confirmed economics
Strictly bounded automation Use with guardrails More conservative model Official excessive-proactiveness warning Confirmed limitation
Local single-workstation use Not practical Smaller open-weight model 2.8T storage and 64+ accelerator guidance Confirmed direction

One official limitation deserves more attention than a benchmark delta: K3 can be excessively proactive on ambiguous tasks. For production agents, specify permission boundaries in the system prompt or AGENTS.md, require confirmation for destructive actions, and log every tool call.

Weights, Risks, and Falsifiers

The largest unresolved issue is not capability; it is whether the July 27 weight release arrives with a usable license, serving stack, and reproducible technical report.

Claim or risk Current status What confirms it What falsifies it
Full weights ship by July 27 Confirmed commitment Official HF/GitHub files and checksums Deadline passes without files
K3 is open-weight in practice Likely future License permits intended use; loaders work Restrictive or incomplete release
2.5x scaling efficiency Vendor-reported Reproducible report and ablations Independent reproduction fails
1M context is useful, not nominal Likely Long-context retrieval and agent tests Quality collapses deep in context
API cost advantage survives Likely Lower cost per accepted task Verbosity/retries erase savings
Lower effort modes arrive Confirmed plan Docs expose low/high No rollout or changed contract
Web search becomes production-ready Pending Warning removed and tests pass Continued outdated-tool warning
K3 beats all frontier rivals False Moonshot's own mixed results Already falsified

The old version of this article predicted 3-4T parameters and a May release. Both are False after launch: K3 is 2.8T and released July 16. That correction is not cosmetic. It is why parameter rumors, prediction-market odds, and screenshots should never be elevated to Confirmed without an official model page.

Final Recommendation

Test Kimi K3 now if your workload is long-horizon coding, research, document analysis, or tool use. Do not migrate every K2.6 or K2.7 workload. K3 costs 3-4x more than K2.6 on official RMB token rates, only supports max reasoning today, and can generate unusually large outputs. Run a fresh-session canary, measure cost per accepted task, and revisit self-hosting only after the promised July 27 weights and license are public.

FAQ

Is Kimi K3 officially released?

Yes. Moonshot AI released Kimi K3 on July 16, 2026 across Kimi, Kimi Work, Kimi Code, and the Kimi API. The official API model ID is kimi-k3.

How many parameters does Kimi K3 have?

Kimi K3 has 2.8 trillion total parameters. Moonshot says 16 of 896 experts are activated, but it has not published the active parameter count. Earlier 3-4T claims were wrong.

What is Kimi K3 API pricing?

Official pricing is $0.30 per million cache-hit input tokens, $3 per million uncached input tokens, and $15 per million output tokens. Chinese documentation lists the same tiers as RMB 2, RMB 20, and RMB 100.

Is Kimi K3 open source or open weight?

Not as a downloadable model yet. Moonshot calls K3 open and promises full weights by July 27, 2026, but no official K3 checkpoint was visible on its Hugging Face organization when this article was verified. Check the files and license after release.

Does Kimi K3 beat GPT-5.6 Sol or Claude Fable 5?

Not across the board. Moonshot reports K3 wins on selected benchmarks such as BrowseComp and Program Bench, while GPT-5.6 Sol or Fable 5 leads DeepSWE, Terminal-Bench, FrontierSWE, GPQA, and other rows. Harness differences limit direct comparison.

Does Kimi K3 support a 1M-token context window?

Yes. The API documentation lists 1,048,576 tokens with no long-context price tier. Useful-context quality still requires independent testing on retrieval and long agent sessions.

Should I migrate from Kimi K2.6 to K3?

Only for workloads that benefit from stronger long-horizon reasoning, vision, or 1M context. K3 is roughly 3.08x more expensive for uncached input and 3.70x for output in official RMB pricing, so short or bulk tasks should remain on K2.6 or another cheaper route.

Can I call Kimi K3 through TokenMix?

Yes. The live TokenMix catalog lists moonshot/kimi-k3 with vision, tools, JSON, streaming, reasoning, structured output, and prompt caching support. Verify current availability and price in the catalog before production because routing and rates can change.

About TokenMix

TokenMix.ai provides access to Kimi, Claude, OpenAI, Gemini, DeepSeek, Qwen, GLM, and other models through one OpenAI-compatible endpoint at https://api.tokenmix.ai/v1. Check the live model catalog, pricing page, and API documentation before selecting a production route.

Sources

Related Articles