On July 16, 2026, Moonshot AI launched Kimi K3 — a 2.8-trillion-parameter Mixture-of-Experts model with a 1M-token context window and native vision. Eleven days later, on July 27, the full open weights landed on Hugging Face, making it the largest open-weight model ever published.
In this guide I give you the exact spec sheet, what K3 improves over K2.6 and K2.7 Code, its lab-reported and third-party scores with honest labels, a verified quickstart against the official API, and the limits you should know before building on it.
1. Kimi K3 at a Glance: the Spec Sheet
Kimi K3 is Moonshot AI’s most capable model to date and, by parameter count, the world’s first open 3T-class model. Every figure below comes from the official model card, the Kimi-K3 GitHub repo, and the platform docs linked in Sources — no K2-era numbers recycled as current.
Parameters
2.8T total MoE · 896 experts, 16 active per token (104B active)
Context
1M tokens (1,048,576) · text + image + video in
Architecture
Kimi Delta Attention + Attention Residuals + Stable LatentMoE
License
Kimi K3 License (modified MIT) — open-weight, commercial use allowed
API price
$3 / 1M input · $0.30 cache hits · $15 / 1M output — model id kimi-k3
Where it lives
Hugging Face moonshotai/Kimi-K3 + OpenAI-compatible API
Why always-on thinking matters for your bill
K3 reasons on every request, and reasoning tokens are billed as output at $15 per million. Budget output generously — a deep agent run can easily produce far more output tokens than a plain chat answer.
Timeline in one line: Kimi K3 API launch on July 16, 2026 → full weights on Hugging Face on July 27, 2026 → the model this guide covers. Its predecessors were K2.6 (April 2026) and K2.7 Code (June 2026) — the next section frames the comparison on those two.
2. What Improved vs K2.6 and K2.7 Code
One generation back, K2.6 shipped with 1T total parameters (32B active) and a 256K window; K2.7 Code (June 2026) specialized that line for programming agents. K3 jumps to 2.8T total with 104B active per token and a full 1M context — roughly 4x the window. Here are the headline numbers, labeled exactly as they are:
DeepSWE 1.0
Lab-reported. Long-horizon software engineering — compare with independent reruns before citing it as fact.
GPQA Diamond
Lab-reported. Graduate-level science QA — strong, but first-party until independently reproduced.
Frontend Code Arena
Third-party (LMArena). #1 overall, ahead of Claude Fable 5 — blind human preference on front-end code.
Intelligence Index
Third-party aggregate (Artificial Analysis). Tied with GLM-5.3 at the top of the open-weights board.
Context window
4x the 256K of K2.6. Matches the 1M windows of the closed flagships — the old long-context edge is now a tie.
Reasoning control
Always-on thinking with a reasoning_effort flag (default max). At launch only max existed; low and high arrived within days.
The number that convinced me
1679 on the Frontend Code Arena — #1 overall, not just #1 among open models, and a 17-place jump over K2.6. Vendor tables are marketing; blind human votes on shipped UI code are the closest thing this industry has to a real exam.
Framed against its own family: K2.6 (April 2026, 1T/32B, 256K, modified MIT) made Moonshot the open-weights price leader; K2.7 Code (June 2026) aimed the line at programming agents. K3 keeps the weights open but moves upmarket — about 3x the input price of the K2 family — trading the discount label for frontier scores.
3. Quickstart: OpenAI-Compatible API in Minutes
Kimi’s API speaks the OpenAI chat-completions protocol, so any OpenAI SDK works — you only swap the base URL and the key. Every line below is taken from the official platform docs, including the verified global endpoint.
Option A — Python with the OpenAI SDK
Install openai>=1.0, export MOONSHOT_API_KEY from the Kimi console, and run the minimal call straight from the docs:
pip install --upgrade "openai>=1.0"
export MOONSHOT_API_KEY="your-kimi-key"
import os
from openai import OpenAI
client = OpenAI(
api_key=os.environ["MOONSHOT_API_KEY"],
base_url="https://api.moonshot.ai/v1",
)
completion = client.chat.completions.create(
model="kimi-k3",
messages=[{"role": "user", "content": "Introduce Kimi K3 in one sentence."}],
)
print(completion.choices[0].message.content)Option B — The same call with cURL
No SDK needed. Identical model id and endpoint, plain HTTP:
curl https://api.moonshot.ai/v1/chat/completions \
--header "Authorization: Bearer $MOONSHOT_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"model": "kimi-k3",
"messages": [{"role": "user", "content": "Introduce Kimi K3 in one sentence."}]
}'Option C — Tune reasoning effort and caching
K3 always thinks — control cost with reasoning_effort and let automatic context caching discount repeated input to $0.30 per million:
completion = client.chat.completions.create(
model="kimi-k3",
messages=[{"role": "user", "content": "Refactor this module."}],
reasoning_effort="low", # "low" | "high" | "max" (default)
)
# Repeated long prefixes hit automatic context caching:
# cache-hit input bills at $0.30 / 1M instead of $3.00 / 1M.Endpoint detail worth knowing
Some third-party guides cite https://api.kimi.ai/v1 — the official platform docs use https://api.moonshot.ai/v1 for the OpenAI-compatible protocol (and https://api.moonshot.ai/anthropic for the Anthropic one). Point your client at the documented host or authentication will fail.
That is the whole setup: one key, one base URL, model id kimi-k3. If you already call OpenAI, migration is literally replacing base_url and api_key — the docs even ship a dedicated migration page for it.
4. Honest Limits
K3 is the strongest open-weights release of 2026, but “strongest open” is not “free of trade-offs”. Here is where it costs you — in money, hardware, or trust.
You will not self-host it on a workstation
The weights are roughly 1.5 TB in native MXFP4 across 96 safetensors shards. Realistic serving means multi-node GPU clusters with vLLM or SGLang — for almost everyone the hosted API is the sane path.
Half the famous numbers are first-party
DeepSWE 67.5 and GPQA 93.5 are Moonshot lab runs. The Arena 1679 is independent and strong, but re-run the two benchmarks that match your workload before migrating a team.
Frontier scores, frontier pricing
At $3/$15 per million tokens, K3 costs about 3x the K2 family on input and sits near Claude Sonnet-tier rates. The $0.30 cache-hit discount only helps if you reuse long prefixes.
Always-on thinking taxes output
There is no cheaper non-thinking K3 variant. Reasoning tokens bill as output, so deep agent loops get expensive fast — set reasoning_effort to low for drafts.
The license is custom, not plain MIT
The Kimi K3 License is MIT-derived and allows commercial use, but community readings flag extra conditions for large Model-as-a-Service operators. Read the LICENSE file on Hugging Face before shipping a product on it.
The most common mistake
Quoting K2.6 specs as K3 specs. K2.6 was 1T/32B with 256K context at $0.95/$4 — K3 is 2.8T/104B with 1M context at $3/$15. Mixing the two generations understates both the model and the bill by roughly 3x.
None of these is a dealbreaker — they are the normal price of frontier open weights. The open release (weights plus technical report plus serving kernels) means the community can verify claims instead of taking them on faith, which is exactly what I recommend you do on your own workload.
Verdict
If you want frontier-adjacent intelligence with downloadable weights, Kimi K3 is the default open answer of late 2026: a 2.8T MoE with 1M context, native vision, always-on thinking, an Arena #1 in front-end code, and a five-minute OpenAI-compatible quickstart.
My recommendation: prototype against the hosted API with reasoning_effort on low and cache-friendly prompts for two weeks, keep your current model as baseline, and compare completed tasks — not benchmark screenshots. Self-hosting can wait until your volume justifies a cluster.
Bottom line
Use it for
- • Agentic coding + front-end generation
- • 1M-context knowledge work
- • Open weights with API fallback
Skip it for
- • Workstation self-hosting
- • Cheapest-per-token workloads
- • Day-one production without evals
Remember
- • Endpoint is api.moonshot.ai
- • Cache hits cost $0.30
- • Label lab vs independent scores



