One control plane for AI agents
Claude Code, Codex, Cursor and other agents, routed through your models, budgets and policies.
Supported agents
Terminal and IDE agents.
Agent setup
Point the agent, editor or desktop app at Multi-Router with an endpoint, a key and a router.
{ "env": { "ANTHROPIC_BASE_URL": "https://api.multi-router.ai", "ANTHROPIC_AUTH_TOKEN": "mr_live_7Kq2…9f2c", "ANTHROPIC_CUSTOM_HEADERS": "X-MR-Router: rt_claude_code" }}
model_provider = "multi-router"model = "gpt-5.4" [model_providers.multi-router]name = "Multi-Router"base_url = "https://api.multi-router.ai/v1"env_key = "MR_API_KEY"wire_api = "responses"http_headers = { "X-MR-Router" = "rt_codex" }
export GOOGLE_GEMINI_BASE_URL="https://api.multi-router.ai"export GEMINI_API_KEY="mr_live_7Kq2…9f2c"
{ "providers": { "anthropic": { "baseUrl": "https://api.multi-router.ai", "headers": { "X-MR-Router": "rt_pi", "X-MR-Api-Token": "mr_live_7Kq2…9f2c" } } }}
Connection
Choose where Claude Desktop sends inference requests.
GatewayEvery agent request passes through the gateway
Each request is checked against policy, routed and recorded.
Policies for every person
Route, region, models and caps are set once in a policy. Everyone it is assigned to gets an agent that follows it.
Budgets, alerts and requests for more
A cap per person and per model, alerts before the cap is reached, a clear refusal at the cap, and a request for more that an admin approves.
A portal for every person
People sign in with SSO and set up the agents their policy allows. Each sees their own budget, models, key and setup, and can ask for more budget.
- Spent
- $431.31
- 86% of $500.00
- Your pace
- $27.60
- a day, last 3 days
- Cap reached
- in 2 days
- Oct 19 at this pace
- Resets
- Nov 1
- 00:00 UTC
// ~/.claude/settings.json { "env": { "ANTHROPIC_BASE_URL": "https://api.multi-router.ai", "ANTHROPIC_AUTH_TOKEN": "sk-mr-••••9f2c", "ANTHROPIC_CUSTOM_HEADERS": "X-MR-Router: rt_cc_priya_4Kd8" } }
Offboarding, audit and rollout
Remove a person in your directory and every key and agent they hold stops. Each change is recorded, and settings reach laptops through device management.
Agents in CI
Agents in CI pipelines and Kubernetes sign in with the identity the platform already issues them. There is no static key to store or rotate.
apiVersion: v1 kind: Pod metadata: { name: triage, namespace: agents } spec: serviceAccountName: triage containers: - name: agent image: acme/triage-agent:2.4 env: - { name: MR_BASE_URL, value: https://api.multi-router.ai/v1 } - { name: MR_TOKEN_FILE, value: /var/run/mr/token } volumeMounts: [{ name: mr, mountPath: /var/run/mr }] volumes: - name: mr projected: sources: - serviceAccountToken: audience: https://api.multi-router.ai expirationSeconds: 600 path: token
Route your agents through Multi-Router
Set the agent's endpoint and API key to Multi-Router, then view its requests in Traffic.