// AI Platform Drift

AI Gateway adds model aliases for pool-based routing

Cloudflare developer changelog · published 2026-11-11 05:28 UTC
WORTH KNOWING VERIFY_ONLY API
WHAT CHANGEDCloudflare AI Gateway now supports model aliases, which are named pools of models (e.g., custom/support-fast) that route requests across multiple models using fallback or smart routing. Applications call the alias name instead of a specific model. Aliases are created on a gateway's Routing page and are scoped per gateway. REST API calls use the alias as the model parameter and require a cf-aig-gateway-id header to select the gateway.
WHY IT MATTERSApplications can change underlying models or routing algorithms without code changes or redeployment. If a model in the pool fails, requests automatically fall back to the next model in the configured order, reducing downtime from individual model failures.
WHAT TO DOReview your AI Gateway configurations to determine whether model aliases would reduce deployment friction for model changes. If you currently hard-code model identifiers in application code, evaluate creating aliases for frequently-changed or failure-prone model selections.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## AI Gateway - Route across a pool of models with model aliases
+https://developers.cloudflare.com/changelog/post/2026-11-04-model-aliases/
+Wed, 04 Nov 2026 00:00:00 GMT
+
+AI Gateway now supports model aliases. A model alias is a pool of models that your application calls by one name, such as custom/support-fast. AI Gateway tries the models in the order you set and falls back to the next one if a request fails, or uses smart routing to choose a model for each request.
+Because your application only references the alias, you can swap models or change the routing algorithm on your gateway without redeploying. Create and manage aliases on your gateway's Routing page, alongside dynamic routes.
+To call an alias through the REST API, use its name as the model. For example, send this body to /accounts/{account_id}/ai/run:
+{
+"model": "custom/support-fast",
+"input": {
+"messages": [{ "role": "user", "content": "Reply with a short greeting." }]
+}
+}
+Include the cf-aig-gateway-id header to select the gateway where you created the alias. Aliases are scoped to individual gateways.
+For setup instructions and routing options, refer to Model aliases.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew AI Gateway feature with API integration points and deployment implications for teams building on Cloudflare AI.
signalsnew feature: model aliases for AI Gateway · new API capability: routing across model pools · new API parameter: model name now accepts alias identifiers · new required header: cf-aig-gateway-id for alias selection · deployment impact: enables model swapping without redeployment · integration change: REST API body structure now supports alias routing
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)