Routing rules now available on AI Gateway

Vercel AI Gateway now supports routing 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.

Link to headingRewrite

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:

vercel ai-gateway rules add --type rewrite \
  --source anthropic/claude-opus-4.8 \
  --destination anthropic/claude-haiku-4.5

Link to headingDeny

Create a deny rule to block a model. Requests for it return a 403:

vercel ai-gateway rules add --type deny --source openai/gpt-5.5

Rules only change which model serves a request. Everything else you’ve configured still applies to the destination model, including:

• Request-level: BYOK, model fallbacks, sorting, the only filter, and provider options.

• Team-level: Zero Data Retention and the provider allowlist.

Routing rules are in beta. For more information, read the routing rules docs.