Claude Opus 5 Cuts the Price in Half —
Meanwhile Kimi K3 Gets Caught Calling Itself Claude

Pain points before the switch:

• Fable 5 is expensive: Flagship intelligence is real, but $10/$50 per million input/output tokens makes daily Agent workloads hard to justify.
• Opus 4.8 fell behind: The prior Opus generation lagged on hard benchmarks like CursorBench and Frontier-Bench.
• Data retention gate: Fable 5 and Mythos 5 require accepting a 30-day data retention policy—compliance-sensitive teams stayed on older tiers.
• Model ID sprawl: Claude runs across API, Bedrock, Vertex, and Foundry; confirm the unified ID is claude-opus-5 everywhere.

Anthropic released Claude Opus 5 on July 24, 2026 (US Pacific time) as its everyday workhorse model. Official positioning: near-Fable 5 intelligence at half the price. Pricing matches Opus 4.8 exactly—$5 per million input tokens, $25 per million output tokens. Context window is 1 million tokens (default and only tier). Max output is 128K tokens. Thinking is on by default; the Effort parameter controls reasoning depth.

Official benchmark highlights (re-check Anthropic's news page after launch):

• Frontier-Bench v0.1: Tops all models on software engineering tasks at 2× Opus 4.8 performance with lower per-task cost.
• CursorBench 3.2: Max effort within 0.5% of Fable 5 peak at half the cost; high / xhigh / max tiers lead on cost-performance vs every other model on the market.
• ARC-AGI 3: Novel problem-solving score is 3× the next-best model.
• OSWorld 2.0: Beats every model at any cost; exceeds Fable 5's best score at under one-third of Fable 5 spend.
• Zapier AutomationBench: End-to-end business automation pass rate ~1.5× the next-best model; lowest effort tier still beats all others; one workflow hit 100% pass rate on Opus 5.

Alignment and safety: automated behavior audits call Opus 5 Anthropic's most aligned Claude yet—lowest deception rate, hardest to jailbreak. On high-risk dual-use skills (cyber offense, biosecurity), Anthropic deliberately did not push Opus 5 to the frontier; restricted Mythos 5 still holds that slot. Cybersecurity classifiers are ~85% looser than Fable 5 for source-level vulnerability discovery while still blocking binary scanning, penetration testing, and exploit generation.

Customer quotes: Cursor called Opus 5 "near-Fable 5 intelligence at Opus speed and cost"; Zapier reported AutomationBench leadership without higher token burn; Box cited +11% on data analysis workflows, +17% on due diligence, +8% overall accuracy.

Verify current specs against Anthropic's official launch post after publication.

https://www.anthropic.com/news/claude-opus-5

Opus 5 is a straightforward product launch. Kimi K3 is not. Moonshot AI shipped Kimi K3 on July 16, 2026: 2.8 trillion (2.8T) total parameters—the first open-weight model to enter the 3T class. Sparse MoE architecture with 896 experts, 16 active per token (~50B effective activated parameters). 1M-token context plus native vision. Built on Kimi Delta Attention (KDA), Attention Residuals, and Stable LatentMoE. Full weights promised for July 27, 2026—external researchers could not independently verify at controversy peak.

For full K3 architecture and benchmark context, see our earlier deep dive: Kimi K3 open-source review.

On July 22–23, White House Office of Science and Technology Policy (OSTP) director Michael Kratsios publicly accused Moonshot of stealing Anthropic Fable model capabilities through "large-scale, covert industrial distillation." The post also referenced alleged use of unlicensed Nvidia GB300 (Grace Blackwell 300) chips, possibly routed through Thai servers. Treasury Secretary Scott Bessent added that "watermarks" from US models were found on many Chinese models, though Treasury did not define what "watermark" means. Kratsios published no supporting evidence; Moonshot did not respond to training-process inquiries.

TechCrunch (July 23) interviewed independent researchers who broadly doubt the distillation story. Snorkel AI co-founder Braden Hancock noted Fable 5 was public for only two weeks before K3 shipped—insufficient time to distill at scale, finish training, and launch. Allen Institute for AI researcher Nathan Lambert argued that as Chinese models approach the frontier, simple supervised-fine-tuning distillation yields diminishing returns; reinforcement learning is what separates leaders. If distillation were that effective, challengers would have closed the gap on GLM or K3 already—they have not.

"Large-scale, covert industrial distillation aimed at stealing proprietary U.S. technology and undermining American research is unacceptable." — Michael Kratsios, White House OSTP Director

Context: Elon Musk admitted in court that xAI distilled OpenAI models when training Grok, calling it common industry practice. Distillation itself is not automatically illegal; the fight is over the line between legitimate technical learning and covert industrial-scale extraction—the same fault line in Anthropic's February accusation and this White House escalation.

The most technically substantive angle in the whole row: Redwood Research chief scientist Ryan Greenblatt published cross-entropy analysis around July 24, 2026 comparing how models respond when asked "who are you?"

• Abnormal Claude self-identification: Kimi K3 disproportionately claims to be Claude and emits Claude internal deployment ID strings such as claude-opus-4-5-20250929 and claude-sonnet-4-5-20250929.
• More accurate than real Claude: Actual Claude Sonnet 4.5 says "I am Claude Sonnet 4.5." Opus 4.5 does not reliably report those internal version strings—or reports stale wrong ones. The student model reports teacher deployment metadata more accurately than the teacher.
• Generation-by-generation chase: K3 locks onto the "Claude 4.5 era" (late 2025), not current Fable/Mythos series. Prior K2 signals pointed at earlier Claude Sonnet 4 (mid-2025)—a pattern of chasing each Claude generation.
• Greenblatt's read: A model surfacing teacher deployment metadata more precisely than the teacher is hard to explain as style mimicry alone. More plausible: training data mixed in Claude data labeled with deployment metadata (API logs or synthetic labeled sets)—a more specific, harder-to-dismiss distillation form.
• Important caveat: Greenblatt stresses these findings do not directly prove distillation occurred. Identity confusion could also come from data contamination, system-prompt leakage, or public dataset synthesis. Combined with Anthropic's February claim, this is still stronger than a headline accusation alone.

Analysis code and writeup live on Greenblatt's GitHub repository—re-open after publication to confirm current commits.

https://github.com/rgreenblatt/which_claude_is_k3

Community reaction (Reddit r/LocalLLaMA and similar) splits three ways: celebration that open and closed gaps shrink to days not months; jokes that almost nobody can run 2.8T locally; pragmatists who say K3's real draw is low price plus lighter content filtering, not beating Fable 5 outright. Until July 27 weights drop, architecture details and benchmarks remain partially unverified externally—fuel for ongoing debate.

Read both stories together: Opus 5 answers the cost question with half-price near-flagship performance. Kimi K3 answers it with open weights and lower API rates. The distillation row is the industry asking whether that price gap comes from engineering—or from extracting someone else's model.

1. Confirm Claude console defaults: Claude Max and Pro users should verify the default switched to Opus 5. Update API calls to model ID claude-opus-5 and sync alias mappings on Bedrock, Vertex, and Foundry consoles.
2. Run CursorBench-equivalent regression: Replay 10–20 production-representative Agent tasks (code review, multi-file refactors, CI script generation) across Opus 4.8, Opus 5, and Fable 5. Log pass rates, token spend, and effort-tier quality deltas.
3. Re-evaluate data retention terms: If Fable 5's 30-day retention blocked your upgrade path, Opus 5's no-forced-retention default may unlock enterprise use—have legal review Anthropic's current DPA and terms.
4. Do not bet production solely on K3 yet: Until July 27 weights ship and third parties reproduce benchmarks, limit K3 to experimental branches. Compliance-sensitive customers should document "distillation allegation unresolved" in vendor risk registers.
5. Optionally reproduce Greenblatt's identity test: Send standardized "who are you?" prompts to K3 and Claude variants. Record whether responses emit claude-opus-4-5-* internal IDs—useful first-party material for vendor due diligence.
6. Host Gateway and Agents on always-on hardware: Whether you standardize on Opus 5, Fable 5, or multi-model routing via OpenRouter, Cursor, OpenClaw, and custom Agent gateways need a macOS host that never sleeps—laptop lid-close kills webhooks and scheduled jobs.

• Opus 5 spectral inverse molecular structure: +10.2 percentage points vs Opus 4.8 on Anthropic internal life-sciences evals.
• Protein sequence variant function prediction: Opus 5 beats Opus 4.8 by 7.7 percentage points.
• Kimi K3 GPQA-Diamond: 93.5%—highest reported open-weight score at launch (Moonshot official).
• Anthropic February distillation claim: 3.4 million anomalous API interactions attributed to Moonshot, some traced to senior staff (Anthropic public statement; Moonshot did not directly respond).

For most developers and enterprise buyers: match the model to the risk profile. Retention-sensitive, compliance-first stacks get strong value from Opus 5's unchanged pricing and step-change capability. Extreme cost and open-weight control—with tolerance for unresolved provenance questions—means waiting for July 27 K3 weights before committing production traffic.

Whether you pick Opus 5 or a multi-model gateway, running 24/7 Agents on a personal laptop hides real costs: sleep disconnects, DerivedData and log bloat, and messy multi-user permissions. For production iOS CI/CD and AI Agent automation that needs stable uptime, CALMVPS bare-metal Mac Mini rental is the stronger foundation: dedicated Apple Silicon, 120-second provisioning, flexible monthly billing, and a gateway that stays online without tying your workflow to one machine.

Further reading: Claude Fable 5 export controls and alternatives · Kimi K3 architecture and benchmark deep dive