# Routing rules now available on AI Gateway

Source: [Vercel](https://vercel.com/changelog/ai-gateway-routing-rules)  
Feed7 permalink: https://feed7.dev/p/ai-gateway-routing-rules-024ifzc  
Published: Unknown  
Trust: Official Source (official_source)

## Why Included

Vercel AI Gateway adds firewall-style routing rules: rewrite one model to another or deny a model outright, applied at the gateway so you swap models across your whole team without shipping a code change.

## Source Summary

**The gist** AI Gateway now has **routing rules**, managed via the Vercel CLI and applied to every request made with your team's gateway credentials. Two types: **Rewrite** transparently serves one model's requests with another; **Deny** blocks a model and returns a **403**.

## Practical Implication

**Why it matters** When a model is retired or goes down, you push one rule instead of a code deploy and every request reroutes instantly—useful for migrating off dead models, standardizing on one, or steering an expensive model to a cheaper one. Existing config still applies to the destination: **BYOK**, fallbacks, sorting, provider options, **Zero Data Retention**, and the provider allowlist.

## Agent-Ready Context

**The gist** AI Gateway now has **routing rules**, managed via the Vercel CLI and applied to every request made with your team's gateway credentials. Two types: **Rewrite** transparently serves one model's requests with another; **Deny** blocks a model and returns a **403**.

**Why it matters** When a model is retired or goes down, you push one rule instead of a code deploy and every request reroutes instantly—useful for migrating off dead models, standardizing on one, or steering an expensive model to a cheaper one. Existing config still applies to the destination: **BYOK**, fallbacks, sorting, provider options, **Zero Data Retention**, and the provider allowlist.

**Watch out** Routing rules are in **beta** and CLI-managed only. They change only which model serves a request—nothing else—so behavior differences between source and destination models are on you to validate.

## Context Map

- Layer: infra
- Domains: None
- Topics: gateways, model-selection

## Uncertainty

- Routing rules are in **beta** and CLI-managed only. They change only which model serves a request—nothing else—so behavior differences between source and destination models are on you to validate.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.