Agent services
Third-party agents and agent services
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.
Agent services
Third-party agents and agent services
Any agent service with a remote MCP server
Web, research, payments, voice and sandboxes go behind the Gateway like any tool.
ApifyAgent servicesWeb-action agent: Apify Actors behind the Tool Gateway, with rules on the URL of every fetch and the name of every Actor.
ApolloAgent servicesProspect research agent: Apollo behind the Tool Gateway, with rules that allow lookups and refuse writes.
BrowserbaseAgent servicesWeb-action agent: Browserbase sessions behind the Tool Gateway, with rules on the URL of every navigation.
Cloudflare ContainersAgent servicesSandboxed compute: Cloudflare's container MCP server behind the Tool Gateway, with rules on who runs commands and for how long.
DevinAgent servicesInbound coding agent: Devin as a registered agent on your Gateway, with its own key, rules on every tool call, and audit by name.
ElevenLabs AgentsAgent servicesInbound voice agent: ElevenLabs Agents on your Gateway, with their own key and rules on every tool call they make mid-conversation.
ExaAgent servicesWeb search agent: Exa behind the Tool Gateway, with rules and guards on every query before it leaves.
FirecrawlAgent servicesWeb scraping agent: Firecrawl behind the Tool Gateway, with rules on the URL of every scrape and the text of every search.
HarveyAgent servicesInbound legal agent: Harvey on your Gateway through per-person sign-in, with rules by lawyer and audit by name.
LindyAgent servicesInbound work assistant: Lindy as a registered agent on your Gateway, with its own key, rules on every tool call, and audit by name.
LinkupAgent servicesWeb search agent: Linkup behind the Tool Gateway, with rules on every query and every fetched URL.
ParallelAgent servicesWeb search agent: Parallel's Search MCP behind the Tool Gateway, with rules and guards on every objective.
Retell AIAgent servicesVoice agent: Retell AI behind the Tool Gateway, with rules on the endpoint, number, and voice agent of every request.
SkyfireAgent servicesPayment rail for agents: Skyfire behind the Tool Gateway, with rules on the seller and the amount of every pay token.SSkyvernAgent servicesWeb-action agent: Skyvern browser sessions behind the Tool Gateway, with rules on the URL of every navigation and login.How it works
Behind the Gateway like any tool
Most agent services ship a remote MCP server. Add it by URL and the same rules, quotas and audit apply.
01
Add the service
The service's API key stays in Dome.
$ dome tools add --name web-search \--url <service-mcp-url> \--auth-method api-key \--gateway prod-gateway02
Sync the catalog
Its tools become available to the agents you grant them to.
$ dome tools catalog sync web-search
Commands tested against a Dome workspace on September 30, 2026.
FAQ
Common questions
Why govern a search or browser service?
It's where an agent reaches the open web. Rules decide which agents may use it, and audit records every call.
Do agents hold the service's API key?
No. Dome holds it and injects it on each call.
Next 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.
MCP gateway guide
What an MCP gateway does, and what to ask of one before your agents depend on it.
Read the guide