Live Nov 18 · Cohort 3Nov 18, 19:00 MSK — free hands-on AI agents live workshop · Live Cohort 3 starts Nov 23Join Nov 18 Live →Cohort 3 (Nov 23)
ReleaseInsight · On RadarRB.RU→ original

Anthropic updates Claude Fable and Mythos to 5.2: 30% faster responses, lower prices

Anthropic has updated two models in its Claude lineup, Fable and Mythos, to version 5.2. According to the company, response generation speed is up 30% and the cost of use has dropped. Both models communicate better and can run in an accelerated mode. Fable is available to a broad audience, while Mythos is so far being issued only to Anthropic's vetted partners.

AI-processed from RB.RU; edited by Hamidun News
Anthropic updates Claude Fable and Mythos to 5.2: 30% faster responses, lower prices
Source: RB.RU. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceRB.RU ↗
Editor-in-Chief
Key metric #1Fable 5.2 is available to everyone, so you can test it right now
Key metric #2Mythos 5.2 is for Anthropic's vetted partners only
Key metric #3The 30% and price figures are company claims, so measure them yourself

Anthropic has released two updated models at once: Claude Fable 5.2 and Mythos 5.2. The headline promises a rare combination: faster and cheaper at the same time. Usually you pay for speed or quality with money. But for now this is a retelling of the company's claims, and the announcement offers few details. Let's go through what is known and what is worth checking yourself.

What is known so far

According to Anthropic, response generation speed has grown by 30% for both models, and the cost of use has fallen. Both received improved communication skills, meaning they got better at holding a dialogue and phrasing answers. In addition, they can run in an accelerated mode.

Access differs. Fable is available to a broad audience: ordinary developers and teams can plug it in. Mythos is intended only for Anthropic's vetted partners. If you are not in that circle, Mythos is not available to you for now, and you will not be able to compare it with Fable on your own tasks.

What the original announcement does not include: specific prices, the size of the discount, benchmark results, and a description of how the accelerated mode works. It does not even disclose what "30% faster" means. It could be generation speed in tokens per second, or it could be response time from request to the last character. For a product, these are different things.

Why 30% does not mean "users get responses 30% faster"

Imagine a support chatbot. The user waits for an answer, and three things affect that wait: the queue on the provider's side, the time to first token, and the speed at which the text is then "typed out." If only the last one was sped up, short two- or three-line answers will barely change. Long reports and code generation will gain noticeably.

The same goes for price. "The cost has dropped" may refer to the price per token, the price of a typical task, or only one of the modes. If the model got cheaper per token but answers more verbosely, the final bill may stay the same. And if the accelerated mode is billed separately, the savings may not match expectations.

What developers and product managers should do

Don't rewrite production based on a press release. Run a short test on your own data:

  • Take 50–100 real requests from your logs, not synthetic examples.
  • Run them through your current model and through Fable 5.2 with identical settings.
  • Measure median and tail latency (p50 and p95), time to first token, and average response length.
  • Calculate the cost of one completed task, not of one token.
  • Check quality manually or via automated evaluation: a new version sometimes "improves communication" but breaks the familiar response format or structured output.

Look separately at the accelerated mode. Find out whether it is included in the regular plan or costs extra, and whether it has limits. For interactive products such as assistants, voice interfaces, and code autocompletion, it may turn out to matter more than the price cut itself.

Limitations and takeaway

The main limitation is the lack of independent measurements. All the figures come from Anthropic itself, and access to Mythos is closed, so only a handful of people will be able to verify it. For most teams, the practical part of the release is Fable 5.2.

The bottom line: if you already work on Anthropic models, the update is worth testing. With the claimed gains in speed and price, migrating could pay off quickly. If not, wait for independent benchmarks and detailed pricing. For now this is a good reason to recalculate your own AI costs, but not a reason to change your architecture.

Story

Key Questions Answered

What is known so far?

According to Anthropic, response generation speed has grown by 30% for both models, and the cost of use has fallen. Both received improved communication skills, meaning they got better at holding a dialogue and phrasing answers. In addition, they can run in an accelerated mode. Access differs. Fable is available to a broad audience: ordinary developers and teams can plug it in. Mythos is intended only for Anthropic's vetted partners.

Why 30% does not mean "users get responses 30% faster"?

Imagine a support chatbot. The user waits for an answer, and three things affect that wait: the queue on the provider's side, the time to first token, and the speed at which the text is then "typed out." If only the last one was sped up, short two- or three-line answers will barely change. Long reports and code generation will gain noticeably. The same goes for price. "The cost has dropped" may refer to the price per token, the price of a typical task, or only one of the modes.

What developers and product managers should do?

Don't rewrite production based on a press release. Run a short test on your own data: Take 50–100 real requests from your logs, not synthetic examples. Run them through your current model and through Fable 5.2 with identical settings. Measure median and tail latency (p50 and p95), time to first token, and average response length. Calculate the cost of one completed task, not of one token.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…