Why Anthropic Made Fable 5 Permanently Available: Pricing War with OpenAI and Kimi
Anthropic switched its flagship Fable 5 model from a limited‑time, high‑price subscription to permanent access, but with reduced quotas and unchanged token fees, as intense price competition from OpenAI and Kimi forces the high‑price anchor to collapse.
When Fable 5 was first released, Anthropic marketed it as the "strongest model" on the market, pricing it at the highest level in the Claude family and offering only a time‑limited subscription for users.
Recently Anthropic changed the model’s policy from "pay‑per‑use after expiration" to permanent availability. The surface message is a more open stance, but the underlying reason is the price pressure from OpenAI and Kimi, whose cheaper yet competitive models have eroded the premium that Anthropic relied on.
Key limitations of the permanent access:
Permanent use is not free; Max and Team Premium plans receive only 50 % of the weekly quota.
Pro and Team standard plans do not include the model directly and still depend on usage quotas or API‑based payment.
Fable 5 API pricing remains $10 per million input tokens and $50 per million output tokens.
Anthropic is not giving away compute for free. The model stays in Max and Team Premium tiers, but with the reduced quota, and longer tasks, code agents, or enterprise workflows still require credits or direct Claude API usage.
Price pressure is the real breaking point. OpenAI has relaunched Codex and expanded ChatGPT Work quotas while also deploying cheaper, higher‑performing models to attract developers, directly challenging Anthropic’s high‑price anchor.
Kimi’s advantage lies in cost‑effectiveness: it offers comparable long‑context, multimodal, and coding capabilities at roughly half the token price of Fable 5. Developers can easily calculate that completing the same tasks with Kimi reduces token costs dramatically, undermining the notion of a "technology premium."
Therefore, Anthropic’s move is not a sudden act of goodwill; it is a response to a fierce large‑model price war that forces the company to keep an entry point while extracting reuse fees.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Architect's Tech Stack
Java backend, microservices, distributed systems, containerized programming, and more.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
