Kimi K3 Full Review: Specs, Agent, API vs DeepSeek & GPT-5

• Treating parameter count as destiny. Kimi K3’s 2.8T MoE headline is real, but only 16 of 896 experts fire per token. Peak capability still depends on your eval pack—not the trillion label alone.
• Assuming DeepSeek is “always cheaper enough.” DeepSeek V4 wins raw dollar-per-token. K3’s flat 1M context and native image/video input can erase that edge on long multimodal agent jobs.
• Mixing three vendor keys on a daily laptop. Parallel SDK scripts, Agent Swarm batches, and MCP sandboxes collide on ports and leak credentials. Isolation is part of model selection—not an afterthought.

For July frontier context, see our GPT-5.6 vs Claude vs Grok roundup and Sol/Terra/Luna open guide.

Moonshot positioned Kimi K3 as the first open-weight model in the near-3T class. Shipping channels include kimi.com, Kimi Work, Kimi Code, and the public API under model id kimi-k3.

• Architecture — Mixture-of-Experts with Stable LatentMoE; Kimi Delta Attention (KDA) plus Attention Residuals for long-sequence efficiency at 1M tokens.
• Modalities — Native text, image, and video input; text output. Always-on thinking via top-level reasoning_effort (launch default: max).
• Agent surface — Agent Swarm for massively parallel search and batch tool runs; OpenAI-SDK compatible hooks for Claude Code, Codex, Cline, and similar CLIs.
• API pricing (July 2026) — Flat across context length: about $0.30 cache-hit input, $3.00 fresh input, $15.00 output per 1M tokens.
• Weights timeline — Open weights announced for July 27, 2026. Until then, treat self-host claims as pending and validate on API first.

Quick read: K3 is the premium open-weight lane—more expensive than DeepSeek, cheaper than closed Opus-class APIs, built for long-horizon coding and Agent Swarm workloads.

Verdict: Pick Kimi K3 when 1M context, vision, and Agent Swarm matter. Keep DeepSeek for cheap bulk tokens. Keep GPT-5.6 Terra when your org already lives inside ChatGPT Work and Codex.

1. Write a one-page workload brief. Split jobs into coding, long-context, vision/video, and swarm-batch buckets with success metrics.
2. Issue three isolated API keys. Provision kimi-k3, DeepSeek V4, and GPT-5.6 Terra with hard daily spend caps.
3. Stand up a MacPull lab node. Rent a Mac mini M4 (24 GB recommended) so eval scripts never share your laptop keychain.
4. Replay identical traces. Fix schemas, temperature policy, and tool definitions. Log TTFT, pass rate, retries, and cost per case.
5. Score by lane, not aggregate. Expect K3 to win long multimodal agents, DeepSeek to win bulk text, GPT-5.6 to win ChatGPT-native workflows.
6. Lock routing and cache policy. Document primary/fallback models, K3 cache-hit targets, and rollback triggers before cutover.

• 2.8 trillion parameters — Official MoE scale with 16 of 896 experts active per token under Stable LatentMoE.
• 1,000,000-token context — Flat API pricing with no context-length tiers; cache-hit input listed near $0.30 per 1M tokens.
• $3 / $15 per 1M — Fresh input and output list prices for kimi-k3 as of the July 2026 public pricing sheet.
• July 16 / July 27 — Product and API launch window versus announced full open-weight release target.
• 24 GB unified memory — MacPull recommended floor for parallel OpenAI-compatible clients, MCP sandboxes, and week-long A/B agent runs on one M4 node.

Kimi K3 is the July 2026 open-weight flagship to beat on scale, 1M context, and Agent Swarm ambition. DeepSeek remains the cost control plane. GPT-5.6 remains the ChatGPT-ecosystem default. The wrong move is declaring a single global winner from a blog headline.

The right move is a fixed eval pack on isolated hardware: measure your prompts, assign lanes, and only then standardize. That is how teams cut token waste and ship Agent workflows without thrashing every launch week.

Ready to compare Kimi K3, DeepSeek, and GPT-5.6 with your own traces? Rent MacPull Mac mini M4 (24 GB + 512 GB recommended for multi-vendor agent sandboxes), review plans on pricing, and follow SSH setup in help. Run the bake-off on dedicated Apple Silicon—then buy the routing policy your data supports.