Dome Systems

Agent runtimes

Agent frameworks and runtimes

Build agents on the framework you already use. Dome governs their tool and model calls without a rewrite.

How it works

Two changes in any framework

Load tools from the Gateway's MCP endpoint and point the model client at the Gateway. The agent's logic is untouched.

  1. 01

    Tools from the Gateway

    Any MCP client works. The agent sees only the tools it is granted.

    from langchain_mcp_adapters.client import MultiServerMCPClient
     
    mcp = MultiServerMCPClient({"dome": {
    "transport": "streamable_http",
    "url": f"{GATEWAY_URL}/mcp",
    "headers": {"Authorization": f"Bearer {DOME_AGENT_KEY}"},
    }})
    tools = await mcp.get_tools()
  2. 02

    Models through the Broker

    Any OpenAI- or Anthropic-compatible client works.

    from openai import OpenAI
     
    client = OpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)

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

FAQ

Common questions

Do I need Dome's SDK?

No. Any OpenAI- or Anthropic-compatible client and any MCP client work. The Python SDK adds ready-made LangChain models.

Where are rules enforced?

At the Gateway, on every call. In-process checks in the SDK are a pre-check.

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.