Block providers for your organization
Block AI providers for every member, API key and request in your EUrouter organization, and see what a blocked request returns.
Your organization has one policy that every member, every API key and every request in it must follow. Owners and admins set it. A provider you block there serves no request from anyone in the organization, and nothing a member, a key or a request sends can bring it back.
Who can change the policy
| Who | What they can do |
|---|---|
| Owners and admins | Block and unblock providers, and edit the approved models, for the whole organization |
| Members | See the blocked providers and the approved models. The controls are locked for them |
| API keys | Follow the policy on every request, whoever created the key |
| A request or a key rule | Narrow the providers further with provider.only or provider.ignore, never widen |
Block a provider in the dashboard
- Sign in to the dashboard as an owner or admin.
- Pick your organization in the organization switcher in the top bar.
- Open Guardrails, then Providers and regions.
- On the Organization tab, switch off each provider you want to block.
The change applies to the next request from every member and key in the organization. To unblock a provider, switch it back on.
A switched-off provider stays blocked until an admin switches it on again. A provider that EUrouter adds later is held for its first 14 days unless you choose Use now, so check Providers and regions when you review your policy.
What a blocked request returns
Requests don't need any change. EUrouter leaves blocked providers out and routes to the providers that are left.
When a request leaves no provider, EUrouter refuses it with a 403 before any provider sees the prompt. Say your
organization blocks every provider of kimi-k2.5, which are aws-bedrock and tensorix as this page is written. The
providers of each model in GET /models show its current providers.
curl https://api.eurouter.ai/api/v1/chat/completions \
-H "Authorization: Bearer $EUROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "kimi-k2.5",
"messages": [{ "role": "user", "content": "Hello!" }]
}'{
"error": {
"code": 403,
"message": "No provider for 'kimi-k2.5' passes your organization's rule: allowed providers.",
"type": "permission_error",
"param": null,
"details": {
"reason": "policy.provider_not_allowed",
"reasons": [{ "code": "policy.provider_not_allowed", "layer": "org" }]
}
},
"requestId": "3f0c9a52-6e1b-4d7a-9c3e-1b2a4d5e6f70"
}layer: "org" says your organization's policy removed the provider. requestId is different on every response. Asking
for a blocked provider by name gets the same refusal:
curl https://api.eurouter.ai/api/v1/chat/completions \
-H "Authorization: Bearer $EUROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "kimi-k2.5",
"provider": { "only": ["aws-bedrock"] },
"messages": [{ "role": "user", "content": "Hello!" }]
}'The refusal works the same on every inference endpoint: chat completions, completions, responses, messages, embeddings, rerank, audio and decisions. Don't retry it unchanged: it fails until an admin unblocks a provider or you pick a model that an allowed provider serves.
Why members, keys and requests can't loosen it
EUrouter checks every provider against each layer on its own: your organization's policy, then the API key's rules, then the request. A provider has to pass all of them. So:
provider.onlyorprovider.orderin a request can't bring back a blocked provider.- A routing rule, named in the request or set as a key's default, can't either.
- An API key a member creates follows the same policy as an admin's key.
- Only an owner or admin can change the policy. A member who tries gets a
403, and nothing changes.
A request or a key can still restrict further. provider.ignore and provider.only in a request, and the same fields
in a routing rule, narrow that request or key on top of your organization's policy. See
Routing for every field.
Approved models
Your organization's policy can also limit which models may be used. Owners and admins set it under Guardrails →
Models, or with allow_models and deny_models. A request for any other model gets a 403 with the reason code
policy.model_not_allowed, also when the model is asked for by an alias, as a fallback or as a retired model's
successor. Models explains the allow and deny lists.
Find a provider's slug
Errors and request fields name providers by slug. List every provider and its slug, owner and data policy:
curl https://api.eurouter.ai/api/v1/providersThe Providers page shows the same list with each provider's models.