Connect
Agents, callers, resources, and Gateways that give workloads governed access to tools and models
Connect defines the entities an agent needs to reach tools and models: agent identity, the people it acts for, resources, and Gateways. Dome stores upstream credentials on those resources, so agents authenticate to Dome rather than to every backend.
What you configure
Agents
Identify the applications and automated processes making requests, and issue the credentials that authenticate them.
Delegated agents
Act for a verified person, so Rules, Quotas, and egress can read trusted end-user claims.
Tools
Attach MCP servers and related backends as resources an agent can call.
Models
Connect LLM providers and hold their credentials server-side.
Pools
Group model connections behind one name with routing and failover.
Gateways
Package resource membership and agent grants behind a single runtime URL.
An agent reaches members only through a Gateway that admits it, and never holds the upstream credentials stored on those resources. Rules, Guards, and Quotas still decide what the call may do, what content may pass, and how much spend is allowed after admission.
Choose between standing and delegated identity on Identity Patterns. See Architecture for the full request path.
Typical workflow
- Register an agent, allow the resources it needs, and issue credentials.
- Configure delegated agents when access must depend on the person the agent acts for.
- Add tools, models, and pools when you want a stable name, routing, or failover.
- Create a Gateway, attach those resources as members, and grant the agent access.
- Point the runtime at the agent credential, Gateway endpoint, and any Act-As envelope.
Afterward you can rotate credentials, update connections and memberships, or manage lifecycle without rebuilding the rest of the configuration.