In eleven days, two Chinese labs put near-frontier models on the table and dared you to run them yourself. Moonshot's Kimi K3 landed July 16 — 2.8 trillion parameters, a million-token context, open weights promised for July 27. Alibaba's Qwen3.8-Max previewed July 19 — 2.4 trillion parameters, multimodal, claimed "second only to Fable 5." Both are engineered around US compute limits, and both are aimed squarely at the same target: the bill you pay a closed-model provider. Here's the founder's read on which one is real today.

The one-line triage: Kimi K3 is a shippable artifact — published benchmarks, a dated weights drop, a per-token API you can prototype on this afternoon. Qwen3.8-Max is, for now, a claim — no benchmark table, no license, no weights date. Act on the first; keep a cheap eye on the second.

What's actually verified about each#

Kimi K3 is text-only, a sparse mixture-of-experts with 16 experts active per token, and it comes with numbers you can check: it took first place on the Frontend Code Arena at 1,679, ahead of Claude Fable 5 (1,631) and GPT-5.6 Sol (1,618). It's live now on the Kimi API and OpenRouter at $3 per million input / $15 per million output tokens ($0.30 cached input), and Moonshot has committed to publishing the full weights on July 27 — expected under a Modified MIT license, though the license file and checkpoint weren't up at launch. Our full Kimi K3 founder guide has the deployment math.

Qwen3.8-Max is the more ambitious spec on paper — a 2.4-trillion-parameter multimodal MoE that takes text, images, video, and documents, also with a 1M-token context. But almost everything a founder needs to make a decision is missing: the benchmark table, the model card, the license, the number of active parameters, and the open-weights date are all unpublished. Alibaba's "second only to Fable 5" is a vendor claim with no scorecard behind it. You can try the preview through Alibaba's credit-based Token Plan — running at 10% of standard pricing during the preview — and inside its Qoder and QoderWork coding platforms.

The asymmetry that decides it#

Strip away the parameter-count bragging and the two models differ on one axis that matters: how much you can verify before you commit.

Kimi K3 lets you do the whole evaluation loop today. Benchmark it against your own tasks on the API, price out inference, and — because the weights land on a known date under a permissive-ish license — plan whether self-hosting or fine-tuning beats renting. That's a decision you can actually make. If you serve open weights, we mapped where to run a model like this.

Qwen3.8-Max asks you to move on faith. Multimodal input and an integrated coding-agent platform are real advantages if the capability claim holds — but with no published benchmarks and no license, you can't price the risk. The honest move is to spend a few preview credits probing it on your own hard cases and wait for Alibaba to ship the artifact before you build anything load-bearing on it.

What a founder does this week#

The capability race between these two will get settled in benchmark tables that don't exist yet. The price race is already decided in your favor: the open-weight frontier is now a Chinese-led sprint, and every entrant lowers the floor on what a team of one pays for near-frontier intelligence. For the rest of the week's moves — the MCP spec that locks July 28 and Claude Code's data-safety fix — the throughline is the same: leverage is shifting toward the builder who keeps their options open.