Baseten adds day-0 API support for Moonshot AI’s Kimi K3

Baseten said it launched day-0 API access for Moonshot AI’s 2.8T-parameter Kimi K3, using NVIDIA GB300 NVL72 to run frontier-scale inference.

Edward Mullen ·

Baseten adds day-0 API support for Moonshot AI’s Kimi K3

Baseten said it has added day-0 support for Moonshot AI’s Kimi K3 to its Model APIs, offering customers access to what it described as a frontier-scale model through an API rather than a bespoke deployment. The company outlined the work in a post published this morning.

According to Baseten, Kimi K3 is an open model with 2.8T parameters, and bringing it online required substantial engineering to manage the system-level demands of running inference at that scale. Baseten said the deployment used NVIDIA GB300 NVL72 systems.

Baseten frames Kimi K3 launch as an inference

Baseten frames Kimi K3 launch as an inference economics shift In its description, Baseten positioned the release as evidence that frontier-model access does not always require organizations to build and operate their own specialized infrastructure. The company argued that an API-first approach can move the burden of hardware procurement, data pipelines, and reliability engineering into a shared service layer. Baseten’s post emphasized a change in how costs are carried, describing a path that shifts spending away from one-time, capital-intensive builds and toward recurring operating expense tied to usage. The company also framed the technical constraint as one of controlling scale at the API boundary rather than inside a private data center. Enterprise trade-offs highlighted: cost, governance, and workload shape For enterprise buyers, the company’s stated implication was direct: organizations may be able to use frontier-scale models without building and maintaining bespoke infrastructure from scratch. Baseten also acknowledged that the practical economics depend on how a customer consumes the service and on the terms attached to pricing, throughput, and uptime commitments. Baseten’s post described a set of scenarios in Baseten’s post described a set of scenarios in which outcomes can differ. It said predictable, steady workloads could benefit from removing procurement cycles and the overhead of maintaining specialized systems, while spiky demand, frequent fine-tuning needs, or strict security controls could push operating costs higher than internal capital cycles would.

Uncertainties: competitive pressure and reliance on a service layer

The company noted that API access can concentrate risk in the contract with a provider, including dependence on a vendor, sensitivity to pricing as model behavior changes, and governance or compliance friction. It added that standardized evaluations, governance templates, and shared compliance controls could reduce some of those risks over time, while still tying overall economics to consumption growth and support costs.

Baseten described its day-0 Kimi K3 support as a live data point, but the longer-term picture remains uncertain, including whether API margins compress as more providers enter the market. It said the next six to twelve months could bring clearer signals, including announcements from major cloud vendors on direct frontier-model access with enterprise guarantees, disclosures by Baseten or Moonshot AI on pricing or onboarding throughput, and statements by frontier developers on preferred deployment partners and governance commitments.

This report is based on a single published account from Baseten, and no independent confirmations were cited in the source material.

More stories