Claude Fable 5.2 API Key: How to Access It With a Regular Key

Claude Fable 5.2 has no API key of its own, and you don't apply for it. As of November 12, 2026, three days after its November 9 release, any Claude API key you create in the Claude Console can call it: the key starts with sk-ant-, and you choose the model by putting claude-fable-5-2 in the request's model field. Whether that call works depends on the organization the key belongs to. It needs usage credits, the standard 30-day data retention rather than zero data retention, and access from a country Anthropic supports (Anthropic's Fable 5.2 overview).

So the next step is short. Create a key at platform.claude.com/settings/keys, add credits under Billing (or link the monthly API credits that come with Max, Ultra and Team plans), and send one request. A Pro or Max subscription on its own pays for Fable 5.2 inside the Claude apps, not for API calls. A working reply carries "model": "claude-fable-5-2", and a 401, 404, 400 or 429 points to the one condition that's missing.

The clouds are the exception to the one-key rule. Amazon Bedrock calls the model global.anthropic.claude-fable-5-2 or us.anthropic.claude-fable-5-2 and signs requests with AWS credentials, while Google Cloud and Microsoft Foundry use claude-fable-5-2 under their own accounts and billing.

How to create a Claude API key for Fable 5.2 in the Claude Console

The key comes from the API keys page of the Claude Console, and the steps are the same for every model, because one key calls every model your organization can use. Anthropic's Get your API key page describes them like this:

1. Sign in to, or create an account at, platform.claude.com.
2. Open the API keys page at platform.claude.com/settings/keys.
3. Click Create key, name the key, select an expiration, and set Linked account to yourself or to a service account. You can also scope the key to one workspace.
4. Copy the full key right away and store it in a secrets manager or an environment variable such as ANTHROPIC_API_KEY. The Console shows it only once.

If you are looking for a key you made earlier, the Console can't show it again, so create a new one. If Create key is grayed out, your role in the organization doesn't allow it, and an admin has to change your role or create a service account key for you. Choose the key type by who will use it: a personal key acts as you and stops working if you leave the organization, while a service account key is meant for CI jobs, services and agents.

Scoping the key to a workspace saves you a header. Anthropic's key page says a key that isn't scoped to a workspace must send an anthropic-workspace-id header with every Claude API request; a workspace-scoped key doesn't need it.

Fable 5.2 API conditions beyond the key: credit, tier, retention, region

A key only proves who is calling. Credit, rate limits, spend caps and data retention all belong to the organization behind it, so a brand-new key in a new organization can still fail on Fable 5.2 for reasons that have nothing to do with the key. Each condition has a place in the Console where you can check it, and a distinct failure when it isn't met.

Two rows need more than a table cell. The first is the usage tier. Anthropic's rate limits page says new organizations "may start in the Evaluation tier, with limits below the standard limits," and it doesn't publish those starting numbers, so the only reliable figure is the one on your own Rate limits page. Once an organization reaches a standard tier, Fable 5.2 gets 4,000 requests, 500,000 input tokens and 100,000 output tokens per minute at Start, 10,000 / 1,500,000 / 300,000 at Build, and 13,000 / 4,000,000 / 800,000 at Scale. Higher limits are requested with Request tier increase on the same page. Fast mode also waits for the Start tier: Evaluation-tier organizations get it only after they move up.

The second is data retention. Fable 5.2 is one of the models Anthropic calls Covered Models, together with Mythos 5.2, Fable 5.1, Mythos 5.1, Fable 5 and Mythos 5. They require 30-day data retention and aren't available under zero data retention unless Anthropic expressly authorizes it (Anthropic's API and data retention page). A default new organization isn't on zero data retention, so this applies only to organizations that have it set up.

Location is a plain yes or no. The supported list has 175 countries and territories as of November 12, 2026, including Japan, South Korea, Singapore, Spain, Mexico and Taiwan. Russia, Belarus, mainland China and Hong Kong aren't on it.

First Fable 5.2 call with cURL or Python

The request is a normal Messages API call with claude-fable-5-2 as the model. Keep the body to model, max_tokens and messages, because Fable 5.2 rejects several parameters that older code often sends. The headers follow Anthropic's quickstart:

