TUE, JULY 28, 2026
Independent · In‑Depth · Practitioner‑Tested
Large Language Models

Kimi K3 vs Claude Opus 5 After Sanctions Threat (July 28 2026): Updated Recommendation

Updated July 28 — Entity List Threat Changes the Enterprise Calculation

🕐 5 min read 👁 7 views 📅 Jul 28, 2026

UPDATED JULY 28 — SANCTIONS CHANGE THE RISK CALCULATION

Performance comparison: Unchanged — K3 SWE Marathon #1, Opus 5 ARC-AGI-3 30.2%
Price comparison: Unchanged — K3 $3/M input, Opus 5 $5/M input
NEW — Moonshot API risk: Entity List designation threatened — US enterprises may need license
NEW — Self-hosted K3 risk: Lower — Modified MIT weights already released cannot be recalled
Claude Opus 5 risk: Zero regulatory risk — US company, White House framework signatory, FLI C+
Recommendation change: Freeze new Moonshot API commitments; existing self-hosted weights lower risk

If you are evaluating K3 vs Opus 5 today: The performance and price case for K3 is unchanged. The regulatory risk has materially increased for the Moonshot-hosted API. If you need zero regulatory risk, Opus 5 is the answer. If you are comfortable with self-hosted K3 on Western infrastructure using already-downloaded Modified MIT weights, the risk is lower — but get a legal opinion before expanding production commitments.

Last updated July 28, 2026. Related: Full sanctions analysis → · Claude Opus 5 full review →

⚖ Our Verdict

Performance unchanged: K3 wins on agentic coding (SWE Marathon #1) and price ($3 vs $5/M). Opus 5 wins on reasoning (ARC-AGI-3 30.2%) and now regulatory safety (zero Entity List risk vs Moonshot API threat). NEW: Freeze new Moonshot API commitments pending sanctions resolution. Self-hosted K3 weights (Modified MIT) carry lower risk than Moonshot API.