Skyfire and Dome
Let agents pay for services, and decide who they pay and how much. Skyfire's MCP server issues the tokens an agent uses to identify itself to a seller and pay it. Connect it to Dome once, and rules decide each pay token on its seller and its amount. Every token an agent asks for lands in one audit trail.
Dome provides a governed gatewayfor Skyfire.
Sellers on a list
Rules read the seller service on every pay token. A seller you haven't listed is refused at the Gateway.
Amounts you set
Each listed seller gets the amounts you allow. A token for any other amount is refused before Skyfire issues it.
Calls capped per day
A quota caps the tool calls an agent makes in a day, pay tokens included. Quotas count calls, not dollars.
Skyfire behind the Gatewayin four steps.
Add the hosted MCP server, sync its tools, apply the rules, and set a quota. Agents reach Skyfire through the Gateway's single MCP endpoint.
Add the Skyfire MCP server
Skyfire reads its key from a skyfire-api-key header. Dome stores the key once and sends it in that header on every call.
shelldome tools add --name skyfire \ --url https://mcp.skyfire.xyz/mcp \ --auth-method api-key \ --credential-type shared \ --authorization "$SKYFIRE_API_KEY" \ --header-secret skyfire-api-key=Authorization \ --gateway data-gatewaySync the catalog
Sync needs a valid key. Until it runs, agents get “tool not available in this gateway”.
shelldome tools catalog sync skyfireApply the rules
Scope them to one agent while you try them, and simulate before you deploy.
shelldome rules apply skyfire-payments.cedar \ --agent data-buyer --name skyfire-paymentsCap the agent's calls
Fifty tool calls a day, across every tool the agent reaches.
shelldome quotas set --subject agent --agent data-buyer \ --dimension tool --unit calls --limit 50 --window daily
Two sellers,at set amounts.
The permit opens Skyfire to the agent. The forbid refuses any pay token, with or without identity, unless it names a listed seller at one of that seller's amounts.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "skyfire" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "skyfire" && ["create-pay-token", "create-kya-payment-token"].contains(resource.tool_name)}unless { resource has arguments && resource.arguments has sellerServiceId && resource.arguments has amount && // Dappier Search ((resource.arguments.sellerServiceId == "81085b79-68d8-4a46-9f8c-63c11a969828" && ["0.50", "1.00"].contains(resource.arguments.amount)) || // Your Apify seller service (resource.arguments.sellerServiceId == "<apify-service-id>" && resource.arguments.amount == "5.00"))};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Amount
agent data-buyer · acting as m.osei
skyfire/create-pay-token(sellerServiceId: "81085b79-68d8-4a46-9f8c-63c11a969828", amount: "1.00")
- Agentdata-buyer is registered and active
- SellerDappier Search is on the list
- Rule1.00 is an allowed amount for this seller
DecisionAllowed
Three agentson Skyfire.
Each one pays narrowly or not at all. Finding sellers is open, and paying them is not.
news-briefer
Buy the morning's news
Pays Dappier for real-time search each morning and writes a briefing for the desk, and only the two listed amounts go through.
data-buyer
Pay for scraping runs
Buys a pay token for an Apify run when a research task needs fresh data, and is refused for any other seller.
seller-scout
Find new data sources
Searches Skyfire's sellers and drafts a shortlist for an analyst to review, without ever paying.
Bringing it alltogether.
Connecting Skyfire to registered agents, tools, and models in Dome completes a governed agent application.
Acting for
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
SkyfireAgent service
ApifyAgent serviceModels
Common questionsabout Skyfire.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude 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
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
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.
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.
Agent services: web, research, payments, voice and sandboxes
Web actions, research, payments, phone calls and code execution are where agents reach past your walls. Put each service behind the Gateway, and every call is authorized, metered and audited.