{"slug": "routing-rules-now-available-on-ai-gateway", "title": "Routing rules now available on AI Gateway", "summary": "Vercel has launched routing rules for its AI Gateway, enabling teams to rewrite or block model requests at the gateway level without code changes. The feature, now in beta, allows instant rerouting when models go down or are retired, and can enforce model usage policies across an entire team.", "body_md": "[Vercel AI Gateway](https://vercel.com/docs/ai-gateway) now supports [routing rules](https://vercel.com/docs/ai-gateway/models-and-providers/routing-rules).\n\nRouting rules are firewall-style rules that control which models your team can use, applied at the gateway level instead of in your application code.\n\nWhen 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:\n\nType | What it does | Use it to |\n| 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 |\n| Blocks requests for a model | Keep your team off models you haven’t approved |\n\nRules apply to every request made with your team's AI Gateway credentials. You manage them with the [Vercel CLI](https://vercel.com/docs/ai-gateway/models-and-providers/routing-rules#manage-rules-with-the-cli).\n\nCreate a rewrite with a source and a destination model. The Gateway swaps in the destination transparently, so your application keeps requesting the source model:\n\nCreate a deny rule to block a model. Requests for it return a `403`\n\n:\n\nRules only change which model serves a request. Everything else you’ve configured still applies to the destination model, including:\n\n**Request-level**: [BYOK], [model fallbacks](https://vercel.com/docs/ai-gateway/models-and-providers/model-fallbacks), [sorting](https://vercel.com/docs/ai-gateway/models-and-providers/provider-filtering-and-ordering), the `only`\n\n[filter](https://vercel.com/docs/ai-gateway/models-and-providers/provider-filtering-and-ordering), and [provider options](https://vercel.com/docs/ai-gateway/models-and-providers/provider-options).\n\n**Team-level**: [Zero Data Retention](https://vercel.com/docs/ai-gateway/security-and-compliance/zdr) and the [provider allowlist](https://vercel.com/docs/ai-gateway/security-and-compliance/provider-allowlist).\n\nRouting rules are in beta. For more information, read the [routing rules docs](https://vercel.com/docs/ai-gateway/models-and-providers/routing-rules).", "url": "https://wpnews.pro/news/routing-rules-now-available-on-ai-gateway", "canonical_source": "https://vercel.com/changelog/ai-gateway-routing-rules", "published_at": "2026-07-02 00:00:00+00:00", "updated_at": "2026-07-03 20:50:52.897421+00:00", "lang": "en", "topics": ["ai-infrastructure", "developer-tools", "ai-products"], "entities": ["Vercel", "Vercel AI Gateway", "Vercel CLI"], "alternates": {"html": "https://wpnews.pro/news/routing-rules-now-available-on-ai-gateway", "markdown": "https://wpnews.pro/news/routing-rules-now-available-on-ai-gateway.md", "text": "https://wpnews.pro/news/routing-rules-now-available-on-ai-gateway.txt", "jsonld": "https://wpnews.pro/news/routing-rules-now-available-on-ai-gateway.jsonld"}}