Claude Opus 5 at Half the Price — While Kimi K3 Gets Caught Calling Itself Claude

Related reading: Kimi K3 review, K3 July 27 open weights release, Claude Fable 5 export ban and alternatives, and OpenRouter API guide.

01 · TL;DR

• Claude Opus 5 (July 24, 2026): Anthropic's new daily-driver model keeps Opus 4.8 pricing at $5/$25 per million tokens but jumps in capability—CursorBench 3.2 peak scores sit within 0.5% of Fable 5 at roughly half the cost; it is now the Claude Max default with no forced data retention.
• Kimi K3 distillation row (July 16–27): Moonshot's 2.8T open MoE model drew a White House accusation of "covert industrial distillation" plus alleged unlicensed GB300 chips; independent experts say the Fable 5 public timeline (two weeks) makes deep distillation implausible; Ryan Greenblatt found K3 abnormally often self-identifies as Claude and emits strings like claude-opus-4-5-20250929—the most technical indirect evidence so far.
• Selection guidance: Compliance- and data-retention-sensitive workloads favor Opus 5 today; absolute lowest cost plus open-weight control favors revisiting K3 after July 27 when full weights allow independent reproduction—until provenance is settled, keep production routing conservative.

02 · Three Decision Pain Points

1. Value vs compliance: Opus 5 closes the gap to Fable 5 at half the price, but Fable/Mythos 5 still carry export-control friction and a 30-day data-retention opt-in; K3 is cheap and open-weight yet sits inside a geopolitical and provenance dispute—teams must trade off cost, compliance, and supply-chain risk.
2. Asymmetric evidence: The White House statement lacked public proof; researchers challenged the timeline; Greenblatt's identity statistics are the most grounded technical lead—but they do not prove distillation happened. Until July 27 weights drop, outsiders cannot independently reproduce K3 architecture or scores.
3. Verification window still open: K3's full weights are promised for July 27; as of publication, outsiders cannot independently reproduce architecture or scores—any claim that distillation is "proven" or "debunked" is premature while provenance remains disputed.

03 · Claude Opus 5 Release Breakdown

Core facts

Benchmark highlights (Anthropic official)

• Frontier-Bench v0.1: Beats every model on the market; more than 2x Opus 4.8 at lower per-task cost.
• CursorBench 3.2: At max effort, within 0.5% of Fable 5 peak at half the cost; best performance-per-dollar at high/xhigh/max tiers.
• ARC-AGI 3: Scores 3x the next-best model on novel problem-solving.
• Zapier AutomationBench: ~1.5x pass rate vs next best; even at lowest effort beats all others; 100% pass on an end-to-end workflow no prior model completed.
• OSWorld 2.0: Beats every model at any cost; exceeds Fable 5's best score using roughly one-third the spend.
• Life sciences: +10.2 percentage points on spectroscopy-to-structure inference; +7.7 points on protein variant function prediction; Box reports +11% on data-analysis workflows, +17% on due diligence, +8% overall accuracy.

"Claude Opus 5 delivers near Fable 5 intelligence at Opus speed and cost. On CursorBench it's just under Fable 5 and has many of the same behaviors." — Cursor team

"Claude Opus 5 topped Zapier's AutomationBench leaderboard without spending more tokens than prior Claude models... Previous models didn't pass; Opus 5 hit 100%." — Zapier

"On our genomics analysis work, Claude Opus 5 behaves more like a careful scientist than any model we've run." — Early biopharma customer

Alignment and safety

• Automated behavioral audit: Opus 5 is Anthropic's most aligned model to date—lowest deception rate, hardest to trick into misuse.
• Dual-use categories (offensive cyber, biology): deliberately not pushed to the frontier; limited-access Mythos 5 keeps that slot.
• Cyber classifiers fire ~85% less often than Fable 5—usable for source-level vulnerability discovery, but binary scanning, pentesting, and exploit generation remain blocked.
• Biology requests previously blocked on Fable 5 now route to Opus 5 instead of falling back to Opus 4.8.

Opus 5 timeline

Hard data point #1: Opus 5 holds Fable 5 pricing economics while landing within 0.5% on CursorBench 3.2 max effort—Anthropic's clearest "half price, nearly flagship" signal since the Fable tier launched.

04 · Kimi K3 Distillation Controversy

The model: first open 3T-class weights

