Kimi K3's license got stricter the week open weight went political

Twenty-five companies signed Jensen Huang’s letter, “Open Weights and American AI Leadership,” on the day he published it, July 24. The count doubled to fifty within twenty-four hours and kept growing for weeks. The letter’s ask is narrow: don’t let regulators restrict downloadable model weights on the theory that open models are inherently less safe than closed ones, because “concentrating advanced AI capabilities behind a small number of closed models compounds that risk” rather than reducing it.

It’s a reasonable argument, and it arrived at a plausible moment. The gap between open-weight and closed-frontier models really has narrowed to the point of argument rather than obvious fact. Moonshot AI’s Kimi K3, a 2.8-trillion-parameter model whose full weights went public on July 27, sits close to Claude Opus 4.8 on independent benchmarks and beats it outright on some coding tests. If you wanted one model to stand as evidence for the letter’s premise, K3 is the obvious pick. The letter doesn’t name it — it doesn’t name any model — but the timing does the naming for it.

Three days after that letter, K3’s weights went public — and the license shipped in the same commit, stricter than the one Moonshot had used for K2. K2’s license was Modified MIT — the standard MIT text plus one clause requiring you to display “Kimi K2” in your product’s UI if you cross 100 million monthly active users or $20 million in monthly revenue. Otherwise, do anything you want. K3 keeps that clause. It adds a new one: if you run a “Model as a Service” business and your revenue crosses $20 million over any trailing 12 months, you need a separate commercial agreement with Moonshot to keep using it. A “Model as a Service” business is defined as giving third parties API access to inference or fine-tuning. Internal use is exempt. Going through Moonshot’s own certified partners is exempt. Reselling raw model access at scale is exactly what got gated.

Compare that to Meta’s approach: anyone whose product crosses 700 million monthly active users needs Meta’s sign-off, full stop, regardless of what the product does. That threshold is built to catch three or four companies on Earth. Moonshot’s threshold catches a mid-sized Series B inference-hosting startup. The dollar figure is lower, but the scope is narrower: it only trips for reselling access to the model, not for shipping a popular app built on it. That’s a more precise instrument than Meta’s. Not necessarily a harsher one. It’s also evidence that “open weight” spans a spectrum, not one license, philosophy, or bet about what deserves protection. DeepSeek sits at one end with its actual unmodified MIT license, Llama in the middle with its blanket hyperscaler carve-out, and Moonshot furthest along with a newly narrower, newly commercial carve-out.

The letter treats “open weight” as a single policy category worth defending as a unit. The licenses underneath it disagree about what commercial activity is safe to leave unrestricted, and that disagreement is getting more specific as the models get more valuable. That’s the part the coalition letter can’t really speak to, because a policy letter has to generalize and a license has to specify. Fair enough — but it means the letter’s implicit evidence (K3 closing the gap) and K3’s actual legal terms (a new commercial wall that didn’t exist in the prior release) are making two different arguments in the same week. Only one of them is the one builders have to read before they ship.

As open-weight capability keeps closing on the closed frontier, the license text becomes the place labs compete on whatever leverage they have left. Expect fewer blanket user-count walls like Meta’s, which mostly gate nobody, and more surgical, business-model-specific gates like Moonshot’s, which gate exactly the resale layer that would otherwise compete with a lab’s own paid API. “Open” will keep meaning something different in a policy letter than it means in a LICENSE file, and the gap between those two meanings is going to matter more than the gap between open and closed model capability ever did.