Vercel AI Gateway now supports routing rules in beta. These are firewall-style controls that determine which AI models your team can call, enforced at the gateway level. Two rule types exist: rewrites, which transparently swap a requested model for a different one, and deny rules, which block a model outright and return a 403.
The operational case is direct. When a model is retired or goes down, the current fix is a code change and a deploy. With a rewrite rule, one CLI command reroutes every in-flight request instantly, with no application changes. Deny rules let teams enforce model governance without relying on application-level guardrails. Both rule types apply to all requests made with a team's AI Gateway credentials.
What makes the full docs worth reading: routing rules compose with existing gateway configuration. BYOK, model fallbacks, provider filtering, Zero Data Retention, and provider allowlists all continue to apply to the destination model after a rewrite. The rule changes the model. Nothing else moves.
[READ ORIGINAL →]