Architecture: 2.8T total-parameter sparse MoE, 16 of 896 experts active per token (~50B active parameters); Kimi Delta Attention (KDA) + Attention Residuals + Stable LatentMoE; 1M-token context with native vision. Full weights promised for July 27 (not yet public at publication). See our K3 open weights release guide for hardware and licensing context.

White House accusation (July 22–23)

OSTP Director Michael Kratsios posted on X accusing Moonshot of "large-scale, covert industrial distillation aimed at stealing proprietary U.S. technology" from Anthropic's Fable model, and separately alleged use of export-restricted Nvidia GB300 chips possibly routed through servers in Thailand. Treasury Secretary Scott Bessent echoed that officials were "finding watermarks of our U.S. large language models on many of the Chinese models"—without defining what "watermarks" means. Kratsios provided no public evidence; Moonshot did not respond to training-process inquiries.

Expert pushback: the timeline does not add up

"I don't think you get a model this strong and this quickly on the heels of Fable doing strictly distillation... Fable's only been publicly available since July 1st. You can't distill that much data, train a model, and release it in two weeks." — Braden Hancock, Laude Institute / Snorkel AI co-founder

"Distillation is becoming less and less impactful over time as the Chinese models get closer to the frontier and the training regime shifts to reinforcement learning... if it were the case, everyone would be easily able to catch up to a GLM or a K3 by using its data for distillation. But we have not." — Nathan Lambert, Allen Institute for AI

Core logic: Fable 5 went public July 1; K3 shipped July 16—only two weeks. Deep distillation (especially RL-style teacher scoring) at 2.8T scale is not credible on that calendar. Elon Musk has testified xAI distilled OpenAI while building Grok, calling the practice common—the dispute is where "normal technique borrowing" ends and "covert industrial theft" begins.

February Anthropic accusation (background)

In February 2026, Anthropic publicly named Moonshot, DeepSeek, and MiniMax for "industrial-scale distillation attacks," claiming it detected over 3.4 million anomalous API interactions reflecting "deliberate capability extraction" rather than legitimate use, and said request metadata traced some activity to senior Moonshot staff. Moonshot has never confirmed or denied those claims.

Community reaction

• r/LocalLLaMA splits three ways: excitement that open/closed gaps are now measured in days; jokes that almost nobody can run 2.8T locally; pragmatism that K3's real sell is low price + fewer refusals, not beating Fable 5 outright.
• With weights locked until July 27, outsiders cannot verify parameter counts, architecture, or benchmark reproduction—fueling ongoing debate.
• Policy chatter revived: restricting Chinese open-weight models and tightening chip export controls (echoing the May Supermicro smuggling case).

05 · Why Kimi K3 Self-Identifies as Claude — The Technical Evidence

Around July 24, Ryan Greenblatt (Chief Scientist, Redwood Research; repo: rgreenblatt/which_claude_is_k3) published a cross-entropy comparison of how models answer identity prompts. Finding: Kimi K3 disproportionately self-identifies as Claude—not vaguely, but with exact internal Anthropic deployment ID strings such as claude-opus-4-5-20250929 and claude-sonnet-4-5-20250929. Real Claude Sonnet 4.5 simply says "I'm Claude Sonnet 4.5"; real Opus 4.5 often omits version strings or gets them wrong.

Greenblatt's read: when a student model reproduces a teacher's deployment metadata more accurately than the teacher states about itself, conversational mimicry is a weak explanation. It more likely indicates training on Claude data labeled with deployment metadata—API logs or synthetic sets tagged with internal IDs—a specific, harder-to-dismiss form of data transfer.

Notable pattern: K3's leaked identity locks to the Claude 4.5 era (late 2025), not current Fable/Mythos; Kimi K2 pointed at earlier Claude Sonnet 4 (mid-2025)—suggesting each Kimi generation tracks whatever Claude generation was current at training time.

Greenblatt emphasizes this does not prove distillation occurred. Identity confusion could stem from data contamination, leaked system prompts, or public-derived synthetic sets. Combined with Anthropic's February filing, though, it is the first evidence in this saga that is technical rather than purely political.

Hard data point #2: K3 emits deployment strings like claude-opus-4-5-20250929 that real Claude models rarely volunteer—statistically anomalous enough to warrant independent verification before trusting K3 in production.

06 · Both Stories Together: Price Pressure and Provenance

