Unverified50% confidenceSolutionExact time
For virtual models carrying production traffic, it is recommended to first create a candidate virtual model pointing to the new model and switch only after evaluation is complete; if quality drops, the original virtual model can be pointed back to the old model to roll back.
1
Sources
50%
Confidence
Long-term
Relevance
10/28/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOn the Virtual Models page, click Create Virtual Model, fill in the slug, select the underlying model, configure the required settings, and save to create a virtual model; it can also be created via the Vercel CLI command `vercel ai-gateway virtual-models create`.71% similarUnverifiedGateway-level settings on a virtual model such as fallback, Zero Data Retention and tags switch along with the virtual model, but provider-specific options take effect per provider, so provider options need to be rechecked when switching providers.71% similarUnverifiedVirtual models can specify which providers to use, configure fallback models, and enforce compliance requirements such as zero data retention (ZDR), so that compliance policies are enforced uniformly at the gateway layer rather than relying on each caller.70% similarUnverifiedThe cost of virtual models is one extra hop of indirection; the benefits are decoupling configuration changes from code releases, enforceable compliance policies, and clearer spending attribution; for teams with a single application calling a single model, the benefits are limited.70% similarUnverifiedRunning a virtual machine inside another virtual machine is called Nested Virtualization.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1109940API
curl https://kongchang.com/api/v1/knowledge/claims/1109940MCP
get_claim(id=1109940)