Announcing Dome Managed Agents.

Try it now

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.

Any agent service with a remote MCP serverWeb, research, payments, voice and sandboxes go behind the Gateway like any tool.

Integration catalog
IntegrationKindGoverned byStandard
Web-action agent: Apify Actors behind the Tool Gateway, with rules on the URL of every fetch and the name of every Actor.
Agent servicesTool GatewayMCP
Prospect research agent: Apollo behind the Tool Gateway, with rules that allow lookups and refuse writes.
Agent servicesTool GatewayMCP
Web-action agent: Browserbase sessions behind the Tool Gateway, with rules on the URL of every navigation.
Agent servicesTool GatewayMCP
Sandboxed compute: Cloudflare's container MCP server behind the Tool Gateway, with rules on who runs commands and for how long.
Agent servicesTool GatewayMCP
Inbound coding agent: Devin as a registered agent on your Gateway, with its own key, rules on every tool call, and audit by name.
Agent servicesTool GatewayMCP
Inbound voice agent: ElevenLabs Agents on your Gateway, with their own key and rules on every tool call they make mid-conversation.
Agent servicesTool GatewayMCP
Web search agent: Exa behind the Tool Gateway, with rules and guards on every query before it leaves.
Agent servicesTool GatewayMCP
Web scraping agent: Firecrawl behind the Tool Gateway, with rules on the URL of every scrape and the text of every search.
Agent servicesTool GatewayMCP
Inbound legal agent: Harvey on your Gateway through per-person sign-in, with rules by lawyer and audit by name.
Agent servicesTool GatewayMCP
Inbound work assistant: Lindy as a registered agent on your Gateway, with its own key, rules on every tool call, and audit by name.
Agent servicesTool GatewayMCP
Web search agent: Linkup behind the Tool Gateway, with rules on every query and every fetched URL.
Agent servicesTool GatewayMCP
Web search agent: Parallel's Search MCP behind the Tool Gateway, with rules and guards on every objective.
Agent servicesTool GatewayMCP
Voice agent: Retell AI behind the Tool Gateway, with rules on the endpoint, number, and voice agent of every request.
Agent servicesTool GatewayMCP
Payment rail for agents: Skyfire behind the Tool Gateway, with rules on the seller and the amount of every pay token.
Agent servicesTool GatewayMCP
Web-action agent: Skyvern browser sessions behind the Tool Gateway, with rules on the URL of every navigation and login.
Agent servicesTool GatewayMCP
1–15 of 18

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.
  1. 1

    Add the service

    The service's API key stays in Dome.

    shell
    dome tools add --name web-search \  --url <service-mcp-url> \  --auth-method api-key \  --gateway prod-gateway
  2. 2

    Sync the catalog

    Its tools become available to the agents you grant them to.

    shell
    dome tools catalog sync web-search

Commands tested against a Dome workspace on September 30, 2026.

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.

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.

MCP gateway guide

What an MCP gateway does, and what to ask of one before your agents depend on it.

Every agent you run, under one system of control.