export ANTHROPIC_API_KEY="sk-ant-..."

curl https://api.anthropic.com/v1/messages \
  -H "content-type: application/json" \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2026-10-21" \
  -d '{
    "model": "claude-fable-5-2",
    "max_tokens": 2048,
    "messages": [
      {"role": "user", "content": "Reply with exactly: ready. Then on a new line give 17 * 23."}
    ]
  }'

In Python, install the SDK with pip install anthropic. The client reads ANTHROPIC_API_KEY from the environment, so the key never appears in the code:

import anthropic

client = anthropic.Anthropic()

message = client.messages.create(
    model="claude-fable-5-2",
    max_tokens=2048,
    messages=[
        {"role": "user", "content": "Reply with exactly: ready. Then on a new line give 17 * 23."}
    ],
)

print(message.model)                          # which model answered
print([block.type for block in message.content])
print(message.usage.input_tokens, message.usage.output_tokens)
for block in message.content:
    if block.type == "text":
        print(block.text)

What you leave out matters as much as what you send. According to Anthropic's What's new in Claude Fable 5.2 page, adaptive thinking is always on, so thinking: {"type": "enabled"} with budget_tokens and thinking: {"type": "disabled"} both return 400; either omit thinking or send {"type": "adaptive"}. Forced tool use with tool_choice set to {"type": "any"} or {"type": "tool", ...} returns 400 invalid_request_error, and temperature, top_p and top_k should be dropped, since non-default values return 400. The older computer_20251124 tool returns 400 too, except on Bedrock.

The default effort on the API is high. For simple calls you can lower it with output_config:

"thinking": {"type": "adaptive"},
"output_config": {"effort": "low"}

The accepted levels are low, medium, high, xhigh and max. Which level is worth paying for on which task is covered in Claude Fable 5.2 vs Opus 5.5: When Fable High Beats Opus Max.

How to check that claude-fable-5-2 answered: a tested reply

Read the model field of the response, not the model's own description of itself, and, at the default or high effort, check that the content starts with a thinking block; at effort low a text-only reply is normal. On November 12, 2026, the prompt above was sent to claude-fable-5-2 through the laozhang.ai gateway, which serves the model under the same ID and in the same Messages format. The direct test against api.anthropic.com that day covered only the key check, so the reply below shows the shape of a successful Fable 5.2 response as that gateway returned it:

Disclosure: laozhang.ai is our own service. Its prices are platform pricing, not an independent comparison.

{
  "model": "claude-fable-5-2",
  "content": [
    {"type": "thinking", "thinking": "", "signature": "..."},
    {"type": "text", "text": "ready\n391"}
  ],
  "stop_reason": "end_turn",
  "usage": {"input_tokens": 33, "output_tokens": 16}
}

That default call returned HTTP 200 in 5.53 seconds with 33 input and 16 output tokens. The thinking block arrived with an empty thinking string and a signature, which is what adaptive thinking at the default effort produced on a one-line question. The same request with thinking: {"type": "adaptive"} and effort low came back in 3.07 seconds with only a text block and 6 output tokens, and effort high produced the same thinking-plus-text reply and 16 output tokens as the default. Through the gateway's OpenAI-compatible /v1/chat/completions endpoint the call also returned model: claude-fable-5-2 with 33 prompt and 16 completion tokens. Each configuration was run once, so the times are single samples, not a speed benchmark.

