API Access
Router Access
Limiting an API key's inference requests to specific routers and aliases.
Router access limits which routers an API key can send inference requests to. A key set to Any router reaches every router in the organization; a key set to Specific routers reaches only the routers and aliases in its list. A limited key suits an application with one job, such as a support bot, because a leaked key then reaches only the routers that application uses, with the models, prompts and budgets those routers carry.
Setting the list
In the Access editor, the Inference row has three choices: None, Any router and Specific routers. Specific routers shows the key's list with Add router, which opens a search of routers by name or id, and the list can hold routers and aliases. A list holds at least one entry and at most 100. A router list works together with the inference scope, so a key with full control reaches every router; to limit a key's routers, set it to Scoped first.
How requests are matched
A request is allowed when the name it uses, or the router that name leads to, is in the key's list. This makes aliases work in both directions:
| List contains | Request names | Result |
|---|---|---|
The alias production | production | Allowed. When the alias is repointed, the key follows it to the new router. |
The router rt_9Hk3Ws7PzQ | An alias that points to rt_9Hk3Ws7PzQ | Allowed, because the alias leads to a router in the list. |
The router rt_9Hk3Ws7PzQ | Another router, rt_2Lw6Yd8NcV | Refused. |
| Any entry | A model name with no router, such as anthropic/claude-sonnet-4.5 or claude-sonnet-4-5 | Refused. A limited key reaches models through its routers, and the Access editor notes that direct model access is off for the key. |
For a fallback or weighted router, the list names the router itself, and the key then reaches every member through it. When an alias is repointed, the Aliases panel notes that keys limited to the alias follow it to its new router. See Alias.
Refusals
A limited key that names a router outside its list receives the same response as for a router that does not exist, which keeps the organization's other routers private. On Chat Completions the response is:
The other endpoints use their own format with the same meaning:
| Endpoint | Status | Response |
|---|---|---|
POST /v1/messages | 404 | Anthropic format, type not_found_error, message the requested model or router was not found |
| Claude Proxy Bedrock and Vertex endpoints | 404 | Claude Proxy not found |
On Chat Completions and Messages, a disabled or missing router also returns this 404 to a limited key. A Claude Proxy, Codex Proxy or Gemini Proxy in the key's list that has been disabled returns 403 with this Claude Proxy is disabled, this Codex Proxy is disabled or this Gemini Proxy is disabled.
What router access covers
Router access applies to inference requests. Managing routers through the API follows the key's control plane scopes, so a key with routers:read lists every router in the organization whatever its router list. See Scope.