Kimi K3 took first place on frontend coding at a third of the price, and the licence has a catch

tldr: Moonshot AI's Kimi K3 took first place in the Frontend Code Arena, ahead of Claude Fable 5 and GPT-5.6 Sol. The API costs $3 per million input tokens and $15 per million output, which is 30% of Fable 5's rate. The open weights landed on 27 July 2026, under a custom licence rather than MIT or Apache: Model-as-a-Service businesses past $20 million in revenue need a separate agreement with Moonshot before commercial use.

What did Kimi K3 score, and what does it cost?

The Frontend Code Arena ranks models head to head on real frontend work. K3 came first. Tom's Hardware reported specific point totals behind that result, though the arena's own figures are not public, so the ranking is the part to lean on rather than the margin.

Push a million tokens in each direction and K3 bills $18 where Fable 5 bills $60. That ratio holds on the input column and the output column independently, which is unusual; most cheaper models save you money on one and claw it back on the other.

The price works because most of K3 sits idle. It is a sparse mixture-of-experts model, so a request wakes a fraction of the network rather than all 2.8 trillion parameters. The context window is a million tokens, putting it alongside Opus 5 for whole-repository work, and Moonshot says the arena result came from a single-agent setup using that full window with no context compression.

The licence landed, and it is not open source

VentureBeat and Tom's Hardware both described K3 as the largest open-source model ever released. The weights arrived on 27 July 2026 at 16:29 UTC in the official moonshotai organisation, and the licence file that came with them settles the question. It is a custom "Kimi K3 License", and the answer is no.

Two commercial gates sit in it. A company that operates a Model-as-a-Service business and whose revenue passes $20 million across any twelve consecutive months must sign a separate agreement with Moonshot before any commercial use of the weights. And any product past 100 million monthly active users or $20 million in monthly revenue must display "Kimi K3" in its interface, the clause carried over from K2's Modified MIT licence. Internal use, where the model and its outputs never reach a third party, is exempt from both.

The first gate is new, and it is the one that matters. A revenue-conditioned restriction on commercial use is exactly what the Open Source Definition does not allow, so K3's terms came out tighter than K2's, not looser. Open weight, certainly: 1.4 TB, free to download and run. Open source, no.

Self-hosting needs about 1.4 TB of GPU memory

The weights run about 1.4 TB under MXFP4, down from roughly 5.6 TB at FP16, the fourfold saving you would expect dropping from 16-bit to 4-bit. That is the floor for loading the file. KV cache and activations come out of whatever is left.

In practical terms it takes eighteen 80 GB accelerators just to hold the weights. A single node of eight 192 GB cards, about 1.5 TB, fits them with almost nothing spare, which leaves no room to actually serve traffic. Community write-ups putting a comfortable configuration nearer 5 TB are describing headroom rather than a minimum, and Moonshot has not published a reference deployment.

So the API at $3 and $15 undercuts the hardware for anyone not already operating a cluster. Open weights buy you auditability, fine-tuning, and somewhere to put data that cannot leave your network. Saving money is not on that list.

What this does to the price floor

Frontier pricing has rested on a straightforward bargain. The best coding model costs the most, and the gap is what you pay for the top of the leaderboard. K3 charges 30% and took first place, from a lab working under export controls on the hardware it trained with.

DeepSeek V4-Flash sits at $0.14 and $0.28 per million, with V4-Pro at $0.435 and $0.87. The floor under everyone's inference bill is being set by open-weight releases now, rather than by the labs that publish rate cards.

None of which retires Fable 5 or Opus 5. A leaderboard position says nothing about how a model behaves on hour three of an agent loop, and that is where the money actually goes. What has changed is that the premium has to be argued for.

Which lands where the pricing hub keeps landing: cost per finished task, not cost per million tokens. A model that needs four attempts at $18 has already cost you more than one that got there first at $60.

FAQ

How big is Kimi K3 really?

2.8 trillion parameters stored, with only a fraction active on any given token, which is what a sparse mixture-of-experts design buys you. The total is why the download runs to 1.4 TB. The active slice is why the API costs $3.

Should I switch from Claude to Kimi K3?

Not on the strength of one leaderboard. The arena result is real and it covers frontend coding; moving a production agent is a decision about failure modes across long sessions, which no ranking measures. Run your own evals on your own tasks. A price gap this wide justifies the afternoon.