Fable 5 will not run without 30-day data retention

Most API model launches change a price and a capability ceiling. Claude Fable 5's changes a data-handling floor, and for one class of customer it is the only fact about the model that matters.

The rule

Anthropic's data-retention documentation designates Claude Fable 5 and Claude Mythos 5 as Covered Models which "require 30-day data retention; ZDR is therefore not available for either model." This is a break from every other model on the API: Anthropic's stated default is that "conversation content (your prompts and Claude's outputs) is not retained by default; the exception is Covered Models."

The requirement is enforced at request time, not in the contract. An organisation whose retention configuration does not meet it gets this on every Fable 5 call:

{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "In order to access this model, your organization or workspace must have data retention enabled."
  }
}

A 400 — the same status as a malformed request. Nothing about the error type says "policy"; teams debugging it for the first time will be reading their JSON before they read their contract.

Who this hits

Zero-data-retention arrangements are the standard posture for legal, healthcare-adjacent, and confidential-workload customers — the arrangement under which "Anthropic does not store customer prompts or responses at rest after the API response is returned." Those organisations cannot call Fable 5 at all under their existing terms. The documentation is explicit that the requirement travels with the model: it "applies wherever Covered Models are offered," including Amazon Bedrock and Google Cloud, where the retained data stays in the cloud provider's environment rather than Anthropic's.

The workaround is a carve-out

Anthropic's documented path for ZDR organisations is workspace-level: enable 30-day retention for one specific workspace and route Fable 5 traffic through it, while "other workspaces in the organization keep zero data retention." It works, but note what it is — a standing exception to the organisation's data policy, scoped by workspace configuration rather than by contract. Whether that satisfies the compliance regime that motivated ZDR in the first place is a question for counsel, not for the console.

The procurement consequence

The clean alternative is one line up the price list. Claude Opus 5 carries no retention requirement and remains ZDR-eligible, and Anthropic's own refusal-handling documentation already treats Opus 5 as the peer model in the same capability tier. A ZDR shop's realistic options are therefore: stay on Opus 5, or accept a documented 30-day retention carve-out to reach Fable 5.

One more line from the same page belongs in any assessment, because it applies to every arrangement: "if a chat or session is flagged" by Anthropic's trust-and-safety systems, "Anthropic may retain inputs and outputs for up to 2 years." Zero data retention has always meant zero-by-default, not zero-under-all-conditions. Fable 5 is simply the first model to move the default itself.

Primary source: Anthropic's API and data retention documentation, read 2026-07-30.