Kimi K3: 2.8 Trillion Parameters
and What It Actually Changes for Your AI Stack
Bottom line: Kimi K3 from Moonshot AI: 2.8T parameters, 1 million token context window, API at $3/$15 per 1M tokens (input/output). This is the first open-weight model that exceeds all closed flagship models in scale while costing less than GPT-5.6 Sol ($5/$30). Full weights drop July 27 — after that, fine-tuned vertical versions and self-hosted deployments become available. If you are building on AI, the infrastructure choice between "pay for closed API" and "run open weights" just became sharper.
On July 17, 2026, Moonshot AI announced Kimi K3 — a 2.8 trillion parameter model. The previous record among open-weight models was DeepSeek V4 Pro at 1.6T (April 2026). K3 is 75% larger.
Within 48 hours of the announcement, demand pushed close to the limits of Moonshot's current GPU capacity. On July 19, the company paused new subscriptions and announced that full model weights will be released by July 27 under a Modified MIT license.
This is not just another large model. It is a moment when open-weight AI stops being a compromise between power and price — and becomes a real infrastructure alternative. Here is what actually changed and what to do about it in the next seven days.
1. What happened
Moonshot AI — a Chinese AI startup founded in 2023 — released Kimi K3. The facts that matter:
Architecture. 2.8 trillion total parameters, Mixture-of-Experts design: 16 out of 896 experts activate per inference pass. Moonshot's official blog confirms the 16/896 structure but has not published an official active parameter count. Community estimates put active params at approximately 50B (calculated as 2800/896 × 16). Use that figure as a community estimate, not an official specification.
Context window. 1,048,576 tokens — exactly 1 million. For comparison: Claude 3.5 Sonnet supports 200K, GPT-4o supports 128K. K3 can process an entire mid-size codebase, a year of customer correspondence, or a full legal document archive in a single inference call.
Multimodality. Native support for text and images is confirmed by the official blog and multiple independent sources. Video is mentioned in one source only and should not be treated as a confirmed specification.
API pricing. $3 per 1M input tokens, $15 per 1M output tokens. GPT-5.6 Sol runs at $5/$30. K3 is approximately 40% cheaper on input and 50% cheaper on output compared to OpenAI's flagship tier. Important caveat: GPT-5.6 Terra at $2.50/$15 is cheaper than K3 on input. The comparison holds only against Sol-tier, not the full GPT-5.6 lineup.
Availability. Moonshot paused subscriptions on July 19 due to capacity pressure and announced two new plans: Kimi Membership (web, mobile, workplace) and Kimi Code Membership (coding workflows). The API is available. Full weights release July 27 under Modified MIT.
2. Why this is a paradigm shift
Before K3, the mental model was clear: closed models (GPT-5.6, Claude 4) offered maximum capability at premium cost; open models (Llama, DeepSeek) offered a tradeoff — cheaper but weaker on complex reasoning tasks.
K3 disrupts this on three axes simultaneously.
2.8 trillion parameters is the largest open-weight model ever released, exceeding in total parameter count what OpenAI and Anthropic keep behind closed APIs. The argument "open models cannot compete with closed ones on capability" loses its universal status — it may still hold for specific tasks, but it no longer holds as a default assumption.
A million-token context window eliminates an entire class of engineering problems: chunking strategies, retrieval-augmented generation pipelines for long documents, context management overhead. For enterprise scenarios — contract analysis, codebase audit, processing a month of support tickets — this translates directly into reduced engineering time and infrastructure complexity.
API at $3/$15 at quality competitive with GPT-5.6 Sol at $5/$30 means roughly 40-50% cost reduction on real workloads. After July 27, when full weights are available under Modified MIT, self-hosted deployment becomes an option — and for organizations with their own GPU infrastructure, inference cost drops further.
3. The new architecture in plain English
Mixture-of-Experts is a way to scale a model without proportional growth in inference cost.
Think of a library with 896 specialists. Each incoming request goes to 16 of them — whichever the router considers most relevant. The other 880 experts consume no compute during that inference pass.
The result: total model size of 2.8T parameters gives it broad knowledge and deep specialization across domains. But each individual inference call uses approximately 50B active parameters (community estimate based on 16/896 structure). This means K3 does not require GPU memory for 2.8T parameters to process a single token — only memory for the active experts plus the routing mechanism.
A large context window means the model holds all information in a single forward pass. RAG — retrieval-augmented generation — is necessary when your context window cannot fit all the data. At 1M tokens, the threshold shifts substantially: an average PDF (300-500 pages) fits entirely, a codebase of 50-100 files fits entirely. This does not eliminate RAG for all use cases, but it removes the requirement for a significant class of tasks where chunking was previously unavoidable.
4. My Content Factory case: real numbers
I run Content Factory — a pipeline that takes a topic, processes it through multiple models in parallel for different tasks, and produces content for 15+ distribution channels. Current stack: Claude API for structure and fact-checking, Gemini for tone and long-form generation, Groq for speed-sensitive micro-tasks.
The primary bottleneck in this pipeline is not quality — it is the cost of long-context inference. When I run fact verification against a full brief (5-10K tokens) plus source material (another 15-20K tokens), each pass costs $0.10-0.20 using premium models. At 50 passes per day, that is $5-10 per day on fact-checking alone.
Kimi K3 at $3/1M input is approximately 1.5-2× cheaper than Claude 3.5 Sonnet on long-context tasks for comparable workloads. I am not publishing specific savings numbers here because quality on my specific tasks needs to be tested — that test runs this week.
More important for my architecture: 1 million tokens of context means I can pass the entire publication archive from the last three months in a single request and ask the model to identify patterns in what performs well. Currently that requires either chunking and aggregating answers, or building a separate RAG system. With K3 — potentially one call. If the July 27 weights come out with clean Modified MIT licensing, I will evaluate self-hosted deployment for tasks where client data cannot go through external APIs.
5. The cost math that wakes up CFOs
Direct cost comparison for a team of 5 developers, 200 API calls per day, average 2K input / 1K output tokens per call:
Input: 200 × 2,000 × $5/1M = $2.00/day
Output: 200 × 1,000 × $30/1M = $6.00/day
Total: $8.00/day, ~$240/month
Input: 200 × 2,000 × $3/1M = $1.20/day
Output: 200 × 1,000 × $15/1M = $3.00/day
Total: $4.20/day, ~$126/month
Difference: $114/month at the same request volume. At 10× enterprise load (2,000 calls per day): $1,140/month in API cost savings.
One important context for the CFO framing: K3 is cheaper than GPT-5.6 Sol, but GPT-5.6 Terra ($2.50/$15) is in a comparable price range and cheaper on input. The economic case for K3 over Terra is the context window advantage, not pure cost. If your tasks fit within 128K-200K tokens, Terra or Luna may still be the rational choice. Build a mixed stack rather than all-in on any single model.
6. What dies, what lives
7. What to build this week
⚠️ Do not migrate production workloads to K3 before you have tested quality on your actual tasks. Parameter count and context window are not performance guarantees. Test on real data before committing.
8. B2C / B2B split
Before K3, the choice was relatively simple: Claude or GPT for quality-sensitive tasks, something from the Llama family for cost-sensitive ones. Kimi K3 adds a third option — a powerful open-weight model with a massive context window at a price point that makes it worth testing seriously.
A concrete scenario for Content Factory users: if you run materials through multiple models for different tasks, K3 is a strong candidate for long-context jobs — summarizing an entire archive, finding patterns across a large dataset, reviewing a full codebase. Want a checklist of "5 tests to evaluate a new AI model against your actual workflow"? Send the word K3 to @N8N270426_bot and it will come automatically.
Three questions worth answering internally before July 27:
- 1.Do you have tasks where long context is the bottleneck? Contract analysis, codebase audits, processing a quarter of customer support interactions.
- 2.What is your current monthly API consumption in tokens? Run the cost math from section 5 against your real numbers.
- 3.Do you have data that cannot go through an external API? If yes, July 27 is the date to start evaluating a self-hosted open-weight option seriously.
Checklist: 5 tests to evaluate any new AI model against your workflow
A ready checklist to test K3 (and any new model) on your real tasks — not benchmarks, your actual workflow. Send the word K3 to the bot — it arrives automatically.
Message @N8N270426_bot → send K3Free 20-minute AI infrastructure audit
Map your current AI stack and identify where K3 delivers real savings. No pitch — just: your current volumes, your tasks, we calculate the actual difference. Send vertical agent to the bot.
Message @N8N270426_bot → send vertical agentFrequently Asked Questions
What is Kimi K3 and why do 2.8 trillion parameters matter? ▼
Kimi K3 is an open-weight language model from Moonshot AI (China, founded 2023). 2.8 trillion parameters is the total model size — the largest ever released as open weights. The previous record was DeepSeek V4 Pro at 1.6T (April 2026); K3 is 75% larger. Important caveat: the Mixture-of-Experts architecture means only approximately 50B parameters are active per inference (community estimate, not official). Total parameters represent breadth of knowledge and specialization; active parameters determine inference cost and speed.
What does Mixture-of-Experts architecture mean for inference cost? ▼
In a standard dense model, every parameter participates in every request. In MoE (Mixture-of-Experts), the model is divided into expert modules — K3 has 896. Per request, only 16 are activated (the ones the router deems most relevant). The other 880 consume no GPU memory during that pass. Result: a 2.8T-parameter model runs at the speed and cost of a ~50B active-parameter model. This is the same architecture as DeepSeek V4 Pro and Mixtral — but at a scale previously seen only inside closed research labs.
How much cheaper is K3 vs GPT-5.6 Sol? What about Terra? ▼
Kimi K3: $3/1M input tokens, $15/1M output. GPT-5.6 Sol: $5/$30. K3 is approximately 40% cheaper on input and 50% cheaper on output compared to Sol. For a 5-developer team at 200 API calls/day: GPT-5.6 Sol costs ~$240/month vs K3 at ~$126/month — a $114/month difference. Important caveat: GPT-5.6 Terra at $2.50/$15 is cheaper than K3 on input. The K3 vs Sol comparison holds; vs Terra, K3 wins on context window (1M vs 128K tokens) not on raw input price. Build a mixed stack rather than all-in on any single model.
What changes on July 27 with the K3 weight release? ▼
On July 27, Moonshot AI plans to release full model weights under a Modified MIT license. This means: commercial use permitted, fine-tuning permitted, self-hosted deployment permitted (with attribution). The API is available right now — July 27 adds the ability to run the model locally or on your own infrastructure. Important: read the final license document when it's published on July 27 before deploying to production. 'Modified MIT' implies standard MIT with additional terms that will be known only at release time.
Should I migrate production workloads to K3 before testing quality? ▼
No. Parameter count and context window size are not performance guarantees on your specific tasks. Recommended sequence: get API access at kimi.com, select one long-context task from your current workflow (document analysis, codebase review, archive summarization), run 20 identical prompts through K3 and your current model, compare on accuracy and cost. Only after a successful test on real data should you migrate workloads. After July 27, additionally evaluate self-hosted deployment for sensitive data that cannot go through external APIs.
Sources
- kimi.com/blog/kimi-k3 — Moonshot AI official announcement
- x.com/Kimi_Moonshot — official X account, July 19 post
- VentureBeat — "Moonshot AI releases Kimi K3", July 17, 2026