Kimi K3 Release Date: API Launch vs Open Weights Drop
On July 16, 2026, Moonshot shipped Kimi K3 through Kimi App, Kimi Work, Kimi Code, and API. Artificial Analysis published an independent review the same day. On July 27, full model weights (Modified MIT) plus a technical report (architecture, training, evaluation) go public on Hugging Face.
Bottom line: K3 is not a Fable 5 killer. AA Intelligence Index 57.1 ranks it #3 of 189, behind Claude Fable 5 (59.9) and GPT-5.6 Sol (58.9). It delivers frontier-adjacent capability at roughly one-third the cost, plus two things closed models cannot offer: downloadable open weights and a 1M-token context window.
| Date | Event |
|---|---|
| 2026-07-16 | K3 API and Kimi product suite launch; Artificial Analysis benchmark release |
| 2026-07-17 | WAIC opens in Shanghai; state media frames K3 as a national AI milestone |
| 2026-07-27 | Full weights on Hugging Face (Modified MIT) + technical report |
API is live now: Model ID kimi-k3 on platform.kimi.ai — no need to wait for weights to start building.
Weights ≠ instant local run: vLLM support for KDA and prefix caching lands with the weight release; Ollama and GGUF builds will follow K2-style community ports.
Unusually honest vendor stance: Moonshot openly admits trailing Fable 5 and Sol overall, citing harness sensitivity and over-eager behavior on ambiguous prompts.
Geopolitical angle: Release timing aligns with WAIC. US regulators briefly pulled Anthropic Fable/Mythos models in June (restored July 1) — fueling the narrative that regulators can shut down closed APIs but not published open weights.
Moonshot comeback: After DeepSeek R1 shook market share in early 2025 (rank fell to #7 domestically), the K2 → K2.5 → K3 open-weight roadmap rebuilt credibility.
What Is Kimi K3? Key Specs at a Glance
K3 uses Stable LatentMoE: 896 experts, 16 activated per token (~1.8% sparsity). Attention stack: Kimi Delta Attention (KDA, hybrid linear attention) + Attention Residuals (AttnRes) + Gated MLA. Weights ship as MXFP4 with MXFP8 activations (native low-precision training). Scaling efficiency is ~2.5× better than K2; KDA delivers up to 6.3× decode speedup at 1M context.
| Spec | Value |
|---|---|
| Total parameters | 2.8 trillion — largest open-weight model to date |
| Architecture | Sparse MoE: Stable LatentMoE, 896 experts / 16 active per token |
| Attention | KDA + AttnRes + Gated MLA |
| Context window | 1,048,576 tokens (1M) |
| Modalities | Native vision (text + image; video in product), text output |
| Weight format | MXFP4 weights + MXFP8 activations |
| Training stability | Quantile Balancing, Per-Head Muon optimizer, SiTU activation |
| License (July 27) | Modified MIT — verify LICENSE text on release day |
Use open weights in headlines, not open source. The distinction matters on r/LocalLLaMA and Hacker News — and it targets the high-intent query "kimi k3 open weights."
Kimi K3 Benchmarks: How It Compares to Claude Fable 5 and GPT-5.6
Data cross-referenced from Artificial Analysis (July 16) and Moonshot release materials. Benchmarks run through different harnesses — always cite source and date when comparing scores.
| Model | AA Intelligence Index | Rank |
|---|---|---|
| Claude Fable 5 | 59.9 | #1 |
| GPT-5.6 Sol | 58.9 | #2 |
| Kimi K3 | 57.1 | #3 / 189 |
Where K3 wins or ties:
Frontend Code Arena: #1 — blind dev preference for UI code over Fable and Sol
Automation Bench, SpreadsheetBench 2: #1
BrowseComp: 91.2 (#1) — 90.4+ with 1M context no-compression strategy
SWE Marathon: 42.0 — far ahead (GPT-5.5 / GLM-5.2 collapse to teens)
Terminal Bench 2.1: 88.3 — near parity with Sol (88.8)
Program Bench: 77.8 — edges Sol (77.6)
FrontierSWE: 81.2 — beats Sol (71.3), trails Fable 5 (86.6)
Where K3 still lags:
GDPval v2 Elo: 1668–1687 vs Fable 5 (1760), Sol (1748) — long-horizon judgment remains Fable territory
DeepSWE: 67.5 vs Sol 73.0
Hallucination rate up vs K2.6 (vendor acknowledged); Reddit reports more hallucinations than top closed models in self-hosted apps
Conversation polish and session variance still below Fable 5 / Sol
| Dimension | Kimi K3 | Claude Fable 5 | GPT-5.6 Sol |
|---|---|---|---|
| Intelligence Index | 57.1 (#3) | 59.9 (#1) | 58.9 (#2) |
| Cost per task (AA) | $0.94 | ~$2.75 | ~$1.04 |
| vs Fable 5 | 65.8% cheaper; 9.4% below Sol | ||
| Open weights | July 27 | Closed | Closed |
| Context | 1M tokens | ~200K class | 128K–1M by tier |
Kimi K3 API Pricing and July 27 Release Checklist
Pricing aligns with Western quality-tier APIs — highest among Chinese vendors, yet still well below Claude Opus 4.8 per-task cost. Coding workloads report 90%+ cache hit rates, slashing effective spend.
| Item | Price (per 1M tokens) |
|---|---|
| Input (cache miss) | $3.00 |
| Input (cache hit, automatic) | $0.30 |
| Output | $15.00 |
What happens on July 27:
Full 2.8T weights on Moonshot Hugging Face org under Modified MIT (terms TBC)
Technical report — architecture, training, evaluation details
vLLM ecosystem — KDA + prefix caching support ships with weights
Community follow-ons — Ollama, GGUF quant builds expected like K2 series
Verify LICENSE text — commercial redistribution scope on release day
Independent long-context retest — cross-check community benchmarks vs official numbers
Sources: kimi.com/en/blog/kimi-k3, platform.kimi.ai, Artificial Analysis (July 16), VentureBeat, Northflank self-hosting analysis, r/LocalLLaMA, Hacker News.
Can You Run Kimi K3 Locally? Hardware Requirements and Why It Matters
Not on consumer hardware. 4-bit weights are ~1.4 TB. Moonshot recommends 64+ accelerator super-node deployment with expert parallelism plus tensor parallelism. Reference: K2.7 Code (1T params) needed ~577 GB VRAM at INT4; K3 is 2.8× that scale.
For most teams the answer is API ($3/$15). Self-hosting only makes sense for strict data residency, fine-tuning on proprietary data, or volume where owned hardware beats cloud inference bills.
2.8T params, 896 experts / 16 active, 1M context — quick reference line one
~1.4 TB at 4-bit; 64+ accelerators recommended — any "run on your laptop" headline is clickbait
Frontend Code Arena #1; SWE Marathon 42.0 — long-session coding lead over closed rivals
Industry impact (four angles):
Open vs closed gap nearly closed at the frontier — from percentage-point chasms to 2–3 index points; harder to justify closed-model premiums on capability alone
Regulatory narrative — published weights outlive API bans
Chinese vendor wave — GLM-5.2, DeepSeek V4 Pro, MiniMax closing in; K3 is the parameter peak
Moonshot strategic reset — open-weight cadence after DeepSeek R1 disruption
Maintaining a 64-GPU inference cluster carries hidden ops cost — power, networking, version pinning, on-call. If your team needs stable Mac hosts for iOS CI/CD and AI Agent orchestration while calling K3 via API, MESHLAUNCH cloud Mac Mini rental is usually the better production path: dedicated Apple Silicon, 24/7 uptime, flexible daily/weekly/monthly terms.
July 27, 2026 on Moonshot Hugging Face. API has been live since July 16 — two different milestones (download vs call).
July 27 delivers open weights, not fully open source (no training code/data). Modified MIT terms must be read on release day. See our Kimi K3 review for architecture depth.
$3/M input, $0.30/M cached input, $15/M output. ~$0.94 per task in AA testing. Details on agent dev environments at our pricing page.
No. ~1.4 TB at 4-bit requires datacenter-scale GPU clusters. Wait for community distilled GGUF builds if you need smaller footprints — with major capability tradeoffs.
Overall index: no (#3). Coding and automation benches: often yes. Long-horizon reasoning and stability: still Fable/Sol territory. Moonshot says so publicly. Hybrid setup guidance in our help center.