OpenAI Agents SDK and Dome
Keep your agents, and govern every call they make. Swap the SDK's model client for one pointed at Dome and add the Gateway as an MCP server. Handoffs and the run loop keep working. Claude can sit behind the same client as GPT, and the record of every call stays in your workspace.
Dome governs every tool and model callin OpenAI Agents SDK.
Handoffs stay as they are
Agents, instructions and handoffs are unchanged. The model client and the MCP server change.
Any model behind one client
The SDK's chat completions model talks to the Broker's OpenAI-compatible endpoint. The model name is a pool, so Claude and GPT sit behind the same client.
Audit stays in your workspace
Turn off the SDK's tracing export and Dome keeps the record. Every model and tool call lands against the agent that made it.
OpenAI Agents SDK on Domein two changes.
The agent gets an OpenAIChatCompletionsModel on the Broker and an MCPServerStreamableHttp on the Gateway, and its definition is untouched.
Install the SDK
OpenAI's Agents SDK has its MCP support built in and needs Python 3.10 or later.
shellpip install openai-agentsLoad tools from the Gateway
MCPServerStreamableHttp lists only the tools this agent is granted, with their real schemas.
pythonfrom agents.mcp import MCPServerStreamableHttp dome = MCPServerStreamableHttp( name="dome", params={ "url": f"{GATEWAY_URL}/mcp", "headers": {"Authorization": f"Bearer {DOME_AGENT_KEY}"}, }, cache_tools_list=True,)Call models through the Broker
Use an OpenAI client, set the Gateway as its base URL, and name a pool as the model.
pythonfrom openai import AsyncOpenAIfrom agents import OpenAIChatCompletionsModel broker = AsyncOpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)model = OpenAIChatCompletionsModel(model="claude-opus-5-5", openai_client=broker)
One agent,end to end.
An Agents SDK agent whose model client points at the Broker and whose MCP server is the Gateway. Tracing stays off; the record lives in Dome.
researcher
Answer questions about the code
Runner works the question through the GitHub tools. The Gateway decides each tool call, and Opus answers through the Broker.
python
import asyncio
from openai import AsyncOpenAIfrom agents import Agent, OpenAIChatCompletionsModel, Runner, set_tracing_disabledfrom agents.mcp import MCPServerStreamableHttp
set_tracing_disabled(True) # Dome keeps the audit trail
async def main(): # Model: a pool on the Broker, through the OpenAI-compatible endpoint broker = AsyncOpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY) model = OpenAIChatCompletionsModel(model="claude-opus-5-5", openai_client=broker)
# Tools: whatever this agent is granted on the Gateway async with MCPServerStreamableHttp( name="dome", params={ "url": f"{GATEWAY_URL}/mcp", "headers": {"Authorization": f"Bearer {DOME_AGENT_KEY}"}, }, cache_tools_list=True, ) as dome: researcher = Agent( name="researcher", instructions="Answer questions about the code. Search before you answer.", model=model, mcp_servers=[dome], ) result = await Runner.run(researcher, "Where is rate limiting handled?") print(result.final_output)
asyncio.run(main())Bringing it alltogether.
Connecting OpenAI Agents SDK agents to tools, models, and identity in Dome completes a governed agent application.
Acting for
Agent
OpenAI Agents SDKRuntime
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Models
Common questionsabout OpenAI Agents SDK.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
Atlassian
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Identity
Microsoft Entra ID
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
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.
Agent frameworks and runtimes: govern agents without a rewrite
Build agents on the framework you already use. Dome governs their tool and model calls without a rewrite.