Moonshot AI Review (2026): Features, Pricing & Verdict
Moonshot AI is the model provider that decided agents shouldn’t work alone. While the rest of this category raced to make one model smarter, the Beijing lab behind the Kimi brand bet on making a hundred models cooperate — and in 2026, that bet is its identity. The K2 family runs on a trillion-parameter Mixture-of-Experts skeleton (only 32 billion parameters active per token, so it prices like a mid-size model), and its signature trick is Agent Swarm: K2.5 (January 2026) introduced an orchestrator trained with Moonshot’s Parallel-Agent Reinforcement Learning to decompose a task across up to 100 simultaneous sub-agents — lifting wide-research benchmarks like BrowseComp from 60.6% to 78.4% and cutting execution time 4.5x — and K2.6 (April 2026) scaled the ceiling to hundreds of parallel sub-agents while adding native multimodality and stronger long-horizon coding. K2 Thinking sustains up to 300 sequential tool calls in a single run. The prices read like the rest of the Chinese cohort: about $0.60 per million input tokens and $2.50 output on the official API — roughly 8–10x below Claude Opus-class rates — with cache hits at $0.15, and the weights ship under a modified MIT licence, so 20+ third-party providers serve K2.6 on Western infrastructure and self-hosting is fully legal. Around the API sits a genuinely ambitious product stack: the Kimi Code CLI (an open-source Claude Code counterpart, 6,400+ GitHub stars), tiered memberships from $19 to $199/month with swarm credits, and hosted tools including web search and memory. The honest counterweights: raw single-shot capability trails the Western frontier (independent readers place K2.6 below current Sonnet/Opus on the hardest reasoning), some vendor benchmarks depend on contested harnesses, the enterprise machinery is young, and the China-residency question applies here as everywhere in this cohort. This review covers the developer platform; the Kimi consumer app is reviewed separately at 0014.
- Best for
- Teams building multi-agent and long-horizon systems — parallel research, autonomous coding runs, document-heavy workflows — where swarm orchestration and 300-step tool calling matter more than winning single-shot reasoning benchmarks; plus cost-driven coding via Kimi Code
- Platform
- Kimi API Platform (platform.moonshot.ai): OpenAI-compatible endpoints for K2.5 (multimodal, thinking/non-thinking), K2.6 (flagship — coding, UI generation, agent swarms) and K2.7 Code; hosted web-search and memory tools; Kimi Code CLI; weights on Hugging Face under a modified MIT licence, served by 20+ providers
- Key differentiator
- Agent Swarm — Parallel-Agent RL trains the model to spawn and coordinate up to hundreds of concurrent sub-agents (BrowseComp 78.4% vs 60.6% single-agent), plus K2 Thinking’s 300-step sequential tool calling for expert-level research runs
- Pricing
- ~$0.60 input / $2.50 output per 1M tokens official (cache hits ~$0.15); OpenRouter market average ~$0.66/$3.41 across 21 providers; Kimi memberships $19–$199/month; Kimi Code CLI open source (Apache 2.0)
- Vendor
- Moonshot AI (Beijing, founded 2023 by Yang Zhilin) — the lab that turned long context into an agent empire; K2 backs Genspark, Tencent CodeBuddy, XtalPi and other production agent platforms
What Is Moonshot AI?
Moonshot AI is the Beijing lab founded in 2023 by Yang Zhilin — one of China’s most-cited young NLP researchers — and the company behind the Kimi brand: a consumer assistant that made its name on extreme long context (reviewed at 0014) and, more relevantly here, a developer platform that has evolved into the most agent-centric offering in this entire category. The pivotal chapter came in late 2025: K2, a trillion-parameter Mixture-of-Experts model with 32 billion active parameters per token, trained on 15.5 trillion tokens with the lab’s MuonClip optimizer — a genuine research contribution that scaled the Muon optimizer to unprecedented size with zero training instability, and the reason a 2023-vintage startup could train at the trillion-parameter tier at all. K2’s design brief was agents from the start: heavy simulated tool-use training across hundreds of domains (real APIs, shells, databases, plus synthetic tools), and a K2 Thinking variant capable of sustaining up to 300 sequential tool calls in one run — the foundation for the expert-research positioning that partners like AlphaEngine (a FinGPT agent doing 300-call financial analysis) and XtalPi (chemical-literature extraction, top-2 on RxnBench benchmarks) built on. Then came the swarm era. K2.5 (January 2026) added native multimodality — vision and text trained together from the start rather than bolted on — thinking and non-thinking modes, and Agent Swarm: an orchestration capability trained via Parallel-Agent Reinforcement Learning, whose reward design first forces the orchestrator to actually parallelise (preventing “serial collapse” into single-agent behaviour), then optimises an 80/20 blend of task quality and critical-path efficiency. The results are the platform’s calling card: on wide information-gathering tasks, swarm mode lifted BrowseComp from 60.6% to 78.4% and cut execution time 4.5x, with Moonshot claiming 50.2% on Humanity’s Last Exam at 76% lower cost than Opus-class pricing. K2.6 (20 April 2026) is the current flagship — the same 1T/32B MoE skeleton with 384 experts per layer, Multi-head Latent Attention compressing the KV cache, native INT4 quantisation, a 262K context window, sub-agent ceilings raised into the hundreds, and a specialisation in long-horizon coding and coding-driven UI generation (one documented run: a 13-hour autonomous session overhauling a 4,000-line financial engine across 1,000+ tool calls). K2.7 Code (July 2026) tops the coding line. Distribution is refreshingly open: the weights ship under a modified MIT licence on Hugging Face (self-hostable via vLLM, SGLang, KTransformers or TensorRT-LLM), OpenRouter routes across 21 providers, and the official OpenAI-compatible API charges about $0.60/$2.50 per million tokens with 75%-off cache hits. Within our Model Providers & AI Infrastructure category, Moonshot is the specialist among generalists: not the broadest catalogue (Qwen), not the price floor (DeepSeek), but the provider that has thought hardest about what happens when one model becomes many.
Core Features
Agent Swarm and 300-step tool calling: the orchestration edge
Moonshot’s differentiator is architectural rather than incremental: it trains its models to be managers, not just workers. The mechanism deserves explanation because it’s genuinely novel among API providers. Standard agents execute serially — plan, act, observe, repeat — which means wall-clock time and error compounding grow with task size. Agent Swarm inverts this: the K2.5/K2.6 orchestrator decomposes a task, spawns specialised sub-agents (up to 100 on K2.5, into the hundreds on K2.6), runs them concurrently, and integrates the results — and critically, this behaviour is trained, not prompted. Moonshot’s Parallel-Agent Reinforcement Learning rewards sub-agent instantiation and concurrency early in training (explicitly preventing “serial collapse,” where an orchestrator lazily reverts to doing everything itself), then shifts to a final reward blending completion quality (80%) with critical-path efficiency (20%) — measured on the slowest dependency chain, exactly like project-management critical-path analysis — so the model learns to parallelise only where it actually helps rather than shredding tasks for show. The measured payoff on wide tasks is substantial: BrowseComp jumps from 60.6% (single agent) to 78.4% (swarm), Wide Search from 72.7% to 79.0%, execution time drops 4.5x, and the product expression — one prompt returning finished documents, websites or spreadsheets without supervision — is what Kimi’s higher membership tiers sell as a headline feature. Alongside the swarm sits the depth dimension: K2 Thinking sustains up to 300 sequential tool calls in a single coherent run, which is what the platform’s flagship enterprise deployments actually use — AlphaEngine’s financial-research agent chews through research reports and macro data across 300+ calls; the legal/IP positioning (contract review, patent analysis) leans on the same long-horizon discipline plus the line’s noted terminological rigour. Hosted platform tools — web search with citations and a memory store for persistent user data — round out the agent toolkit, a small but real advantage over DeepSeek’s tools-free API. The honest boundaries: swarms multiply cost (every sub-agent bills its own tokens — the cheap per-token rate is what makes the architecture affordable, not free); swarm gains concentrate on wide tasks (research, multi-file generation) rather than deep single-thread reasoning, where parallelism can’t help; and orchestration quality is bounded by the underlying model — K2.6 coordinating a hundred K2.6s is powerful, but each worker still carries the capability profile described below. For teams whose workloads are genuinely parallel — market research, codebase-wide changes, batch document analysis — no other provider in this category ships this as a first-class, RL-trained capability.
K2.6, Kimi Code and the coding economics
Moonshot’s second front is coding, where its pitch is the sharpest cost arbitrage in the category — and where the honest capability picture matters most. The architecture is the pricing argument in one sentence: K2.6 keeps 1 trillion parameters of capacity but activates only 32 billion per token (384 experts per layer, 8 routed plus 1 shared, Multi-head Latent Attention to shrink the KV cache, native INT4 quantisation), so inference costs like a 32B model while knowledge scales like a 1T one — which is how the official API lands at $0.60/$2.50 per million tokens, roughly 8.3x cheaper on input and 10x on output than Opus-class rates, with cache hits at $0.15 dropping repeated agent-loop context by 75%. The product stack converts that into a developer experience: Kimi Code, launched January 2026 under Apache 2.0, is a deliberate open-source counterpart to Claude Code — same terminal interaction model, Model Context Protocol support, 6,400+ GitHub stars — defaulting to K2.6 (and now K2.7 Code, July 2026’s release, Moonshot’s strongest coding model with a simultaneous high-speed variant) with flat-rate membership credits from $19/month, versus $100–200 for the closed alternatives. The capability evidence is a study in reading both columns. For it: K2.6 handles genuinely long-horizon work — the documented 13-hour autonomous session that overhauled an 8-year-old, 4,000-line financial engine across 12 strategies and 1,000+ tool calls (+185% throughput) is the kind of run few models sustain — and its coding-driven UI generation (prompt-to-polished-interface with scroll animations, auth and database operations) is a distinctive strength; practitioner consensus lands around “80–90% of Claude Code’s quality at about 12% of the cost” for the standard 80% of tasks: generation, unit tests, refactors, prototyping. Against it: independent readers place K2.6 below current Sonnet/Opus tiers on raw capability; the K2.5→K2.6 gain was modest; domain-specific tasks are a noted weak spot; and some launch comparisons rest on contested harnesses (Moonshot’s Terminal-Bench figures measured GPT-5.4 with a harness scoring it ~10 points below other evaluations — leaderboard positions move a lot depending on whose harness you trust). On single-shot high-stakes reasoning the gap is explicit: K2.6 trails top Western models on GPQA-Diamond (90.5 vs 92.8) and AIME (96.4 vs 99.2) — small numbers, but exactly where wrong answers are expensive. The resulting playbook writes itself and mirrors what the Kimi Code community actually does: run the bulk of coding volume on K2.6/K2.7 at an eighth of the cost, keep a frontier model in the loop for architecture decisions and the hardest debugging, and let the 75% cache discount make the long agent sessions — Moonshot’s true home turf — cheap enough to leave running overnight.
Open weights, distribution and the trust picture
Moonshot handles the questions every Chinese provider faces — licensing, portability, residency — with a posture closer to DeepSeek’s radical openness than Qwen’s open-except-the-best hedging, and that shapes the trust calculus. The weights: K2-family models ship on Hugging Face under a modified MIT licence — permissive commercial use, modification and redistribution, with light attribution-style conditions added to base MIT (read the delta, but it’s nowhere near Llama’s MAU gates or acceptable-use novelties) — and crucially, Moonshot opens its flagship: K2.6, the best model it has, is the open model, matching DeepSeek’s philosophy and inverting Qwen’s. Self-hosting is first-class, with official support across vLLM, SGLang, KTransformers and TensorRT-LLM, and native INT4 quantisation baked in at training time rather than bolted on — a trillion-parameter model that deploys more gracefully than its size suggests. Distribution follows: OpenRouter routes K2.6 across 21 providers (market-average pricing ~$0.66/$3.41, with effective rates 60–80% lower after prompt caching on repeated context), DeepInfra, Fireworks, Parasail, Clarifai and SiliconFlow serve it on Western infrastructure with blended prices from $1.15–2.15 per million tokens, and provider choice meaningfully changes throughput and latency — for production, K2.6 is a routing decision, not just a model decision. That third-party depth is also the residency answer: the first-party API is a Chinese platform (Beijing-based company, with the same jurisdictional considerations that apply to DeepSeek’s endpoint — organisations that bar Chinese-parent hosted platforms will bar this one), but the modified-MIT weights on US/EU hosts or your own GPUs remove Moonshot from the data path entirely, and for privacy-focused teams that is the recommended architecture. The production credibility is real but young: Genspark runs its agent platform on K2, Tencent CodeBuddy embeds K2 Thinking, XtalPi and DP Technology deploy K2.5 in scientific R&D — serious names, concentrated in China’s ecosystem — while the Western-enterprise machinery (compliance artefacts, support tiers, contractual maturity) visibly trails OpenAI, Anthropic and even Mistral; reviewers consistently flag the younger ecosystem, the Chinese-first interface heritage and less-established enterprise support as the trade for the price. Operationally, apply this category’s standard hygiene with extra emphasis on cadence: three model releases in six months, limited-time launch promotions (K2.7 Code shipped with one), membership tiers that have already been renamed and repriced, and vendor benchmarks that need independent confirmation. The one-line trust summary: the models are as portable as any in this review — flagship-tier open weights, 20+ hosts, self-hosting that actually works — so the risk you’re pricing is the hosted platform and the company’s youth, not lock-in.
Scored Categories
Pricing
| Model / item | Price (per 1M tokens) | Notes |
|---|---|---|
| Kimi K2.6 (flagship, open weights) | ~$0.60 input / $2.50 output | Official API; cache hits ~$0.15 (75% off). 1T MoE, 32B active, 262K context, multimodal, agent swarms. ~8–10x under Opus-class rates |
| Kimi K2.5 | ~$0.60 / $2.50 | Multimodal (vision + text), thinking/non-thinking modes, Agent Swarm up to 100 sub-agents |
| Kimi K2.7 Code | Promotional at launch | Strongest coding model (July 2026) with a simultaneous high-speed variant — ⚠ limited-time promo pricing; budget at standard rates |
| Third-party hosting | ~$0.66/$3.41 avg (OpenRouter, 21 providers); blended $1.15–2.15 | DeepInfra, Fireworks, Parasail, SiliconFlow and others on Western infrastructure; effective cost 60–80% lower with caching on repeated context |
| Kimi memberships | $19 / $39 / $99 / $199 per month | Moderato → Vivace: chat + agent credits, Deep Research, Kimi Code credits, Slides/Websites tools; top tiers unlock swarms up to 300 sub-agents and cloud deployment. China plans priced separately in RMB |
| Kimi Code CLI | Free, open source (Apache 2.0) | Claude Code-style terminal agent, MCP support, 6,400+ GitHub stars; runs on membership credits or API billing |
| Self-hosting | Free (modified MIT weights) | Official support for vLLM, SGLang, KTransformers, TensorRT-LLM; native INT4 quantisation |
| Higher volume | Tiered rate limits; custom above Tier 5 | Contact Moonshot sales for negotiated limits |
Strengths
- Agent Swarm — the only RL-trained parallel-orchestration capability in the category (BrowseComp 78.4% vs 60.6% single-agent, 4.5x faster)
- K2 Thinking’s 300-step tool calling — genuine long-horizon research and analysis runs
- Flagship-tier open weights under a modified MIT licence — Moonshot opens its best model
- ~$0.60/$2.50 pricing with 75%-off cache hits — roughly a tenth of Opus-class cost
- Kimi Code: open-source Claude Code counterpart (Apache 2.0, MCP support) at a fraction of closed-CLI pricing
- Documented long-horizon coding — 13-hour autonomous sessions across 1,000+ tool calls
- Native multimodality from K2.5 — vision and text trained together, not grafted
- Broad distribution — 21 providers on OpenRouter, Western hosting, first-class self-hosting with native INT4
- Real production deployments — Genspark, Tencent CodeBuddy, XtalPi, AlphaEngine
- Hosted web-search and memory tools — more agent tooling than DeepSeek’s bare API
Weaknesses
- Single-shot capability trails the Western frontier — below current Sonnet/Opus tiers on the hardest reasoning (GPQA-D 90.5 vs 92.8; AIME 96.4 vs 99.2)
- Some vendor benchmarks rest on contested harnesses — independent numbers run lower
- Swarms multiply token consumption — parallelism is bought, not free
- 262K context trails the 1M windows of DeepSeek and Qwen
- Young enterprise machinery — support, compliance artefacts and Western go-to-market trail the majors
- First-party API carries the standard Chinese-platform residency question
- Rapid cadence and promo pricing — three models in six months; launch discounts expire
- Domain-specific tasks flagged as a weak spot by practitioners
Verdict: 8.0 / 10 — The Agent-Swarm Specialist
Moonshot AI earns a solid 8.0 as the provider with the clearest thesis in this category: the future of AI work is many agents, coordinated well, at prices that make the coordination affordable. On that thesis it delivers something nobody else here ships — Agent Swarm’s RL-trained parallel orchestration is a real, measured capability (not a prompting pattern), K2 Thinking’s 300-step runs anchor genuine expert-level research deployments, and the economics close the loop: a trillion parameters of capacity billed like a 32B model, $0.60/$2.50 with 75%-off caching, flagship weights under a modified MIT licence, and a 21-provider distribution market that makes residency a routing choice. Kimi Code extends the same logic to developers — 80–90% of the closed-CLI experience at roughly 12% of the cost is a trade most teams should at least trial. What holds it at 8.0 — three tenths under the DeepSeek/Qwen/Llama trio — is the sum of honest gaps: raw single-shot capability sits visibly below the Western frontier and slightly below DeepSeek’s V4 Pro on the hardest reasoning, exactly where errors cost most; the 262K context trails its Chinese peers’ million-token windows; several headline benchmarks need the harness caveat; and the enterprise story — compliance depth, support maturity, Western references — is the youngest of any major provider reviewed in this run. The buying logic: if your workload is wide — parallel research, batch analysis, codebase-scale changes, long autonomous runs — Moonshot is arguably the best-adapted platform in the market and should be trialled on your real tasks this quarter, first-party or via a Western host as your compliance posture dictates. If your workload is deep single-shot reasoning with expensive failure modes, route that slice to a frontier model and let K2 handle the volume around it. Either way, watch this lab: three meaningful releases in six months, a genuine research contribution in its training stack, and a differentiator the giants are now copying. Specialists who pick the right specialty tend to stop being specialists — and swarms look increasingly like the right one.
Frequently Asked Questions
What is Agent Swarm, and when does it actually help?
Agent Swarm is Moonshot’s trained capability for one model instance to act as an orchestrator — decomposing a task, spawning up to hundreds of specialised sub-agent instances, running them concurrently, and integrating the results — and the crucial word is trained: this isn’t a prompting framework bolted on top (the LangChain/CrewAI pattern anyone can build), it’s behaviour instilled through Moonshot’s Parallel-Agent Reinforcement Learning. The training design explains both the strength and the limits. Early in training the reward explicitly incentivises spawning sub-agents and running them concurrently, to prevent “serial collapse” — the natural failure mode where an orchestrator just does everything itself. Later training rebalances toward output quality, with a final reward of 80% task completion quality and 20% critical-path efficiency, measured on the slowest sub-agent chain at each stage (classic critical-path analysis: total runtime is your longest dependency chain, not your total work). That last detail matters: it teaches the model to parallelise only where the task graph genuinely allows it, rather than shredding work into artificial fragments for reward points. Where it helps, measurably: wide tasks — those whose subtasks are independent enough to run simultaneously. On BrowseComp (wide web research) swarm mode scores 78.4% versus 60.6% for the same model running as a single agent; on Wide Search, 79.0% versus 72.7%; execution time drops about 4.5x because ten minutes of parallel browsing replaces forty of sequential. Product-wise this is what powers Kimi’s one-prompt-to-finished-deliverable features (documents, websites, spreadsheets in a single unsupervised run) and enterprise patterns like sweeping market research, batch document review, and repository-wide code changes where files can be touched independently. Where it doesn’t help: deep tasks. A hard proof, a subtle debugging chase, a single chain of reasoning — these have one long dependency chain by nature, parallelism has nothing to grab, and a swarm of K2.6s won’t out-think one stronger model; this is exactly where the Western frontier’s single-shot edge (and even DeepSeek V4 Pro’s) still tells. And two costs to price in: token multiplication — every sub-agent bills its own input and output, so a 100-agent run consumes on the order of 100 single-agent runs’ tokens (the cheap per-token rate is what makes this viable at all — compare end-to-end task cost, not rate cards); and orchestration overhead on small tasks, where spinning up a swarm for something one agent finishes in three steps is pure waste. The practical rule: profile your workload’s task graph. Genuinely parallel structure → swarm mode is Moonshot’s unique, measured advantage. Serial structure → run K2 as a normal single agent (it’s a good one, with 300-step endurance) or route to a stronger single-shot model. Mixed → the common production pattern: swarm for the gathering phase, single strong agent for the synthesis.
Kimi Code vs Claude Code — is the 88% saving real?
The saving is real; whether it’s free depends on your task mix — the honest practitioner consensus is “80–90% of the quality at roughly 12% of the cost,” and everything in the decision lives inside those two ranges. What Kimi Code is: an open-source (Apache 2.0) terminal coding agent launched January 2026, deliberately modelled on Claude Code’s interaction pattern — same agentic loop, Model Context Protocol support for the existing tool ecosystem, 6,400+ GitHub stars — defaulting to K2.6 and now K2.7 Code as its backend, billed either through Kimi membership credits (from $19/month, versus $100–200 for the closed heavy-usage tiers) or per-token API rates ($0.60/$2.50, cache hits $0.15). Because both CLI and weights are open, you can also point it at other models, or run K2 locally underneath it for a fully self-hosted stack — options the closed alternative structurally can’t offer. Where the arbitrage holds: the standard ~80% of coding work — code generation from clear specs, unit tests, refactors within defined boundaries, UI prototyping (a genuine K2.6 specialty: prompt-to-production-interface with animations, auth layers and database operations), and long unattended runs, where the documented 13-hour, 1,000-plus-tool-call session overhauling a 4,000-line financial engine shows the endurance is real and the caching makes it cheap. On this slice, paying 8x more for the closed stack buys you little. Where it breaks down: the hardest 20% — architectural decisions, subtle multi-system debugging, domain-heavy code (a flagged K2 weak spot), and anything where a wrong answer is expensive, because independent readers place K2.6 below current Sonnet/Opus capability and the deficit concentrates exactly at that difficulty ceiling; expect more re-prompting there, which erodes both the time saving and some of the cost saving. Also read benchmarks skeptically in both directions: some of Moonshot’s launch comparisons used harnesses that scored the competition ~10 points below other evaluations, so trust your own task suite over anyone’s leaderboard. The playbook that’s emerged in the community, and that we’d endorse: adopt Kimi Code for volume work — it’s a two-day trial to find out if your codebase sits in the friendly 80% — keep a frontier model available for the escalation slice (the OpenAI-compatible API makes dual-wielding trivial), lean on cache-friendly prompt structure to hit the $0.15 rate on long sessions, and re-evaluate quarterly: K2.5→K2.6→K2.7 landed in six months, and the quality range in that “80–90%” keeps drifting upward while the 12% cost figure hasn’t moved.
How does Moonshot compare to DeepSeek and Qwen — and can Western enterprises use it?
Moonshot is the specialist of China’s big three API providers: it can’t match Qwen’s breadth or DeepSeek’s price floor, but neither rival ships its agent orchestration — and the enterprise answer follows the same three-route pattern as its peers, with a younger company attached. Against DeepSeek: DeepSeek is cheaper at the floor (V4 Flash’s $0.14/$0.28 undercuts everything here) and slightly stronger on the hardest single-shot reasoning and coding benchmarks (V4 Pro’s ~80.6 SWE-bench Verified and 1M flat-rate context versus K2.6’s 262K window), with brutally simple billing. Moonshot answers with capabilities DeepSeek simply lacks: native multimodality (DeepSeek is text-only), hosted tools (web search, memory — DeepSeek ships none), and above all the trained swarm/300-step orchestration layer. Both open their flagship weights permissively (MIT vs modified MIT — near-equivalent in practice). Rule of thumb: DeepSeek for cheap text volume and hard single-thread work; Moonshot when the workload is agentic, wide, or needs eyes. Against Qwen: Qwen is the everything store — 145+ hosted models, every modality, the deepest open shelf, Singapore residency on its international endpoint — but its best model stays closed and its billing is the category’s most complex. Moonshot is one model line, done deeply: flagship weights open, agent-first training, simpler rates. Teams standardising on one Chinese provider for breadth pick Qwen; teams building multi-agent products pick Moonshot; plenty use both through a router, which the OpenAI-compatible endpoints make trivial. On Western enterprise use, apply the cohort’s standard three-route analysis with Moonshot-specific adjustments. Route one, the first-party API: Moonshot is a Beijing company, and organisations whose policies bar Chinese-parent hosted platforms — regulated industries, government-adjacent, strict data-residency shops — will bar this endpoint as they do DeepSeek’s; unlike Qwen, there’s no Singapore-fronted international tier to soften it, so treat first-party as suitable for public and non-sensitive data only, per your counsel. Route two, Western hosts: the modified-MIT weights mean DeepInfra, Fireworks, Parasail, SiliconFlow and the OpenRouter constellation (21 providers) serve K2.6 on US/EU infrastructure under their own DPAs and compliance artefacts — your data never touches Moonshot, and this is the default recommendation for Western production use; note providers differ meaningfully on throughput and latency, so bench them. Route three, self-hosting: official vLLM/SGLang/KTransformers/TensorRT-LLM support plus native INT4 quantisation make the trillion-parameter model surprisingly deployable, with absolute data control. The residual honest caveat isn’t residency — the open weights solve that — it’s maturity: Moonshot’s enterprise machinery (support tiers, compliance depth, Western references, contractual stability) is the youngest of the major providers, its membership tiers and prices have already churned, and its production showcase skews heavily Chinese (Genspark, Tencent, XtalPi). Price that in as vendor risk on the platform, hedge it with the weights’ portability, and the models themselves are as safe to build on as anything in this cohort.