Sign inSign up

Connect agents to what they need

through one governed path.

Verify who each agent acts for, then connect the tools and models it calls. Credentials stay with Dome and are added on the way out.
See the platformRead the docs
CallersToolsModelsPools

Callers

The person an agent is acting for. Attach your identity provider, and callers are verified against it over OIDC (or by HMAC for services) before they become an identity. A rule can then name the caller as well as the agent, and the audit record names both. An agent can be required to always act for someone.

Attach your identity provider

Callers are verified over OIDC, or by HMAC for services.

Require a person

Make an agent always act for someone. Calls without a verified caller are refused.

Name both in the record

A rule can name the caller as well as the agent, and the audit record names both.
dome — bash
dome agents update support-triage \  --actas-required \  --actas-method oidc

Attach your identity provider

Tools

A connection to something an agent can call. An MCP server, a REST API described by OpenAPI, or an internal service. Tools surface in a catalog that policy filters per agent, so an agent sees only the tools it may call.

Connect a system

Register the supported endpoint and authentication method.

Expose the relevant operations

Surface a catalog of tools under that connection.

Control what reaches the agent

Apply access rules and content controls to the connection's traffic.
dome — bash
dome tool add --name zendesk \  --url https://mcp.zendesk.example.com \  --protocol streamable-http \  --auth-method oauth

Connect tools like

Models

A connection to a model provider. Anthropic, OpenAI, Bedrock, Vertex, Azure OpenAI, or any OpenAI-compatible endpoint, including your own. The provider credential lives with the connection and is injected at egress.

Name a provider connection

Give a model endpoint a managed identity in Dome.

Keep credentials at the boundary

Supply the provider credential when Dome sends the request upstream.

Group approved connections

Use model pools to define routing and fallback candidates.
dome — bash
dome model add anthropic-prod \  --provider anthropic \  --model claude-sonnet-5

Route to

Pools

A named group of models with a routing strategy. Priority and weight choose the member that serves a request, and failover falls through on rate limits or outages. Each candidate is authorized in its own right, so failover can't route around policy.

Fail over inside the call

A rate limit or an outage falls through to the next member.

Route by priority and weight

Choose which member serves a request, and how traffic splits between equals.

Every member is authorized

Each candidate is checked in its own right. Failover can't route around policy.
dome — bash
dome model pool create prod-models \  --routing-strategy priority_weighteddome model pool member add prod-models anthropic-prod --priority 0

Pool model families like

Every agent you run, under one system of control.

Talk with our teamGet started