Claude Fable and Dome
Run Claude Fable 5.1 for the people who need it, with a ceiling on spend.
Fable is Anthropic's model for long-horizon agentic work: a migration planned and carried out over hours. Those runs are where cost surprises come from. Dome keeps the run alive across two providers, opens Fable to a pilot group, and stops it at a ceiling you choose.
How Dome helps
Dome provides model brokering and routing for Claude Fable
Two providers for long runs
A run that takes hours shouldn't die with one provider. The pool sends the next call to Bedrock when Anthropic fails.
Open to one group
Tag Fable connections as frontier. A rule refuses them unless the person the agent acts for is in the pilot group.
A ceiling per run and per month
$1,000 a month across the pool, and 20M tokens a day for the migration agent. A long run stops at its line.
Get started
Fable with failover in five steps
Connect Fable twice, pool it, open it to the pilot group and set two ceilings.
01
Connect Anthropic
The frontier tag is what keeps Fable to the pilot group. The migration agent never sees the Anthropic key.
$ dome models add fable-51-anthropic \--provider anthropic \--model claude-fable-5-1 \--api-key "$ANTHROPIC_API_KEY" \--attributes '{"tier":"frontier"}' \--gateway prod-gateway02
Connect Amazon Bedrock
On Bedrock, Fable is us.anthropic.claude-fable-5-1. Enter it with your AWS keys and region in the dashboard, tagged tier: frontier.
03
Pool them for failover
Each call in a long run is routed on its own, so an Anthropic failure mid-run moves the next call to Bedrock.
$ dome models pool create claude-fable-5-1 \--failover-max all --gateway prod-gateway$ dome models pool member add claude-fable-5-1 fable-51-anthropic --priority 0$ dome models pool member add claude-fable-5-1 fable-51-bedrock --priority 104
Point your agent at the Gateway
The migration agent keeps the Anthropic SDK and swaps in the Gateway URL and its own Dome key.
import anthropicclient = anthropic.Anthropic(base_url=GATEWAY_URL, api_key=DOME_AGENT_KEY)client.messages.create(model="claude-fable-5-1",max_tokens=8192,messages=[{"role": "user", "content": "Plan the migration of this service."}],)05
Cap the spend
The pool cap covers everyone on Fable. The agent cap stops one runaway run without touching the rest.
$ dome quotas set --subject pool --pool claude-fable-5-1 \--unit provider_usd --limit 1000 --window monthly$ dome quotas set --subject agent --agent migration-agent \--dimension llm --unit tokens --limit 20000000 --window daily
Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Claude Fable itself, see Anthropic's documentation.
Rules
Fable for the pilot group only
Any connection tagged frontier is refused unless the person the agent acts for is in frontier-pilot. The group arrives in their identity token.
forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)when { resource has tier && resource.tier == "frontier" }unless { principal has act_as && principal.act_as.groups.contains("frontier-pilot")};Try it
One call, two outcomes
Switch the caller or the argument and watch the same call decide differently. Every decision lands in audit.
Acting for
- Agentmigration-agent is registered and active
- Callert.brennan verified, groups: frontier-pilot
- RuleFrontier models are open to frontier-pilot
- Quota$640 of $1,000 this month
Agent workflow
Bringing it together
Connecting Claude Fable to registered agents, tools, and identity in Dome completes a governed agent application.
Acting for
Control point
Gateway
- Rules
- Guards
- Quotas
Every call decided and audited
Models
FAQ
Common questions
Which providers serve Claude Fable through Dome?
Anthropic's API and Amazon Bedrock. Dome doesn't route Claude through Vertex AI.
Does Dome support Claude Fable 5 and 5.1?
Yes. Each is a model id you add as its own connection, and a pool decides which one agents reach.
Can I limit who uses Fable?
Yes. Tag its connections and write a rule on the group in the person's identity token.
How do I stop a long agent run from overspending?
Set a quota on the pool or on the agent. Once the limit is reached, further calls are refused until the window resets.
Explore
More of what Dome works with
Provider
OpenAI
The OpenAI API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
Read moreMCP server
GitHub
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Read moreIdentity
Microsoft Entra ID
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Read moreRuntime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Read moreClient
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Read moreAgent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Read moreNext steps
Talk with our FDE team
Our forward deployed engineers work with your platform team to get your agents into production and under control: the first one governed on your own systems, and a pattern your teams can repeat for every agent after it.
No card required to start. Register your first agent in minutes.
AI models for enterprise agents: failover, rules and quotas
Every model your agents call goes through the Model Broker. Pool providers for failover, decide who may call each model, and cap what it costs.
See them all