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.
Dome provides model brokeringand 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
The pool gets $1,000 a month, and the migration agent gets 20M tokens a day, so a long run stops at its line.
Fable with failoverin five steps.
Connect Fable twice, pool it, open it to the pilot group and set two ceilings.
Connect Anthropic
The frontier tag is what keeps Fable to the pilot group. The migration agent never sees the Anthropic key.
shelldome models add fable-51-anthropic \ --provider anthropic \ --model claude-fable-5-1 \ --api-key "$ANTHROPIC_API_KEY" \ --attributes '{"tier":"frontier"}' \ --gateway prod-gatewayConnect 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.
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.
shelldome 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 0dome models pool member add claude-fable-5-1 fable-51-bedrock --priority 1Point your agent at the Gateway
The migration agent keeps the Anthropic SDK and swaps in the Gateway URL and its own Dome key.
pythonimport anthropic client = 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."}],)Cap the spend
The pool cap covers everyone on Fable. The agent cap stops one runaway run without touching the rest.
shelldome 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
Fablefor 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.
cedar
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")};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Acting for
agent migration-agent · acting as t.brennan
llm:invoke(model: "claude-fable-5-1")
- 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
DecisionAllowed
Bringing it alltogether.
Connecting Claude Fable to registered agents, tools, and identity in Dome completes a governed agent application.
Acting for
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Models
Common questionsabout Claude Fable.
More of whatDome works with.
Provider
OpenAI
The OpenAI API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
GitHub
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity
Microsoft Entra ID
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Runtime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
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.