The Kimi K3 license guards Moonshot's own API price floor, not rent from clouds — resolves 2026-11-05
The Kimi K3 license guards Moonshot's own API price floor, not rent from clouds — resolves 2026-11-05
Scheduled check: 2026-11-05
Background
The debate: Moonshot released Kimi K3's weights, but its license requires any company running a model-as-a-service business with more than $20 million in combined affiliate revenue over 12 months to sign a separate agreement with Moonshot before commercial use, and the question is whether that threshold is a toll on cloud providers or serves another purpose.
Why it matters: third-party clouds got the weights for free yet did not undercut Moonshot's official API, with 8 of the 12 provider endpoints we read in early August matching the official price to the cent, so the expectation that open-weight inference gets competed down to cost needs rechecking.
Who is on each side: the rent reading expects Moonshot to collect sizeable license fees from cloud providers; our 2026-08-07 deep dive found that what the threshold can be shown to do is protect Moonshot's own API price floor and keep control of a channel whitelist.
The call
Our call: what the Kimi K3 license threshold can be shown to do is protect the price floor of Moonshot's own API and keep control of a channel whitelist, not collect rent from cloud providers. The 2010s base rate from the open-source licensing wars: cloud providers never paid license fees, and such licensing walls had a half-life of 13.5 to 43 months. The claim that value shifts to the US should be split into two layers: the layer that rents out compute is unchanged, while the layer that sells model access by usage has opened a channel back to Moonshot, small in size and with the fee rate entirely undisclosed.
Sources behind the call
X / @kevinsxu (Kevin Xu, author of the Interconnected newsletter and analyst of US-China tech policy)
“This pricing being *not* cheaper than Kimi's…”
The receipt
On 2026-11-05, check the provider price table on the Kimi K3 model page at OpenRouter, and only that page. If no third-party (non-Moonshot) provider's blended price is 12% or more below Moonshot's first-party price, the call is right and the floor held; if at least one is 12% or more below, it missed. If K3 is delisted from OpenRouter before then, or the page no longer lists Moonshot's first-party price, there is no baseline and the call is void. Logged but not scored: any disclosure of license fees, whether export controls on model weights take effect, and whether a lab releases a comparable model under a permissive license.
What would overturn it
(1) Third-party K3 prices tiering down by 12% or more by the due date: the reading that the license holds up a price floor weakens, and the explanation that a new model's price is simply anchored to the official rate wins. (2) Any party publicly disclosing a sizeable license fee paid to Moonshot, for example as a separate revenue line in a prospectus: the rent-collection reading wins.