| published by | Jessica Wachtel |
|---|---|
| in blog | The New Stack |
| published date | 2026-11-15 |
| original entry | Claude Fable 5.2 vs. Opus 5.5: Same scores at almost 4x the cost |
Anthropic released Claude Fable 5.2 on November 9 and said it beats Claude Opus 5.5 in almost every capability the company measured. In the same announcement, it recommended starting with Opus for most coding and knowledge tasks, calling it its “strongest daily driver.” I wanted to find out why a company would steer people away from its best model, and whether the cheaper one really is enough.
…why a company would steer people away from its best model, and whether the cheaper one really is enough.
On Anthropic’s coding benchmarks, Fable 5.2 scored 49.1% at Xhigh effort on FrontierCode 2.0, compared with 45.5% for Opus 5.5 at Max. Anthropic also reports that Fable scored 45.3% at High effort at roughly half the cost per task of that Opus run. On FrontierSWE v2, the company reports 69.9% for Fable and 62.3% for Opus. Fable’s standard API rates are twice Opus’s: $8 per million uncached input tokens and $40 per million output tokens, versus $4 and $20.
Twice the price should make a meaningful difference, so I gave both models three coding and agent jobs and measured how well they did, how many tokens they used, what they cost, and how long they took. My tests are much smaller than Anthropic’s benchmarks and can’t prove or disprove those scores.
I ran each model once per test through Anthropic’s API at default settings, with no turn cap. Anthropic’s API defaults on Fable and Opus aren’t equal. Fable 5.2 runs at high effort, and Opus 5.5 runs at medium, so these results show what a developer gets without tuning anything. I used a script to grade each answer the model gave for each test. The dollar figures are estimated API costs based on reported token usage. Anthropic prices uncached input, cache reads, cache writes, and output separately.
Here are the tests I ran:
The models tied with perfect scores on the first version of every test, so I made each test harder and reran it twice.
This test checks whether a model can turn a detailed spec into correct code and then absorb a change without breaking it. Here’s what differed between the versions.
Both models scored 50/50 on all three versions. The difference was in how much work each one did to get there. Fable 5.2 wrote two to three times as much reasoning as Opus 5.5 on every version. The extra reasoning did not raise Fable’s score on any of the three versions.
The extra reasoning did not raise Fable’s score on any of the three versions.
Across the three scheduler versions, Opus matched Fable’s scores in 358 seconds versus 661 and cost an estimated $0.99 versus $3.29.
The numbers:
This bug hunt is similar to the work agents do for developers daily. Here’s how I adjusted the tests with each round:
This test produced the widest gap in cost and time between the two models. Both models scored 50 of 50 on all three versions, fixing the bugs the grader covered and reporting the wrong test without editing it. Opus 5.5 used fewer reasoning tokens on every version. It finished each version in under a minute, while Fable 5.2 took about one minute and 46 seconds to just under four minutes and cost eight times as much across the three.
On these runs, Fable’s extra reasoning didn’t improve its score.
The numbers:
This test rewards careful digging more than fast coding, so I expected it to favor Fable 5.2.
Here are the changes I made for each test version.
Both models scored perfectly (50 out of 50) across all three versions. Fable 5.2 took fewer turns in every version, 9 to 11 versus Opus 5.5’s 12 to 14. Across all three versions, Fable’s estimated cost was $2.54 versus Opus’s $0.91.
The numbers:
The scores were identical across all nine runs per model. Fable 5.2 cost almost four times as much and took more than twice as long.
These tests give me a reason to start with Opus 5.5 for work like this. It matched Fable 5.2’s score and finished faster on every version, at about a quarter of the estimated cost overall.
That doesn’t make Fable 5.2 a bad model. My tests were hard but short. Anthropic recommends Fable for more open-ended technical work. I tested each model at its API default, so the comparison leaves open how much of the gap comes from the different effort settings.
I’d start with Opus 5.5 and move up to Fable 5.2 only when Opus stops producing ideal results.
AI Engineer Step by step guide to becoming an AI Engineer in 2026 Introduction Working With LLMs Context Engineering AI Models Embeddings & Vector Databases Embedding Models RAGs AI Agents AI Safety and Ethics Evaluation & ObservabiityYOUTUBE.COM/THENEWSTACK
Tech moves fast, don't miss an episode. Subscribe to our YouTube channel to stream all our podcasts, interviews, demos, and more.