Skip to main content
Connect defines the entities an agent needs to reach tools and models: agent identity, resources, and Gateways. Dome stores upstream credentials on those resources. Agents authenticate to Dome, not to every backend. Refer to Core Concepts for how the pieces fit together and Architecture concept for the request path.

​
How Connect defines entities

The following entities are what you configure in Dome so workloads can call tools and models:
  • Agents identify the applications and automated processes making requests. Credentials authenticate inbound traffic.
    • Delegated agents act for a verified person. Dome verifies act-as before authorization so Rules, Quotas, and egress can use trusted claims. Choose standing vs delegated on the Identity Patterns concept.
  • Resources are what agents call through Dome:
    • Tools are MCP servers and related backends.
    • Models are LLM provider connections.
    • Pools group model connections behind one name with routing and failover.
  • Gateways package resource membership and agent grants behind one runtime URL.
An agent authenticates to Dome and reaches members only through a Gateway that admits it. It never holds the upstream credentials stored on those resources. , , and still decide what the call may do, what content may pass, and how much spend is allowed after admission. The typical workflow is:
  1. Register an agent, allow the resources it needs, and issue credentials.
  2. When access must depend on the person the agent acts for, configure delegated agents.
  3. Add tools, models, and pools when you want a stable name, routing, or failover.
  4. Create a Gateway, attach those resources as members, and grant the agent access.
  5. Point the runtime at the agent credential, Gateway endpoint, and any Act-As envelope.
After setup, you can rotate credentials, update connections and memberships, or manage lifecycle without rebuilding the rest of the configuration.

​
Next steps

  • Govern to authorize actions, set usage limits, and inspect content
  • Operate to investigate audit events, stream live events, and subscribe to events
  • Manage for platform access, environments, integrations, and data exports
  • Develop to send runtime credentials, Gateway endpoints, and Act-As envelopes from the application