Opus 5 answers price pressure by closing the Fable gap at half the token bill; K3 answers it with open weights, aggressive API pricing, and minimal refusals. The K3 row is the industry's first public fight over a harder question: when a lab claims frontier-class capability at a fraction of the cost, how do you separate genuine engineering from quietly riding someone else's model?

Practical advice: match the model to the scenario first, politics second. Compliance-sensitive workloads with data-retention constraints favor Opus 5 today. Absolute lowest cost plus open-weight control favors revisiting K3 after July 27 lets independent teams reproduce the numbers—until then, K3 capability is still "vendor self-report plus speculation."

07 · Claude Opus 5 vs Fable 5 Decision Matrix

08 · Dual Event Timeline

09 · Five Mac Verification Steps

1. On an isolated rented Mac, configure Claude API (claude-opus-5) and Kimi K3 API; run one baseline completion each; log latency and token usage.
2. Run a CursorBench-class coding task on Opus 5 (small internal repo patch) and compare against historical Opus 4.8 / Fable 5 results.
3. Run Greenblatt-style identity probes on K3 ("Who are you? Report your version.") and record whether Claude deployment ID strings appear—do not store sensitive logs on your daily driver.
4. Configure Opus 5 ↔ K3 fallback via OpenRouter or custom routing; verify 429/timeout failover.
5. Export benchmark and compliance notes, revoke test keys, wipe the rental per checklist—avoid contaminating your primary Keychain during the controversy window.

10 · FAQ x5

Q: How much cheaper is Claude Opus 5 than Claude Fable 5?
A: At published token rates, Opus 5 runs about half of Fable 5 ($5/$25 vs roughly $10/$50 per million input/output tokens), while landing within 0.5% of Fable 5's CursorBench 3.2 peak.

Q: Is Claude Opus 5 the default model on Claude Max now?
A: Yes. From July 24, 2026, Opus 5 is the Claude Max default and the strongest model available to Claude Pro subscribers.

Q: Did Moonshot AI actually distill Kimi K3 from Claude?
A: Unconfirmed and disputed. The White House statement included no public evidence; researchers argue the two-week Fable-to-K3 timeline makes deep distillation implausible. Ryan Greenblatt's finding that K3 self-identifies as Claude—including exact deployment IDs—is the strongest technical indirect evidence so far, but not proof.

Q: When do Kimi K3's full weights release?
A: Moonshot committed to July 27, 2026. At publication, weights were not yet public, so independent architecture and benchmark verification remained pending.

Q: Why does Kimi K3 say it's Claude?
A: Greenblatt's statistics show K3 abnormally often self-identifies as Claude and emits strings like claude-opus-4-5-20250929 more accurately than real Claude models—likely pointing to training data tagged with deployment metadata, not mere style copying. That still does not directly prove distillation.

11 · Rent an Isolated Mac to Trial Opus 5 and Kimi K3

You can hit Claude and Kimi endpoints from a Windows laptop or Linux VPS with curl, but most Mac developers evaluate multi-model agents inside Cursor, Claude Code, and macOS Keychain—not in a headless shell. Rotating Anthropic and Moonshot keys on your daily machine, running K3 identity-probe experiments, or stress-testing fallback chains during a geopolitical news cycle leaves credentials in Keychain, pollutes local caches, and creates compliance audit trails you cannot roll back cleanly.

Windows cloud boxes handle raw API scripts but cannot reproduce Cursor plus Apple Silicon tooling end to end. Linux VPS lacks native macOS IDE integration. Buying a Mac Mini fixes hardware cost while controversy windows stay short. Day-rent isolated Apple Silicon nodes fit a 1–3 day "Opus 5 upgrade + K3 observation" sprint—run verification, export notes, destroy the instance, and keep test keys off your primary Mac. See M-series Mac compute pricing for current rates.

Hard data point #3: Opus 5's no-retention-default policy plus ~50% token savings vs Fable 5 makes a short rented-Mac bake-off the lowest-risk way to validate agent workflows before committing production routing—especially when K3 provenance remains unresolved.

12 · Sources

• Anthropic: Claude Opus 5 official release
• Ryan Greenblatt: which_claude_is_k3
• TechCrunch: experts question distillation timeline (July 23, 2026)
• MacDate: Kimi K3 review
• MacDate: OpenRouter API guide

Last updated: July 25, 2026