Claude Opus 5 or Fable 5: Which One Should You Pay For Your Dev Team

Two Anthropic models, one price gap that decides your budget: Claude Opus 5 costs 5 dollars per million input tokens, Claude Fable 5 costs 10. A token is the unit of text the model reads and writes, and it's what your bill is calculated on. Fable 5 costs exactly double, for the same quality of context. So the real question isn't which of the two is smarter, but which one is worth paying for your developers, task by task.

Here's the note I'd send to a CEO who signs the invoice, not to the dev who writes the code. No technical benchmarks, no charts: cost, turnaround, risk, and a verdict you can apply Monday morning.

The one number that should drive your choice: double

Let's put the prices side by side, because everything starts there. Opus 5 charges 5 dollars per million input tokens and 25 for output. Fable 5 climbs to 10 for input and 50 for output. Both models share the same 1 million token context window (the amount of code and documents the model reads in a single pass, roughly a very large repository), and the same 128,000 token output limit. The container is identical. Only the price per litre changes.

For the same work, choosing Fable 5 by default means doubling your API bill with no guarantee whatsoever of doubling what gets delivered.

This isn't an accounting footnote. These rates are public and verifiable in Anthropic's official pricing table: the 1-to-2 ratio between the two models is a billing fact, not an impression. A model that costs twice as much and buys you 5 percent more perceived quality is a bad deal on a dev budget.

How much is that per developer, per month?

Take a low, honest assumption: an AI-augmented developer who burns through 50 million input tokens and 5 million output tokens over a month of active work. On Opus 5, the API bill comes out around 375 dollars (250 for input, 125 for output). On Fable 5, it climbs to 750. 375 dollars of difference per dev per month, mechanically, for the same volume of work.

Across a team of five developers, you're looking at nearly 1,900 dollars a month gone up in smoke if you plug in Fable 5 by reflex. That's an intern's salary, every month, against a gain nothing proves in the day-to-day of coding.

Look at the last column: Opus 5 is the baseline, the line everything else positions itself around. Fable 5 isn't the standard model in a pricier version, it's the flagship. That distinction is worth money.

What Fable 5's always-on reasoning makes you pay for

That double price isn't arbitrary: it buys reasoning, and that's exactly where the budget trap snaps shut. Reasoning is the time the model spends "thinking" before it answers, producing intermediate tokens you pay for at the output rate. The more it thinks, the more thorough the answer, the higher the bill, and the longer you wait.

On Fable 5, that reasoning is always on and impossible to switch off. You pay for maximum thinking mode on every single request, even to reformat a file or fix a typo in your code. On hard tasks, a single turn can run several minutes: great for an architecture problem, ruinous for a quick fix loop where you're waiting to get back to the keyboard.

What does an effort level actually mean in practice?

It's the dial that decides how much the model thinks before it delivers. Opus 5 offers five notches: low, medium, high, xhigh, max. You can even turn reasoning off up to the "high" level. In business terms: you set the speed/cost/quality trade-off task by task, instead of having it imposed on you.

That's exactly the lever Fable 5 takes away from you. Where Opus 5 lets you drop to a low notch for a simple task and dial back up for a hard one, Fable 5 charges full throttle at all times. Note in passing that Opus 5 has a "fast mode" at 10/50 dollars, the same rate as Fable 5: only turn it on when speed genuinely matters more than cost.

Opus 5, your team's workhorse

Once that dial is in your hands, the default choice becomes obvious. Anthropic explicitly positions Opus 5 for complex agentic coding and enterprise work. Agentic coding is when the model plans, writes, tests and fixes on its own across multiple files, instead of spitting out an isolated snippet. That's precisely what an AI-augmented developer does on a real engagement.

The point that changes the math: Opus 5's low effort levels (low and medium) are unusually capable. In practice, a large share of daily work runs perfectly well on a low notch, at a reduced cost and with short latency. That's your main lever for savings, before you even pick a model.

Full disclosure: I bill AI-augmented senior developers, so I have a stake in these tools delivering on their promises. That's also why I watch the API bill closely, not just the demo. In July 2026, on the engagements I run, shifting routine tasks down a notch of effort cut the API bill almost in half without the delivered quality moving at all. The waste wasn't in the model, it was in the settings.

Why start at the lowest effort level?

Because moving up a notch costs a few seconds, whereas paying the maximum by default costs you every month. My rule is simple: I start on Opus 5 at low effort, and I only move up when a task genuinely gets stuck. A senior dev knows how to recognize that moment, and that's where at least eight years of experience earns its keep. If you want the full breakdown of API rates and subscriptions, I laid it out in this comparison of Claude Code pricing, and the question of a team's real velocity is covered in this guide on measuring velocity.

When paying for Fable 5 isn't a waste

Everything above assumes normal tasks. When that assumption breaks, Fable 5 finds its place. It's Anthropic's most capable widely available model, and it targets two specific cases: the most demanding reasoning and the longest agentic tasks, the ones where a run holds together for tens of minutes without going off the rails. A heavy migration, an overhaul of a gnarly architecture, an algorithmic problem where an Opus 5 miss would cost you more than the extra on the bill: there, paying double is justified.

Fable 5 also drags along operational constraints a CEO should know about before signing off. Three concrete points.

First, Fable 5 enforces a 30-day data retention and isn't available in zero-retention mode. Second, some requests can be refused by its safety classifiers, notably around cybersecurity and biology: a security code audit can end up blocked. Third, those multi-minute turns break the short feedback loop a fast-shipping team lives on.

Should you worry about the 30-day data retention?

For most projects, no. For a regulated client (healthcare, finance, defense) that contractually requires zero-retention mode, yes: Fable 5 is then out of the running, and Opus 5 becomes not only cheaper but the only compliant choice. That kind of constraint weighs more heavily on a project's real cost than the price per token, as I detail in this look back at the true budget of AI agents in production.

My verdict: Opus 5 for the everyday, Fable 5 on the meter

A clear recommendation, the one I apply. Opus 5 by default, at low effort, for all of the team's agentic coding. You move up a notch when a task resists, and you only pull out Fable 5 for extreme reasoning problems or very long runs, treating it as an exceptional expense you justify line by line.

How do you apply this verdict starting Monday?

The decision rule fits in one sentence: if you can't name the specific task that requires Fable 5, then Opus 5 is enough. Paying double "just in case" isn't caution, it's waste you've signed off on. Ask your lead dev which model and effort level your agents run on today: if nobody can answer, you're probably paying full price without knowing it.

"Companies don't want AI. They want to ship faster and spend less. The most expensive model is almost never the answer to that demand."

Vincent Roye, July 2026

Choosing a model isn't about buying the most prestigious one, it's about industrializing a software production line around the right unit cost. The real edge is in the tuning and the steering, not in the premium line of the catalogue. For the purely business angle of this reasoning (staffing, day rates, team structure), the GoLive Software blog carries the thinking further on the development side.

At Extra Dev, an AI-augmented senior developer (at least eight years of experience) costs 180 euros a day all in, and I staff them on Opus 5 tuned tight, not on the priciest model for comfort's sake. It's that discipline, more than the choice of model, that makes the difference on your end-of-month bill.