multi-router.aidocs

Routing

Managing Routers

Find, inspect, enable, disable and delete routers in the dashboard and through the API.

Routers are managed on the Routers page of the dashboard and through the /v1/routers API. Organization admins create, change, enable, disable and delete routers, organization members can view them, and API keys need the router scopes described below.

The Routers page

The Routers page lists every router in the selected organization. A strip at the top shows Routers and Enabled, counted over the routers that match the current filters, with Aliases, Requests 24h, Errors 24h and p95 24h. The table lists each router's name and id with optional columns:

ColumnShows
Statusenabled, disabled, unconfigured for a router with no model, or needs re-save for a Claude Proxy whose routing has not been saved.
ModelThe router's model, or its members or route.
PromptThe bound prompt.
AliasesThe router's aliases.
24h reqRequests in the last 24 hours.
UpdatedWhen the router last changed. Sorting by it toggles newest and oldest first.
Engineering · org_7Tq2Wd9KxP

All routers

Save viewNew router
Status:
AllActiveDisabled
Filters
Search name, id, model, tag, alias…
Export
Routers
8
Enabled
7
Aliases
3
Requests 24h
70K
Errors 24h
312
p95 24h
1840 ms
Routers
1–8 of 825 / page
Columns
Updated
NameStatusModelPromptAliases24h reqUpdated
Eng proxy
rt_5Tc7Hn1GsR
enabledbedrock-geo route
—
claude-code
41K12m ago
Support bot
rt_9Hk3Ws7PzQ
enabledanthropic / anthropic/claude-sonnet-4.5
support-system
ip_5Gk2Nw8QvL@latest
production
18K2h ago
claude-fallback
rt_6Fp1Zr4MxJ
enabled2 members
—
support-ha
2.1K5h ago
Support bot · Bedrock EU
rt_2Lw6Yd8NcV
enabledbedrock / anthropic/claude-sonnet-4.5
support-system
ip_5Gk2Nw8QvL@latest
—1.2K1d ago
Support bot A/B
rt_3Qa8Jk2VnE
enabled2 members
—
—9403d ago
codex-eng
rt_8Mv4Bq6LdY
enabledOpenAI Responses passthrough
—
—6.3K6d ago
Draft classifier
rt_1Xe9Pw3KcU
unconfiguredpick a model
—
——9d ago
Legacy summarizer
rt_4Nd2Rs8TfB
disabledopenai / openai/gpt-5-mini
summarize.md
pr_7Jw3Hc5XmD@3f9c2e1
——5/18/2026
The Routers page: the views rail, filters, 24-hour stats, and each router's type, status, model, prompt, aliases and requests. Select to enlarge.

The Columns picker shows or hides columns. The filter bar filters by status (All, Active or Disabled), by Provider, Model, Tag, Has prompt, Has aliases and Updated, and by a search across name, id, provider, model, tag and alias. Export downloads the visible rows as CSV. The views rail offers pinned views (All routers, With aliases, Recently changed and Disabled), views by router type, saved views, and tags.

The router page

Each router has a page with a header and an Overview tab. The header shows the router's name, status, type, tags, description, id with Copy router ID, and creation and change dates, with Disable or Enable and Delete. The Overview tab shows the Aliases panel, the type's main panel (Model for a static router, Rules and Routing for an Adaptive Router, Members for a fallback or weighted router, Routing for a Claude Proxy, Forwarding for a Codex Proxy or Gemini Proxy), and the Prompt, Request Logging and Settings panels that apply to the type. See Router Settings.

Enabling and disabling

Disabling a router stops it from serving: requests to it, and through its aliases, return router_disabled, while its configuration is kept. Disabling acts as a kill switch for a model or an application, and enabling the router restores it. A disabled member of a fallback or weighted router is skipped. Routers are disabled and enabled from the router's page, from the Routers table, or with PATCH /v1/routers/{id} and {"enabled": false} or {"enabled": true}.

Deleting a router

Deleting a router removes it permanently. A router must be disabled before it is deleted, must have no aliases pointing to it, and must not be a member of a fallback or weighted router. A router created by a tools policy is enabled, disabled, changed and deleted through the policy, and aliases cannot point to it.

Router API

The router endpoints act on the routers of the API key's organization:

MethodPathDescriptionScope
POST/v1/routersCreate a router. Accepts an Idempotency-Key header and dry_run.routers:write
GET/v1/routersList routers, newest change first, paged with limit (1 to 200, default 50) and cursor, and filtered with kind and tag.routers:read
GET/v1/routers/{id}Get a router by id, with its tags and aliases.routers:read
PATCH/v1/routers/{id}Change a router, including enabling and disabling it with enabled.routers:write
DELETE/v1/routers/{id}Delete a disabled router with no aliases.routers:delete

Scopes are cumulative: routers:delete includes write, and write includes read. An API key with no scopes has full control, and a key without the required scope receives 403 insufficient_scope. Limiting a key to specific routers controls which routers it sends requests through; a key with routers:read lists every router in the organization. The list response holds the routers in data with next_cursor and has_more, and kind accepts static, fallback, weighted, adaptive_router, claude_proxy, codex_proxy or gemini_proxy. Members, aliases and tags have their own endpoints; see Routers in the API Reference. With a kind filter, a page can hold fewer routers than the limit while more remain, so continue until next_cursor is null.

Disable, then delete, a routerbash
curl -X PATCH https://api.multi-router.ai/v1/routers/rt_9Hk3Ws7PzQ \
  -H "Authorization: Bearer $MR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "enabled": false }'

curl -X DELETE https://api.multi-router.ai/v1/routers/rt_9Hk3Ws7PzQ \
  -H "Authorization: Bearer $MR_API_KEY"
Delete response 200json
{ "organization_id": "org_7Tq2Wd9KxP", "id": "rt_9Hk3Ws7PzQ", "object": "router", "deleted": true }

Errors

Managing routers returns the following errors:

ErrorStatusCause
router_not_found404No router with that id exists in the organization.
router_enabled409A router is deleted while it is enabled. Disable it first.
has_dependent_aliases409A router is deleted while it has aliases.
policy_managed409The router was created by a tools policy and is changed through the policy.
version_conflict412The If-Match ETag is stale. The response carries the current router.
insufficient_scope403The API key lacks the router scope the endpoint requires.
Router SettingsOverview
Was this helpful?