Moonshot AI is reportedly negotiating up to 30% of Kimi K3 revenue with three US cloud giants, signaling a push to expand the model abroad.

Moonshot AI is reportedly seeking as much as a 30% share of revenue generated through three US cloud giants as it prepares to distribute its Kimi K3 model in the American cloud market. The reported arrangement would give the Chinese AI company a potentially significant role in the economics of overseas access to its model, while leaving the cloud providers responsible for distribution and customer access.
The claim appears in two separate wire reports carried by finance.biggo.com and Pandaily. Their headlines describe the same development, but the supplied reporting does not identify the three cloud companies, disclose the proposed commercial terms beyond the upper limit of 30%, or confirm that an agreement has been signed. The evidence therefore points to reported negotiations or a commercial request, not a completed partnership.
If finalized, the arrangement could place Kimi K3 inside established US cloud channels rather than requiring customers to work directly with Moonshot AI. That route would matter to developers and enterprises that already buy model access, compute, security controls, and usage management from major cloud platforms.
For Moonshot AI, cloud distribution could provide a faster way to reach international developers. It could also shift part of the operational burden—such as serving workloads, handling billing, and integrating with existing enterprise systems—to platform partners. The trade-off would be sharing revenue and accepting the commercial, technical, and policy constraints imposed by those platforms.
The reported ceiling of 30% is especially notable because it suggests Moonshot AI may be seeking economics materially different from a simple model-hosting arrangement. However, the available evidence does not explain whether the figure refers to gross revenue, net revenue after infrastructure costs, selected usage tiers, or a particular period. Those distinctions would determine how valuable the proposal is to either side.
Pandaily’s headline frames the development as Kimi K3 “eyes US clouds,” while finance.biggo.com describes Moonshot AI as seeking revenue share from three US cloud giants. Neither supplied source provides technical specifications for Kimi K3, a release timetable, an application programming interface, pricing, or details about the model’s availability outside China.
That missing information limits what can be concluded about the product strategy. Kimi K3 could be offered as a hosted inference service, made available through a cloud marketplace, integrated into an existing model catalog, or distributed through more than one of those routes. Each approach would create different requirements for latency, data handling, regional availability, and customer support.
For AI builders, the key question is not only whether Kimi K3 reaches a US platform. It is whether developers can use it with familiar deployment tools and predictable commercial terms. Model access through a major cloud can reduce integration work, but it does not automatically resolve questions about data residency, content policies, uptime commitments, or compatibility with existing evaluation and monitoring systems.
The strongest confirmed fact in the supplied material is that two wire stories independently describe Moonshot AI seeking up to 30% revenue share involving three US cloud giants and Kimi K3. The source extracts contain no full article text, named executive comments, contract documents, direct company statements, benchmark results, or confirmation from any cloud provider.
That means the revenue figure should be treated as a reported negotiating position or commercial target, rather than a verified market standard or completed financial arrangement. It is also not possible from the evidence to determine whether all three cloud providers are in active negotiations, whether the same terms were proposed to each, or whether any provider has accepted them.
There are no performance or adoption claims in the supplied sources to validate. Any assessment of Kimi K3’s quality, demand, or competitiveness would require separate evidence, such as published evaluations, customer deployments, usage data, or an official product announcement from Moonshot AI.
The story highlights a growing tension in model distribution. Model developers need access to customers and infrastructure, while cloud providers control much of the enterprise buying relationship. Revenue sharing can make a model more attractive to a platform if it supports differentiated demand, but a high share may also reduce the model developer’s margin after computing, support, compliance, and research costs.
For enterprise buyers, the proposed structure could influence pricing and vendor selection if Kimi K3 becomes available through familiar US cloud providers. Buyers would still need to compare the total cost of inference, not just the headline model price. They would also need clarity on whether workloads are processed in the United States, how prompts and outputs are retained, and which party is accountable for service failures or policy disputes.
The arrangement would also test how easily a Chinese model developer can expand through US cloud infrastructure. Access to cloud marketplaces is not the same as unrestricted availability. Export controls, platform review processes, cybersecurity requirements, and each provider’s policies could affect where and how Kimi K3 is offered. The supplied reports do not say whether any such review has occurred.
The first signal will be an official announcement from Moonshot AI or one of the three unnamed US cloud providers. Such a statement could clarify whether the discussions produced a deal, identify the platforms involved, and explain whether Kimi K3 will be offered through an API, marketplace listing, managed service, or another format.
Developers should also watch for a Kimi K3 model card, documentation, pricing page, and regional availability details. Those materials would help establish the model’s context limits, supported capabilities, safety controls, and operational requirements.
Commercial follow-up will be equally important. A published revenue-share structure, customer pricing, service-level commitments, and data-processing terms would show whether the reported 30% figure is a broad platform arrangement or a narrow negotiating proposal. Independent testing and early customer evidence would be needed before drawing conclusions about the model’s performance or adoption.
The reported negotiations matter less for the headline percentage than for the distribution question they expose. Moonshot AI appears to be exploring whether Kimi K3 can use US cloud providers as a bridge to international customers, but the available evidence does not yet show a signed agreement or a launch plan.
For builders and enterprise teams, the prudent response is to monitor access, pricing, governance, and independent evaluations rather than assume availability or performance. If a deal is confirmed, its structure will offer an early indication of how major clouds are balancing model choice, infrastructure economics, and geopolitical risk.