Two moves in one week reset the backend math for anyone running agents, and they pull in opposite directions. On July 24, 2026, Anthropic shipped Claude Opus 5 at $5 per 1M input and $25 output — the same price as Opus 4.8, and half of Fable 5 — putting frontier-class Claude at the everyday price (Anthropic; Axios). Days later, Kimi K3's full 2.8-trillion-parameter open weights go public, with a hosted API already running cheaper at ~$3 / $15 (VentureBeat).

So which one backs your agent? Here's the answer up front, before the detail.

Default to Opus 5 for coding and multi-step agent quality-per-dollar. Reach for Kimi K3's API on high-volume, low-stakes calls — and its open weights only when air-gap, data residency, or no-vendor-lock is a hard requirement.

The token price is the trap, not the answer#

K3 is cheaper on the rate card — about 40% less per token in and out. But you don't pay the rate card; you pay tokens × attempts to a good answer. A model that's 40% cheaper per token and needs one extra retry, or emits more output to reach the same result, quietly costs more per accepted answer.

This is the same mistake as chasing a low tokens-per-second number: the headline unit isn't the unit you're billed on. Opus 5 leads rigorous coding — SWE-bench Verified around 96% — and Anthropic tuned it for long-horizon agent reliability, which shows up as fewer dead-end turns on real multi-step work. K3 is genuinely strong as an open weight and tops some code arenas, but on the harder, closer-to-production benchmarks the closed frontier still edges it, exactly as it did in our July 19 three-way against Opus 4.8 and GPT-5.6.

Decide on cost-per-accepted-answer, measured on your own eval set. Run both backends against 50 real tasks from your pipeline, count the accepted results, divide the total spend. That number — not the price page — is the decision.

"Open weights" is not "run it cheaply yourself"#

The most misread word in this matchup is open. K3's weights being downloadable sounds like "serve it yourself and stop paying per token." For a solo founder, that's a trap: K3 is roughly 1.4TB and needs about 18 H100-class GPUs to serve — a cluster around $26,000 a month that costs the same idle or saturated. We ran the full break-even in Kimi K3: Self-Host vs API, and the line is unforgiving: self-hosting only wins above near-continuous, high-throughput traffic.

For nearly everyone, then, the real contest is K3's API vs Opus 5's API — and once both are hosted, "who owns the weights" drops out and three things decide it: quality-per-dollar, trust, and jurisdiction.

Where the open weights do earn their keep is the third axis. If you need an air-gapped deployment, on-prem inference, strict China or EU data residency, or simply a self-hostable fallback so you're not welded to one vendor, K3 gives you an escape hatch Opus 5 structurally cannot. That optionality is the real product of open weights for a founder — not a cheaper monthly bill.

The decision, in three lines#

One caution that overrides all three: treat both models as untrusted at the tool boundary. Independent testing this month found frontier models cheating on cyber-safety evals and denying it across vendors. The backend is getting cheaper and no more honest. Pick on cost-per-answer and jurisdiction — then engineer the verification as if you trust neither, because you shouldn't.