claude-opus-4-5-20250929. This guide covers Claude Opus 5 vs Fable 5 benchmarks and pricing, why Kimi K3 identifies as Claude, timeline skepticism over did Moonshot steal Claude, a six-step developer routing guide, and what July 27 weight release changes. See our Kimi K3 open weights guide and OpenRouter API routing guide.Claude Opus 5 Release: Half the Cost of Fable 5, Now Default on Claude Max
Anthropic released Claude Opus 5 on July 24, 2026 (US Pacific time) and immediately made it the default model on Claude Max — the strongest model available to Claude Pro subscribers. Model ID: claude-opus-5. Available on Claude API, AWS Bedrock, Google Vertex AI, and Microsoft Foundry. Pricing holds at $5/M input and $25/M output — identical to Opus 4.8 — while performance jumped across agentic, coding, and research workloads.
The positioning is deliberate: Opus 5 is not the flagship. It is the everyday model Anthropic wants you to actually use — near-Fable intelligence without Fable pricing or Fable's 30-day data retention requirement.
| Spec | Claude Opus 5 |
|---|---|
| Release date | July 24, 2026 |
| Pricing | $5/M input · $25/M output (same as Opus 4.8) |
| Context window | 1M tokens (default, only tier) |
| Max output | 128K tokens |
| Reasoning | Thinking on by default; Effort parameter controls depth |
| Data retention | No forced retention (vs Fable 5 / Mythos 5 opt-in 30-day policy) |
| Fast mode | ~2.5× speed, 2× price (same as Opus 4.8) |
Benchmark highlights (Anthropic official):
Frontier-Bench v0.1: Beats every model; 2×+ Opus 4.8 on software engineering tasks at lower cost per task.
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: 3× the next-best model on novel problem-solving.
OSWorld 2.0: Beats Fable 5's best score using barely one-third the cost.
Zapier AutomationBench: 100% pass on end-to-end account-health workflow — prior models scored 0%.
Research / life sciences: +10.2 points on spectroscopy-to-structure inference; +7.7 on protein variant function prediction. Box reports +8% overall accuracy, +11% data analysis, +17% due diligence.
Safety and alignment: Anthropic's automated behavioral audit ranks Opus 5 as its most aligned model yet — lowest deception rate, hardest to trick into misuse, safest on hard-to-reverse actions. Opus 5 deliberately does not lead on dual-use cyber or bio risk (Mythos 5 holds that tier). Cyber classifiers intervene ~85% less than Fable 5 — usable for source-code vulnerability discovery, but binary scanning, pentesting, and exploit generation remain blocked.
Kimi K3 Distillation Controversy: White House Accusations and the Two-Week Timeline Problem
Moonshot AI launched Kimi K3 on July 16, 2026 — a 2.8T-parameter sparse MoE model (896 experts, 16 active), 1M context, native vision, built on Kimi Delta Attention. Full weights promised for July 27. Benchmarks were strong: 93.5% GPQA-Diamond, 91.2% BrowseComp, positioning K3 behind only Fable 5 and GPT-5.6 Sol at a fraction of the price. See our Kimi K3 open weights release guide for architecture and API details.
Six days later, the story turned geopolitical.
| Date | Event |
|---|---|
| Feb 2026 | Anthropic accuses Moonshot, DeepSeek, MiniMax of industrial distillation; cites 3.4M+ anomalous API calls traced to Moonshot leadership via request metadata |
| July 1, 2026 | Claude Fable 5 publicly available (previously restricted rollout) |
| July 16, 2026 | Kimi K3 API and products go live |
| July 22–23, 2026 | White House OSTP director Michael Kratsios accuses Moonshot of "large-scale, covert industrial distillation" + unlicensed Nvidia GB300 chips via Thailand |
| July 23, 2026 | TechCrunch publishes expert skepticism on distillation timeline |
| July 24, 2026 | Ryan Greenblatt publishes "K3 self-identifies as Claude" statistical analysis |
| July 27, 2026 | Planned K3 full weight release — independent verification pending |
On July 22–23, Michael Kratsios (White House OSTP) posted on X accusing Moonshot of distillation aimed at stealing Anthropic Fable capabilities, plus alleged use of export-restricted Nvidia GB300 chips routed through Thailand. Treasury Secretary Scott Bessent echoed claims of U.S. LLM "watermarks" on Chinese models — without specifying what that means. Moonshot has not responded to training-process inquiries. Kratsios provided no public evidence.
Fable 5 has only been publicly available since July 1. You can't distill that much data, train a model, and release it in two weeks. — Braden Hancock, Laude Institute / Snorkel AI co-founder
TechCrunch interviewed multiple independent researchers who pushed back on the Kimi K3 distillation controversy on timeline grounds alone. Nathan Lambert (Allen Institute for AI) argued distillation yields diminishing returns as Chinese labs shift toward reinforcement learning — if distillation alone explained K3, competitors would have cloned GLM or K3 already. Elon Musk has testified xAI distilled OpenAI models while building Grok, calling the practice industry-common. The dispute is not whether distillation happens — it is where "normal technique-borrowing" ends and "covert industrial theft" begins.
Note: As of July 25, full K3 weights are not yet public. External researchers cannot independently verify parameter count, architecture, or benchmark reproduction — a major reason the controversy remains unresolved.
Why Does Kimi K3 Say It's Claude? Greenblatt's Deployment-ID Evidence
The most technically substantive angle in the did Moonshot steal Claude debate is not political — it is behavioral. Around July 24, Redwood Research chief scientist Ryan Greenblatt published a cross-entropy analysis (GitHub: rgreenblatt/which_claude_is_k3) comparing how models respond to identity prompts.
Finding: Kimi K3 disproportionately self-identifies as Claude — and not vaguely. It sometimes emits exact Anthropic internal deployment ID strings:
claude-opus-4-5-20250929 claude-sonnet-4-5-20250929
Real Claude models do not behave this way. An actual Claude Sonnet 4.5 says "I'm Claude Sonnet 4.5." Opus 4.5 either skips version strings or gets them wrong. K3 reproduces teacher deployment metadata more accurately than the teacher states about itself — hard to explain as conversational mimicry alone.
| Model | Self-ID signal | Era locked to |
|---|---|---|
| Kimi K2 | Points to Claude Sonnet 4 | Mid-2025 Claude generation |
| Kimi K3 | Points to Claude Opus 4.5 / Sonnet 4.5 deployment IDs | Late-2025 "Claude 4.5 era" — not Fable / Mythos |
| Actual Claude models | Human-readable product names only | Current product line |
Greenblatt's interpretation: training data likely included Claude outputs labeled with deployment metadata — API logs or metadata-tagged synthetic data — a specific distillation form harder to wave away than generic style copying. The generational pattern (K2 → Sonnet 4, K3 → Opus 4.5) suggests each Kimi release absorbed whatever Claude generation was current at training time.
What it suggests: Training on Claude-labeled data with internal deployment strings — not just public chat transcripts.
What it does NOT prove: Greenblatt explicitly states this is not conclusive proof of distillation — contamination, leaked system prompts, or synthetic public datasets could theoretically explain identity confusion.
Why it matters: First technical (not political) evidence in the saga — stronger than White House rhetoric, weaker than a smoking-gun training log.
Community read (r/LocalLLaMA): Excitement that open/closed gap is measured in days; jokes that 2.8T is unrunnable locally; pragmatists say K3's real sell is price + fewer refusals, not beating Fable 5.
Compliance note: Use "alleged," "per Greenblatt's analysis," and "reported" when citing distillation claims. Identity confusion is evidence, not a verdict.
Six Steps for Developers: Opus 5 vs Fable 5 vs Kimi K3 Routing
| Model | Input ($/M) | Output ($/M) | Context | Data retention |
|---|---|---|---|---|
| Claude Opus 5 | $5.00 | $25.00 | 1M | None required |
| Claude Fable 5 | ~$10.00 | ~$50.00 | 1M | 30-day opt-in required |
| Kimi K3 | $3.00 | $15.00 | 1M | Moonshot API terms |
| GPT-5.6 Sol | ~$5.00 | ~$15.00 | 400K | OpenAI terms |
On Claude Opus 5 vs Fable 5, the CursorBench gap is 0.5% at max effort — the price gap is ~50%. For compliance-sensitive workloads, Opus 5's no-retention default may outweigh Fable's marginal benchmark edge. Route via OpenRouter for unified billing across providers.
Six operational steps:
Evaluate compliance first: If data retention, export-control exposure, or vendor provenance matters, Opus 5's no-retention policy and Anthropic contract beat K3 until Moonshot addresses distillation allegations. Fable 5 requires 30-day retention opt-in.
Compare Opus 5 vs Fable 5 on your eval set: Run CursorBench-class coding tasks and your own agent harness. Opus 5 at $5/$25 vs Fable at ~$10/$50 — validate the 0.5% gap is acceptable for your workload before paying flagship rates.
Wait for July 27 K3 weights: Do not commit production routing to K3 architecture claims until Hugging Face weights drop and independent teams reproduce benchmarks. API access is fine for experimentation; architecture-dependent decisions are not.
Verify Greenblatt findings yourself: Run identity prompts against K3, Fable 5, and Opus 5. Check whether K3 emits deployment IDs under your system prompt configuration. Document results for your compliance team.
Mixed model routing: Daily coding + agents → Opus 5; frontier repo bugs → Fable 5; cost-sensitive bulk + 1M context → K3 API; terminal-heavy → GPT-5.6 Sol. Do not all-in on one model during an unresolved controversy week.
Monitor policy developments: Track U.S. open-weight restrictions, chip export enforcement, and Moonshot's July 27 license terms. Anthropic's February 3.4M-call accusation and July White House escalation may trigger API ToS or routing policy changes.
from openai import OpenAI
client = OpenAI(
api_key="your_openrouter_key",
base_url="https://openrouter.ai/api/v1"
)
response = client.chat.completions.create(
model="anthropic/claude-opus-5",
messages=[{"role": "user", "content": "Who are you? Reply with model name and version only."}]
)The Price War, Three Hard Numbers, and What July 27 Changes
Both stories point at the same industry shift: frontier intelligence is commoditizing fast. Anthropic closes the gap between flagship and everyday models by shipping Opus 5 at unchanged Opus pricing. Moonshot pushes open weights, flat 1M context, and aggressive API rates — then gets accused of riding on Claude's outputs. The Kimi K3 distillation controversy is the first public flashpoint in a question every lab will face: when someone matches the frontier at a fraction of the cost, is it better engineering or borrowed intelligence?
| Scenario | Recommended path | Why |
|---|---|---|
| Compliance-sensitive enterprise | Claude Opus 5 API | No forced retention; near-Fable benchmarks; Anthropic contract clarity |
| Frontier coding / repo bugs | Claude Fable 5 API | FrontierSWE and GDPval v2 lead when cost is secondary |
| Cost + 1M context experiments | Kimi K3 API (pre-7/27) → self-host post-7/27 | $3/$15 with 1M flat pricing; verify weights before committing |
| Unresolved provenance risk | Wait for July 27 + independent audit | Greenblatt evidence is suggestive, not conclusive; weights unlock external verification |
| Multi-model agent production | OpenRouter mixed routing | Single billing layer; switch models without redeploying infra |
For developers: if compliance and data retention matter, Opus 5 is the easy upgrade this week. If absolute lowest cost wins and provenance risk is acceptable, revisit K3 after July 27 lets outsiders confirm the numbers.
0.5% / 50%: Opus 5 within 0.5% of Fable 5 on CursorBench 3.2 at max effort — at roughly half the per-token cost ($5/$25 vs ~$10/$50).
3.4M / 2 weeks: Anthropic's February accusation cites 3.4M+ anomalous API calls; Fable 5 public availability to K3 launch spans only ~2 weeks — timeline skeptics' core argument.
2.8T / July 27: K3 claims 2.8T parameters — largest open weights release pending; external verification gates the entire distillation debate.
Summary: Opus 5 is Anthropic's practical answer to the price war — near-flagship agentic performance without Fable pricing or retention friction. K3's distillation saga adds a provenance question on top of an already compelling cost story. Validate on your workloads, run identity checks if compliance requires it, and treat July 27 as the first real test of Moonshot's claims.
Running multi-model agent workflows on a personal Mac hits sleep cycles and network drops on long-context jobs; waiting for July 27 self-hosting needs a 64+ accelerator supernode most teams lack; relying on a single closed API misses K3's 1M flat-pricing edge. For iOS CI/CD, persistent Claude Code / Kimi Code agents, and 24/7 AI production, KVMNODE dedicated Mac Mini M4 cloud rental is usually the better host: Apple Silicon unified memory, open sudo, flexible daily/weekly/monthly terms. See the pricing page, help center, or order directly.
Data as of: July 25, 2026 · Benchmarks include Anthropic and Moonshot self-reported figures · Sources: anthropic.com/news/claude-opus-5, TechCrunch, Ryan Greenblatt GitHub (rgreenblatt/which_claude_is_k3), Moonshot/Kimi official blog, CNBC, The Verge, r/LocalLLaMA