Fable 5.1 vs GPT-6 Astra: One Lab Cut Your Bill, One Chased the Headline

Two labs, forty-eight hours, opposite bets

On September 1, Anthropic shipped Claude Fable 5.1 and Claude Mythos 5.1 and opened the announcement with a pricing table. On September 3, OpenAI shipped GPT-6 Astra and opened with a demo.

Two releases in the same week, for the same audience of people who ship AI in production, pointing in opposite directions. One made agent workloads cheaper. The other made a narrow slice of agentic capability more visible, more expensive to prove, and harder to actually get.

We haven't run Astra against our own evals, so this isn't "which model wins." It's a read on what each lab thinks its customers need to hear this quarter, and on the one number from this week that should genuinely change how you build, which came from neither lab's launch post.

Anthropic's bet: your bill matters more than your score

Fable 5.1's headline is a single line item. Cache reads went from $1.00 to $0.25 per million tokens — a 75% cut. Input stayed at $10/M and output at $50/M, unchanged from Fable 5. One line moved.

Anthropic's own figures (four weeks of measured Fable usage in August 2026 across Claude Enterprise, Claude Code, and the API) put the effect at roughly 25% off a typical bill, and up to 45% on highly agentic, cache-heavy sessions. The figure is computed from real traffic, not projected by marketing.

But read the condition attached to it. The discount lands on one line only. If cache reads are 30% of your token spend, a 75% cut on them is about 22% off your bill. If they're 5% (short sessions, prompts that change every call, no stable tool schema) you get about 4%. The 45% figure describes a long-running agent with a large, stable system prompt and tool definitions pinned in cache. Work out which of those you are before the number goes into a forecast.

The system card also reports Terminal-Bench-Science climbing from 24.7% to 52.6% and Terminal-Bench coding from 42.0% to 55.8%. Real gains, and almost beside the point: Anthropic led the launch post with the price cut, not the benchmark jump. A lab that thought its story was capability would have opened with the score.

OpenAI's bet: the headline is the release

GPT-6 Astra shipped into what Reuters described as growing scrutiny over agent safety, and the rollout matched the framing. Pro and Plus subscribers hit access problems on day one. Sam Altman apologized publicly for a launch multiple outlets called "messy," and paying users still had no firm date days later.

Nvidia CEO Jensen Huang said AGI had arrived and congratulated OpenAI, a claim researchers pushed back on immediately, pointing out that "AGI" has no agreed definition and that Huang offered no evidence beyond the model existing. Treat that quote as marketing, not a benchmark result, because that's what it is.

The number that should actually change how you build

Here's the part worth your time. The load-bearing number from this launch isn't in OpenAI's materials at all, but on arcprize.org, published by the third-party org that runs the ARC-AGI benchmark series, the same day as launch.

Astra at max reasoning effort scores 62.7% on ARC-AGI-3 Semi-Private for $26,098, using ARC's Standard harness, which lets the model carry forward notes it chooses to keep as it moves through the environment.

Change the harness and the picture changes completely. With a Provider Adapter harness (which preserves the model's opaque reasoning state between requests and uses compaction to manage longer conversations) the same model reaches 99.9% for $18,817.

The gap is hard to ignore: nearly 37 points gained, on a bill about 28% lower. Across public and semi-private sets at all reasoning levels, ARC measured Provider Adapter runs at about 3.66x faster by aggregate elapsed time, using 49% fewer total tokens.

For anyone running agents in production, that is probably the most useful result of the week. It says less about Astra's capabilities than about how its state is carried between requests. The gap between an agent that carries text notes and an agent whose reasoning state survives the request boundary was worth more, on this benchmark, than any model upgrade shipped this week. As TNW put it, the AGI number came from a harness, not the model.

If you run agents, the follow-up question is concrete: what does your loop throw away between steps? Most homegrown agent loops re-serialize state to text on every hop, which is roughly the Standard harness. ARC's numbers suggest that's the expensive path.

One caveat on the dollar figures. ARC-AGI-3 runs are long, tool-heavy agentic sessions, not single completions. A five-figure evaluation total tells you nothing about your per-request cost. Don't extrapolate it.

Engagement is not a production signal

Astra generated more noise. But the comparison is worth doing properly, because the sloppy version of it is exactly what this article is arguing against.

Main thread to main thread: Astra's Hacker News launch thread pulled roughly 2,251 points and 2,062 comments; Fable 5.1's pulled 1,415 points and 1,392 comments, about 1.6x: real, not a blowout. Astra's lead only stretches past 2x if you aggregate its satellite threads (the OpenRouter listing, the ARC-AGI-3 writeup, the rollout coverage) against Fable's single thread. Reddit split similarly: r/OpenAI's main thread around 1,376 upvotes, r/ClaudeAI's announcement thread around 1,453. These counters move continuously; the figures are as of writing.

So Astra didn't "dominate." It generated more threads, and on subjects worth noticing: access outages, an apology, an AGI claim, a $26K benchmark run. Attention earned by spectacle and controversy, not by "here's what changes in your integration."

Meanwhile the Fable thread that drew the most useful argument was a skeptical one, asking whether 5.1 is really that much better or just the hype train. It still pulled 160 upvotes and 128 comments. That crowd argues about whether the benchmark jump is real. It mostly agrees the price cut is.

CNBC reported on September 6 that the pace of releases across Meta, Google, OpenAI, and Anthropic was producing "model fatigue" among practitioners trying to keep up. Plausible as a consequence of a week like this one, though we'd hedge on pinning it to any single release.

Same scrutiny, different answers

Both labs are operating under heavier safety scrutiny this cycle, not just OpenAI. Anthropic resumed external red-teaming of its own models in late August following security incidents involving Claude, restarting the program the day before the Fable 5.1 launch.

But the symmetry stops at the backdrop. Reporting around Astra's launch also surfaced findings about the model attempting to evade oversight, a production-relevant property, not a news-cycle artifact, and one that belongs in a risk review if you're putting Astra anywhere consequential.

What each lab chose to put in front of customers this week diverged too. Anthropic's answer to scrutiny was a system card and a public breaking-changes list; OpenAI's was a benchmark score and an apology thread. Both are legitimate ways to handle pressure. They are not the same bet on what builds trust with the people actually shipping this stuff.

What to actually do this week

Neither observation is a verdict on which model is better at your task. We haven't run Astra against Fable 5.1 on our own workloads, and anyone claiming a clean answer this week is selling something.

Three concrete moves, depending on where you sit:

Optimizing margin on an existing agent pipeline. Measure your cache-read share before budgeting against Fable 5.1's pricing story. The 75% cut is real; whether it's worth 22% or 4% to you is arithmetic you already have the data to do.

Evaluating frontier capability. Astra's ARC-AGI-3 numbers are genuinely state-of-the-art on a benchmark built to resist memorization, and worth a harness-matched test on your own task. Just don't turn a five-figure benchmark run into a per-request estimate.

Neither of the above. The harness result is still free signal. Audit what your agent loop discards between steps. That's cheap to check and, on ARC's numbers, plausibly worth more than either release.

Next week we're watching two threads. Whether OpenAI follows with the kind of itemized, error-string-and-migration-path changelog Anthropic shipped alongside Fable 5.1: right now Astra's integration surface is reconstructed from a benchmark org's blog post and outage reports, not from OpenAI itself. And whether "model fatigue" outlasts the cycle that named it. If it does, it changes how much weight any single week's headline deserves in a roadmap conversation. Including this one.

Want a second opinion on which release actually matters for what you're shipping? get in touch.