Kimi K3 Is Live — But the Spec Sheet Isn't
Moonshot AI's Kimi K3 landed on July 15, 2026, tied to a limited-time API recharge promotion that briefly surfaced on the company's own platform before an official announcement arrived. What we know about it comes from a patchwork of leaked promo pages, community benchmark sightings, a few well-placed researcher posts, and one developer trying to fit a 2.5-trillion-parameter model into 1.5 terabytes of Mac Studio memory.
That last detail alone signals something important: K3 is not an incremental update to the Kimi K2 family. It is, by every available signal, a different class of model — and understanding what that difference implies for builders, researchers, and the competitive frontier landscape is the goal of this piece.
We covered the initial Kimi K3 launch signal when the promo page first leaked on July 14. This article goes deeper on architecture, competitive context, and what the spec gaps actually mean.
From 1T to 2.5T: What the Scale Jump Implies
The Kimi K2 family — spanning K2, K2.5, K2.6, and K2.7 Code — held a consistent blueprint across every release: one trillion total parameters, 32 billion active per token, 384 routed experts plus one shared expert, Multi-head Latent Attention, and SwiGLU activation. That consistency made the K2 series easy to benchmark against itself. K3 breaks that pattern.
Community leaks point to roughly 2.5 trillion total parameters — a 2.5× jump in scale over the entire K2 family. That alone would make it one of the largest models ever built if confirmed. But scale is only part of the story; the architecture signals matter more.
What the Architecture Leaks Actually Say
Three distinct technical threads appear consistently across the K3 pre-release material:
- New architectural innovation — Moonshot's own promotional framing describes K3 as built on a "new architectural innovation," not a direct extension of the K2 MoE blueprint. This is consistent with researcher speculation that the company has been exploring hybrid linear attention variants.
- Hybrid linear attention — Community discussion on the r/kimi subreddit surfaced references to Moonshot publishing internal papers on a "1T internal hybrid linear model," suggesting the team has been experimenting with Mamba-style or linear-complexity attention mechanisms at scale before committing them to K3.
- Kimi Residual Attention and DSA — Leaked spec-sheet screenshots circulating July 14 reference terms including "DSA" and "Kimi residual attention," alongside claims of the sparsest MoE expert routing ratio yet and native 4-bit training from the base. These are unverified but specific enough to track.
Researcher Teortaxes, who has accurately characterized Moonshot's architectural direction before, posted on July 7 that K3 should be expected to include AttnRes (residual attention), modality vision input, and "Kimi-Linear+" at 2T+ scale — putting a plausible label on what "new architecture" actually means.
If the hybrid linear attention signals hold, K3 would be among the first frontier-scale models to ship a production-grade linear attention hybrid — something that has been theoretically attractive (O(n) instead of O(n²) complexity for long sequences) but has not yet scaled cleanly in public releases.
The 1M-Token Context Window: What It Actually Enables
The rumored 1M-token context window is, if confirmed, the headline capability upgrade. The Kimi K2 family topped out at 256K tokens — already strong by mid-2025 standards. A 1M-token window would put K3 in the same tier as Google's Gemini 2.5 Pro and the reported Gemini 3.5 Pro, which is itself rumored to be targeting a 2M context window.
Practical implications for builders
- Whole-repository code review — At 1M tokens, K3 could ingest large monorepos in a single context pass. The K2.7 Code baseline already showed strong multi-file reasoning; K3 would extend this to projects that previously required chunking strategies.
- Long-document synthesis — Legal, scientific, and financial document sets that run to hundreds of pages can be analyzed without retrieval-augmented generation workarounds.
- Multi-hour autonomous agent runs — K2.6 demonstrated 12–13 hour autonomous coding sessions with thousands of tool calls. A larger context window means the agent's working memory — its accumulated tool outputs, reasoning traces, and code state — can grow proportionally without truncation.
- Multi-agent orchestration — K2.6 shipped Claw Groups for coordinating heterogeneous agents. K3's extended context makes the orchestrator model more capable of holding a full multi-agent session history in view.
The critical unknown is what the 1M context costs at inference — latency, pricing per MTok at long contexts, and whether Moonshot will tier pricing the way competitors have. These remain unpublished.
K3 vs. the Frontier: Where It Sits Right Now
The most honest framing is that K3 sits in a competitive window alongside three simultaneous frontier moves: DeepSeek V4, the rumored GLM-5.5 (targeting August), and Gemini 3.5 Pro. Each is attacking the same long-context, long-horizon coding segment.
| Model | Developer | Total Params | Context | Status |
|---|---|---|---|---|
| Kimi K2.7 Code | Moonshot AI | 1T | 256K | Released (Jun 2026) |
| Kimi K3 | Moonshot AI | ~2.5T (unconfirmed) | ~1M (unconfirmed) | Launching July 15, 2026 |
| GLM-5.5 | Z.ai | >1T (rumored) | TBC | Targeting Aug 2026 |
| Gemini 3.5 Pro | Google DeepMind | Not disclosed | ~2M (leaked) | Targeting Jul 17, 2026 |
Early beta tester ChrissGPT described K3 as "an Opus 4.7+ coding model" that outperforms GPT-5.6 on some coding evaluations, while noting that Fable 5 and GPT-5.6 Sol still lead on Terminal-Bench 2.1. That framing is directionally useful but should be treated as anecdotal until independent harness results land. The GLM-5.5 release and Gemini 3.5 Pro will both arrive within weeks, making this the densest frontier convergence window since mid-2025.
The Open-Weight Question
The K2 family was released under a Modified MIT license — one of the most permissive open-weight licenses in the frontier model space. That decision made Kimi K2 one of the most-downloaded models of 2025 and gave Moonshot a developer ecosystem that closed competitors cannot easily match.
Whether K3 continues that pattern is the highest-stakes unknown for the developer community. A 2.5T-parameter model under a permissive license would be, by a wide margin, the largest open-weight model ever released. It would also be effectively unrunnable for most organizations — as developer Max Weinbach noted when describing the hardware ceiling of a 1.5TB Mac Studio cluster failing to accommodate a 2.5T model with 1M context.
The realistic open-weight scenario, if Moonshot follows precedent, would be quantized versions at INT4 or lower, distributed with a configuration that makes partial loading feasible. But none of this is confirmed, and the licensing terms for K3 have not been published.
What the $500M Series C Was Buying
Moonshot AI's January 2026 Series C — $500 million at a $4.3 billion valuation — was explicitly reported as funding "computing capacity and developing the K3 model." That capital signal is worth contextualizing: building and serving a 2.5T-parameter model with a 1M-token context window requires inference infrastructure that dwarfs what K2.6 demanded.
The recharge promotion tied to the K3 launch (10–30% bonus credits on ¥99–¥5,000+ top-ups through August 11) is a standard Chinese API platform growth tactic — it incentivizes API credit deposits before developers have confirmed whether K3 meets their use case. Moonshot's ability to price API access competitively while serving a model of this scale will be as consequential as the model's benchmark scores.
What We Still Don't Know
The gap list as of July 15, 2026 is long, and being honest about it matters for any builder making decisions right now:
- Confirmed parameter count and active parameter ratio — The 2.5T figure is from a Chinese tech report dated April 2026. No Moonshot primary source has ratified it.
- Confirmed context window and pricing at long contexts — Whether 1M ships at launch, and at what latency and token cost.
- Architecture specification — Expert count, routing algorithm, whether hybrid linear attention is production-deployed, and what "Kimi residual attention" refers to technically.
- License and weights availability — Whether K3 continues the Modified MIT open-weight precedent.
- Independent benchmarks — SWE-Bench Verified, Terminal-Bench 2.1, HLE, and agent-specific harnesses have not yet published K3 results.
- Multimodal scope — Image, audio, and video input capabilities are rumored but unconfirmed.
- Per-token API pricing — For reference, K2.6 launched at $0.60 input / $2.50 output per million tokens. K3's pricing has not been published.
Three Signals That Will Resolve This Picture
The K3 story moves from "leaked" to "confirmed" along three concrete paths: an official model card from Moonshot AI or the @Kimi_Moonshot account with architecture and context window specifications; a Hugging Face repository landing with a license file and weights that ratify the parameter count; and independent benchmark runs on a standardized harness (SWE-Bench Verified being the most comparable to K2.6's published results).
Until those three things land, K3 is the most technically interesting unverified frontier release of the year — and the one with the widest gap between community excitement and confirmed capability.
Related Reading
- Kimi K3 Launch Imminent: Moonshot AI's 2.5T-Parameter Model Set to Drop on July 15
- Gemini 3.5 Pro Leak: Is Google Finally Back in the AI Race?
- GLM-5.5 Could Arrive in August: Z.ai's 1 Trillion Parameter Beast Takes Aim at the West
- Chinese Models Now Own 45% of OpenRouter Traffic — and the West Hasn't Noticed