The usage numbers let you price a call yourself. Fable 5.2 lists at $8 per million input tokens and $40 per million output tokens (Anthropic's Fable 5.2 overview), so the default call costs 33 × $8 / 1,000,000 + 16 × $40 / 1,000,000 = $0.000264 + $0.00064, about $0.0009. If you use any service other than Anthropic, compare its charge for a call with that list-price figure, and treat a model value other than claude-fable-5-2 as a different model. How 5.2's cost per task compares with the previous version is in Fable 5.1 vs 5.2: Cheaper at Medium, Costlier at High and Max.

Fable 5.2 API errors: what 401, 404, 400 and 429 mean

Every failure on the Claude API comes back as JSON with an error.type and a message, and each one points to a different condition. The two 401 rows come from requests sent to api.anthropic.com on November 12, 2026; the others are Anthropic's documented responses from its errors reference, rate limits page and Fable 5.2 pages.

The key is checked before anything else. In the November 12 test, a request with no key header got the first 401 and a made-up key (sk-ant-api03-not-a-real-key) got the second, with the same answer under anthropic-version: 2023-06-01 and 2026-10-21, and the same 401 came back from GET /v1/models. Each reply arrived in under a second. So a 401 tells you nothing about Fable 5.2 access yet: the model name, version header and request body were never looked at. Tell the two 429s apart before retrying: on the spend-cap 429, retries, including the SDK's automatic ones, keep failing until access resumes.

A gateway can answer differently from Anthropic. Through laozhang.ai on the same day, the wrong IDs claude-fable-5.2, fable-5-2, global.anthropic.claude-fable-5-2 (the Bedrock ID) and claude-fable-5-2-latest each returned HTTP 503 api_error with "Current group default has no available channels for model …" instead of a 404, and a made-up gateway key returned 401 "Invalid token." Two of the three request shapes Anthropic rejects were accepted there: thinking: {"type": "disabled"} returned 200 and still included a thinking block, and temperature: 0.2 returned 200. Forced tool use with tool_choice: {"type": "any"} failed with a 400 there too. Code that runs cleanly through a gateway can therefore still get a 400 on api.anthropic.com, so test against the endpoint you'll ship on.

Disclosure: laozhang.ai is our own service. Its prices are platform pricing, not an independent comparison.

Is there a free Claude Fable 5.2 API key?

A key costs nothing to create; what you pay for is usage, and Anthropic offers two ways to cover some of it without buying credits. First, Anthropic's pricing page says "New users receive free credits to test the API." It doesn't publish the amount, and it doesn't say whether a new organization in the Evaluation tier can spend that credit on Fable 5.2, so check the balance on your own Billing page before you count on it.

Second, Max, Ultra and Team plans include monthly Claude API credits: $100 on Max, $200 on Ultra, and on Team $20 per Standard seat and $100 per Premium seat, pooled and capped at $500 a month (Claude Help Center article on monthly API credits). Free, Pro and Enterprise plans don't get them. You claim them after seven days on the plan under claude.ai > Settings > Billing > API credits > Link organization, for one Console organization, with no payment method needed. They work with any available model on the Claude API, Fable 5.2 included, and are spent before purchased credits, but unused credit expires each billing cycle and doesn't apply to interactive Claude Code.

Beyond that, usage is prepaid under Console > Billing > Buy credits; credits expire a year after purchase and aren't refundable, and failed requests aren't charged. Videos that promise a "free Fable key" are showing a third-party gateway's own sign-up credit, not Anthropic's. Buying safely and what each kind of credit covers is explained in Claude API Key: How to Get One, Is It Free, and Safe Buying.

Does Claude Pro or Max include Fable 5.2 API access?

Not directly. A Pro, Max or Ultra subscription doesn't pay for API calls; the API is billed separately at standard API rates, and the only overlap is the monthly API credit that Max, Ultra and Team plans can link to a Console organization.

What the subscription does cover is Fable 5.2 in the Claude apps, through the model picker. Fable models are on every paid plan and not on Free. Max, Ultra and premium Team or Enterprise seats include them up to 50% of the weekly limit, while Pro and standard Team seats pay for Fable with usage credits, except during the launch offer that includes it on Pro and standard Team seats for one week through November 16, 2026, 11:59 pm PT (Claude Help Center article on Fable models by plan). How fast Fable uses up those app limits is covered in Claude Fable 5.1 Usage Limits: Pro, Max, and Paid Credits.

Other ways to call Fable 5.2: Bedrock, Google Cloud, Foundry, gateways

If your company already pays a cloud provider, you can call Fable 5.2 there with that provider's credentials and model ID instead of a Console key. Each cloud bills and rate-limits on its own account, so an sk-ant- key does nothing on it, and a cloud credential does nothing on api.anthropic.com. The IDs below come from Anthropic's Fable 5.2 availability notes and its Bedrock pages; the Claude Platform on AWS row follows Anthropic's Claude Platform on AWS guide.

Bedrock has the most room for mistakes. Fable 5.2 runs only on the bedrock-runtime endpoint, and inference profiles exist for global and us but not for eu, jp or apac, so an EU or Asia-Pacific profile ID won't resolve. The base ID anthropic.claude-fable-5-2 is what those profiles point to.

Gateways sell access with their own key and balance. laozhang.ai, for example, has listed claude-fable-5-2 since November 10, 2026, at the same list price as Anthropic ($8 input, $40 output, $10 cache write and $0.20 cache read per million tokens), and on November 12 its model list showed 207 models from several vendors under one key. It takes Anthropic-format requests at https://api.laozhang.ai/v1/messages with a token from its Claude Code group, and OpenAI-format requests at /v1/chat/completions with a default-group token. Its docs list differences from Anthropic's API: one response is capped at 32,768 output tokens, the server tools web_search, web_fetch and code_execution return 400, there's no token counting, Message Batches or Files endpoint, and a stop-sequence hit reports stop_reason as end_turn. Whichever gateway you pick, run the check from the tested-reply section: read the model field and compare the charge with the list price.

Disclosure: laozhang.ai is our own service. Its prices are platform pricing, not an independent comparison.

Using your API key for Fable 5.2 in Claude Code

Claude Code can run Fable 5.2 on an API key, but only from version 2.1.321. Select it with /model fable or start with claude --model claude-fable-5-2. With ANTHROPIC_API_KEY set, Claude Code bills your Console organization at API rates instead of your subscription, and the monthly API credits from Max, Ultra and Team don't apply to interactive Claude Code sessions.

Check the version first with claude --version. In a test on November 10, 2026, against a local mock server that recorded what the client sent, Claude Code 2.1.321 sent both fable and claude-fable-5-2 as claude-fable-5-2, with effort medium and max_tokens 128000. Version 2.1.316 turned fable into claude-fable-5-1, and for claude-fable-5-2 it printed "Claude Code doesn't recognize the model … assumes a context window of 200k tokens" and sent it with max_tokens 32000. The same test machine still reported 2.1.316 on November 12, so an install doesn't always update itself. Whether a session is billed to the key or to the plan, and how to confirm it, is in Claude Code API Billing vs Subscription: Key, Credits, or Pro/Max; why the effort level resets is in Claude Code Effort Level: Model Defaults and Why It Won't Stick.

Claude Fable 5.2 API access: other questions

Is Fable 5.2 restricted to verified organizations like Mythos 5.2?

No. Claude Mythos 5.2 (claude-mythos-5-2) has the same specifications and price, but as of November 12, 2026, only organizations verified through Anthropic programs such as the Cyber Verification Program can call it, and an ordinary key gets no access. Fable 5.2 is available to all Claude API customers without an application (Anthropic's Fable 5.2 overview).

Which anthropic-version header should a Fable 5.2 request send?

Anthropic's quickstart uses anthropic-version: 2026-10-21 as of November 12, 2026, while older tutorials and some gateway docs still show 2023-06-01. Both values produced the same 401 for an invalid key in the November 12 test, which only shows the version header isn't checked before the key; for a valid request, follow the current quickstart.

Can I call Fable 5.2 without creating an API key?

For local development, yes. Anthropic's quickstart offers signing in with its ant command-line tool (brew install anthropics/tap/ant, then ant auth login) as an alternative to a key, and its cURL example then sends the sign-in access token as a bearer token. Services and CI jobs still need a key, preferably a service account key.

Does Fable 5.2 share rate limits with Fable 5.1?

No. As of November 12, 2026, Anthropic's rate limits page gives Fable 5.2 its own bucket, separate from the one Fable 5.1 and Fable 5 share, so heavy Fable 5.1 traffic doesn't use up your Fable 5.2 limits. Cache reads don't count toward input tokens per minute.

How long will claude-fable-5-2 stay available on the API?

Anthropic lists Fable 5.2 as active, its latest Fable model, with retirement no sooner than November 9, 2027. The ID claude-fable-5-2 is both the model ID and its alias, so code that uses it keeps pointing at this model.