Kimi K3 Beat Almost Everyone. Then the Bill Showed Up.

The Biggest "Open" Model Ever Released Isn't Open Yet.

Jul 21, 2026

Moonshot AI shipped Kimi K3 on July 16, and every headline grabbed the same word: biggest. The biggest open-source model in history. 2.8 trillion parameters. Benchmarks nipping at the heels of the best closed models on the planet.

If you route real work through LLMs, coding agents, research pipelines, anything with a monthly token bill, this breakdown does one specific job for you. By the end you’ll know exactly which work K3 deserves, which work it would quietly triple your costs on, and what the “open source” label is hiding until July 27.

The verdict up front: K3 is the strongest open-class model anyone has released, and independent numbers back that up. It’s also slow, spectacularly wordy, and roughly triple the price of the Kimi most users were running last month. And as of today, you can’t download it. The weights are a promise with a date attached. So treat K3 as an escalation tier. Route it the jobs your cheaper models keep failing, and nothing else.

Now the receipts.

What K3 actually is

K3 is a 2.8 trillion parameter mixture-of-experts model. Only a small slice of that fires per token, sixteen experts at a time, so the headline number describes total capacity, not what runs on every request. The context window is 1,048,576 tokens. Reasoning stays on at all times, with adjustable effort. It reads images natively, which matters more than it sounds once your agents start working from screenshots and UI states. The API speaks the OpenAI SDK format, so it drops into existing toolchains without surgery.

Input costs $3 per million tokens. Output costs $15 per million. A cache hit drops input to $0.30, and that discount ends up doing serious load-bearing work in the cost story. Hold that thought.

The receipts, from people who don’t work at Moonshot

Artificial Analysis scores K3 a 57 on its Intelligence Index. Only Claude Fable and GPT-5.6 Sol Max sit above it there. Vals AI ranks it second on its own index. On Arena’s frontend code leaderboard, K3 opened at number one. Its GPQA Diamond score, the graduate-level science benchmark built to resist Googling, lands at 93.5 percent.

Moonshot’s own launch table goes further. The company claims K3 performed competitively with Fable 5 and substantially outperformed Opus 4.8, GPT-5.6 Sol, and GPT-5.5. That’s the vendor talking, and their table mixes different agent harnesses (KimiCode, Claude Code, Codex, Terminus), which means some rows compare models under different test conditions. Use it to build a shortlist. Don’t use it to crown anybody.

The part the launch posts skipped

Artificial Analysis clocks K3 at roughly 39 output tokens per second. The first token takes about 2.6 seconds to arrive. That’s slow for 2026. And this model talks a lot. Running the Intelligence Index evaluations, K3 generated around 130 million tokens where the average model needs about 63 million. Picture the coworker who answers “quick question” with a whiteboard session and then a recap email about the whiteboard session. Now bill that coworker at $15 per million output tokens.

Verbosity at premium output rates is a compounding problem, because agents don’t send one prompt. They loop for hours. Moonshot knows this, which is exactly why the 90 percent cache discount exists. Turn it on before you run anything, or the invoice will teach you the lesson instead.

About that “open source” headline

As of this writing, you cannot download K3. Moonshot says the full weights arrive by July 27 under a Modified MIT license. Until the files actually appear, K3 is an API product with a very good press release. And once the weights do land, self-hosting means real hardware. Moonshot recommends 64 or more accelerators for deployment. Your gaming rig is not invited, and neither is your startup’s single rented GPU.

For almost everyone, K3 will remain a hosted model. The open label is a story about future customization rights, not about something you’ll run in the garage this summer.

Is it a good agent brain?

Yes, with supervision. K3 supports OpenAI-style function calling, JSON schema structured outputs, and dynamic tool loading, which is the exact plumbing frameworks like Hermes Agent and OpenClaw depend on. Hermes already lists moonshotai/kimi-k3 in its OpenRouter catalog, and that’s the clean path right now, because the direct Kimi provider catalogs still stop at the K2 family.

Moonshot’s own guidance carries warnings worth respecting. K3 expects its thinking history preserved, so don’t swap it into the middle of a thread another model started. The docs also flag it as overly proactive, their words, which in agent land means it may take steps you never asked for. Every credible setup guide says the same thing about that combination: keep shell access, browser control, and external writes behind explicit approvals until you’ve watched it work on your own tasks.

K3 vs GLM-5.2: brains or bargain

Z.ai’s GLM-5.2 arrived in mid-June, and it’s the other open flagship in this conversation. The split is clean. K3 wins on capability, GLM-5.2 wins on economics.

On the Artificial Analysis index, GLM-5.2 scores 51 to K3’s 57. Its weights shipped on Hugging Face on day one under a straight MIT license, no waiting period. Sources list the model at 744 billion total parameters or 753 billion, depending on who’s counting, a discrepancy I’m flagging rather than resolving for you. About 40 billion of those fire per token. Input runs $1.40 per million on Z.ai’s API. Output runs $4.40. Reported throughput is several times faster than K3’s. And GLM-5.2 is text only, no image input.

So the routing logic writes itself. Visual agent work and the genuinely hard long-horizon jobs go to K3. High-volume text work goes to GLM-5.2, and your accountant sends Z.ai a card.

Coming from K2.6 or K2.7? The upgrade math

Don’t think of K3 as an update to the K2 line. It’s a new base model with new behavior. The K2 generation runs a 256K context. K3 goes to a full million. K2 was text-focused, and K3 sees images. The frontend coding jump is real too, since the K2 line sat mid-pack on Arena’s frontend rankings and K3 opened in first.

The price moved just as hard in the other direction. K2.7 Code costs $0.95 per million input tokens. Its output runs $4 per million. It also isn’t going anywhere, and for routine coding it remains the rational default. Meanwhile, Moonshot has marked K2.5 and moonshot-v1 for retirement on August 31, and new users already can’t access them. If production traffic runs on either one, your migration clock started last week.

Context worth having

The Kimi line had serious customers before this launch. Fortune reports that Cursor used Kimi models to help build its Composer 2 coding agent. DoorDash’s CTO said in a July post that the company delegates lower-level work to K2.6. Thinking Machines tapped K2.5 to generate early post-training data for its Inkling model. Moonshot also raised $2 billion in May. That round valued the company above $20 billion. A statement from the company’s financial advisor put annual recurring revenue past $200 million, which is self-reported, so salt it accordingly.

So what do you do with this?

Do this: If you run long agent workflows, big-repo coding, or anything visual, test K3 this week through OpenRouter with caching on and a hard token budget. Send it only the jobs your current model fails.

Skip this: Self-hosting plans until the weights actually exist, and routine high-volume coding where K2.7 Code or GLM-5.2 already passes your tests. Paying K3 rates for work a $4-output model handles is just tipping Moonshot.

Wait on this: Independent head-to-head agent benchmarks, since the vendor table mixes harnesses. Also July 27 itself, when we find out whether the weights ship as promised.

Steal this line: K3 is an escalation tier, not a new default. Route it your failures and leave everything else alone.

More when the weights drop on the 27th. If they drop.

The AI Signal

Discussion about this post

Ready for more?