You do not need a Claude Pro or Max subscription to run Claude Fable 5 — Anthropic's most intelligent generally available model. The routes: the Anthropic API (pay-per-token, no session windows, frontier rates), cloud platforms (Bedrock/Vertex, same per-token economics with enterprise billing), or a flat-rate provider serving Claude 5-family models — Standard Compute exposes them over the Anthropic Messages API (/v1/messages) at a fixed monthly price from $19, which means Claude Code itself works by swapping ANTHROPIC_BASE_URL. The subscription's 5-hour windows and weekly caps do not exist on any of the API routes; the meter or the monthly budget replaces them.
| Route | Price | The catch |
|---|---|---|
| Claude Pro / Max | $20–200/mo | 5-hour session windows plus weekly caps — the limits heavy Claude Code users keep hitting |
| Anthropic API | Pay-per-token | No windows; frontier per-token rates make sustained agentic use the expensive route |
| Bedrock / Vertex | Pay-per-token | Enterprise procurement and cloud billing; same economics as the API |
| Flat-rate via Messages API (Standard Compute) | $19–249/mo flat | Fixed price against a monthly compute budget; routing decides when Fable-class is used unless you pin it |
Claude Code speaks the Anthropic Messages API, so it can point at any provider that serves that dialect: set ANTHROPIC_BASE_URL to the provider's endpoint and the agent runs outside Anthropic's plan windows entirely. That is the practical answer for people who hit the weekly cap on Monday.
The honest trade-off: first-party gives you every Anthropic variant, the newest features on day one, and the deepest Claude Code integration. The flat-rate route gives you Claude 5-family quality without windows or a per-token meter — and on a routed plan, Fable-class handles the hard requests while efficient models take the routine turns, which is what makes the fixed price survive agent workloads.
Fable 5 is the model everyone wants for hard agentic coding right now, which makes it the model everyone hits limits on. No route removes the constraint — the subscription windows it, the API meters it, a flat plan budgets it. The choice is which constraint matches your workload, not which provider found free compute.
Standard Compute serves Claude 5-family models over the Anthropic Messages API and in the OpenAI-compatible routed pool: flat plans from $19/mo, Claude Code via the ANTHROPIC_BASE_URL swap, no session windows or weekly caps. Pin Fable-class explicitly or let smart routing spend it only where the request needs it — the setup guide is at /integrations/claude-code.
Yes — Claude Code works against any endpoint serving the Anthropic Messages API. Set ANTHROPIC_BASE_URL to the provider's URL with that provider's key, and plan windows no longer apply; you are on that provider's billing instead.
They share the same underlying model; Fable 5 is the generally available version, while Mythos 5 is restricted to approved organizations. For API buyers the practical target is Fable 5.
Max's windows and weekly caps are sized for interactive use, and sublinear scaling between tiers is by design — 20x price does not buy 20x weekly volume for sustained agent work. Volume workloads belong on metered API or budgeted flat plans, with the subscription kept for what needs first-party integration.