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

On July 24, 2026 (US Pacific time), Anthropic shipped Claude Opus 5 and immediately made it the default model on Claude Max — the strongest model available to Claude Pro subscribers. Model ID: claude-opus-5, reachable via Claude API, AWS Bedrock, Google Vertex AI, and Microsoft Foundry.

• Claude Opus 5 pricing unchanged: $5/M input tokens, $25/M output tokens — identical to Opus 4.8. Fast mode runs ~2.5x faster at 2x the base price.
• Context: 1M tokens (default and only tier), 128K max output. Thinking is on by default; the Effort parameter controls reasoning depth.
• Data retention: Like every prior Opus model, general access carries no forced 30-day data retention. Fable 5 and Mythos 5 require opting into retention.

Box reported an 11% lift on data-analysis workflows, 17% on due diligence, and 8% overall accuracy. In life sciences, Opus 5 scored 10.2 percentage points higher than Opus 4.8 on inferring molecular structure from spectroscopy, and 7.7 points higher on predicting protein variant function.

If Fable 5 felt out of budget, Opus 5 is Anthropic's answer: give up almost nothing on hard agent and coding tasks for half the token bill. Use this matrix to decide quickly:

The Cursor team put it plainly: "Claude Opus 5 delivers near Fable 5 intelligence at Opus speed and cost." Zapier noted Opus 5 topped AutomationBench without burning more tokens. For multi-model routing, see our OpenRouter integration guide for fallback configuration.

Opus 5 is a straightforward product launch. Kimi K3 is a geopolitical story. Moonshot AI released Kimi K3 on July 16, 2026: 2.8 trillion total parameters in a sparse MoE layout (896 experts, 16 active per token — roughly 50B active parameters), 1M-token context, native vision, GPQA-Diamond 93.5%, BrowseComp 91.2%. Full weights were promised for July 27 — meaning outsiders could not independently verify architecture or scores when the controversy erupted.

Kratsios wrote: "Large-scale, covert industrial distillation aimed at stealing proprietary U.S. technology… is unacceptable." Treasury Secretary Scott Bessent echoed that officials were "finding watermarks of our U.S. large language models on many of the Chinese models" — without specifying what those watermarks are.

• Timeline rebuttal: Fable 5 has been publicly available only since July 1 — just two weeks before K3 shipped. Snorkel AI co-founder Braden Hancock: "You can't distill that much data, train a model, and release it in two weeks."
• Diminishing returns: Allen Institute researcher Nathan Lambert argues distillation matters less as Chinese labs close the frontier gap; reinforcement learning training is the real differentiator now.
• Industry double standard: Elon Musk testified that xAI distilled OpenAI models while building Grok, calling the practice common — the dispute is where "normal technique-borrowing" ends and "covert industrial theft" begins.

This is the angle worth your time as a technical reader — and one almost nobody outside a GitHub repo has covered in depth. Around July 24, Redwood Research Chief Scientist Ryan Greenblatt published a statistical analysis (GitHub: rgreenblatt/which_claude_is_k3) comparing how models respond when asked to identify themselves.

• Kimi K3 disproportionately self-identifies as Claude, sometimes emitting exact internal Anthropic deployment IDs like claude-opus-4-5-20250929 and claude-sonnet-4-5-20250929.
• Real Claude models don't do this: Sonnet 4.5 simply says "I'm Claude Sonnet 4.5." Opus 4.5 either skips the version string or gets it wrong.
• Generation-by-generation pattern: K2's signal pointed to Claude Sonnet 4 (mid-2025); K3 points to Opus 4.5 (late 2025) — not the current Fable/Mythos generation.

Greenblatt's read: a model reproducing its teacher's deployment metadata more accurately than the teacher states it about itself is hard to explain as conversational mimicry. It more likely means training data included Claude samples labeled with deployment metadata — API logs or tagged synthetic data. That connects to our earlier piece on Claude Code fingerprints and tracking: identity leakage is a meaningful signal for detecting data contamination.

• API bill vs. compute bill: Opus 5's half-price positioning helps — but agents running on shared VPS hosts or desk-side Macs lose those savings to queue jitter and dropped long connections.
• Compliance and supply chain: Fable 5 / Mythos 5's 30-day retention policy is a hard gate for finance and healthcare. K3's distillation accusation adds export-control and policy uncertainty.
• Open-weight verification window: Until July 27, K3 architecture and scores are "vendor claims plus outside guesses" — production adoption carries information asymmetry.
• Routing complexity: Multi-model fallback (Opus 5 + K3 + local inference) needs stable CI and a dedicated agent host — not just a new API key.

1. 01
   Audit existing Claude calls: check whether endpoints still point to Opus 4.8 or Fable 5. Claude Max users should confirm the console switched to Opus 5 as default.
2. 02
   Run CursorBench or internal smoke tests: compare Opus 5 vs Fable 5 on your real codebase at high and max effort — track pass rate and token spend side by side.
3. 03
   Evaluate data retention terms: compliance-sensitive workloads should default to Opus 5 (no forced retention). If you need Fable 5's peak capability, assess the 30-day retention policy separately.
4. 04
   Hold K3 out of production for now: wait for the July 27 weight drop, independently reproduce GPQA-Diamond / SWE Marathon scores, and run Greenblatt-style identity probe tests.
5. 05
   Configure multi-model routing: use OpenRouter or LiteLLM to set Opus 5 as primary with an open-weight fallback; log model ID and cost on every call.
6. 06
   Deploy a stable agent host: long agent sessions need dedicated compute and reliable SSH. Review pricing for NUKCLOUD dedicated Mac nodes as your CI and agent build plane — shared-pool tail latency can erase API cost wins.

Opus 5 answers price pressure with "half the cost, nearly the same intelligence." Kimi K3 answers with open weights, lower API pricing, and fewer refusals. The K3 distillation controversy is really the industry's first public fight over a harder question: when a lab claims frontier performance at a fraction of the price, how do you tell better engineering from quietly riding someone else's model?

For most developers: match the model to the scenario, then to your risk tolerance. Compliance, data retention, and supply-chain sensitivity → Opus 5 is an easy upgrade. Absolute lowest cost and open weights → revisit K3 after July 27 independent benchmarks. On r/LocalLLaMA, three camps coexist: excitement that open-closed gaps now shrink in days not months; jokes that nobody can run 2.8T locally; and a pragmatic view that K3's real edge is price plus fewer refusals, not beating Fable 5 outright.

Teams driving long-running Opus 5 or K3 agents against large codebases still need a stable, auditable local dev and CI plane. Shared minute pools, desk-side Macs, and oversubscribed VPS hosts introduce bandwidth jitter, neighbor CPU contention, and dropped long-lived connections — friction that quickly eats token savings. For production agent hosts, NUKCLOUD multi-region bare-metal Mac / cloud Mac nodes provide dedicated Apple Silicon compute with clear tenant boundaries. Compare specs on the pricing page and provision a trial via order.

Data as of 2026-07-25. Sources: Anthropic official release, Moonshot/Kimi technical blog, TechCrunch, Ryan Greenblatt GitHub, CNBC, The Verge.