Routing rules now available on AI Gateway
AI Gateway now supports routing rules that let you control which models your team can use at the gateway level without code changes. You can create rewrite rules to transparently swap models or deny rules to block specific models, allowing instant rerouting when models go down or get retired.
now supports .Vercel AI Gatewayrouting rules
Routing rules are firewall-style rules that control which models your team can use, applied at the gateway level instead of in your application code.
When a model goes down or gets retired, you usually have to ship a code change to move off it. With routing rules, you push one rule and every request reroutes instantly. There are two types:
Rules apply to every request made with your team's AI Gateway credentials. You manage them with the .Vercel CLI
Create a rewrite with a source and a destination model. The Gateway swaps in the destination transparently, so your application keeps requesting the source model:
Create a deny rule to block a model. Requests for it return a :403
Rules only change which model serves a request. Everything else you’ve configured still applies to the destination model, including:
Routing rules are in beta. For more information, read the .routing rules docs
Type | What it does | Use it to |
Rewrite | Serves a request for one model using another | Keep traffic flowing when a model is unavailable, migrate off a retired model, standardize on one model, or route an expensive model to a cheaper one |
Deny | Blocks requests for a model | Keep your team off models you haven’t approved |
Rewrite
Deny
: , , , the , and . Request-levelBYOKmodel fallbackssortingfilterprovider options
only: and the .Team-levelZero Data Retentionprovider allowlist
Source: original entry ↗