Unverified50% confidenceFactExact time
Virtual 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.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/28/2026
First Seen
Valid until: 1/26/2027
Sources
Related Entities
Related Claims
UnverifiedGateway-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.78% similarUnverifiedIf a virtual model requires Zero Data Retention or disallowPromptTraining, these security policies remain enforced even if the request explicitly sets them to false.76% similarUnverifiedSettings on a virtual model take precedence over settings of the same name in a request, and callers cannot override the provider order, fallback or service tier set by the virtual model.72% similarUnverifiedFor 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.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.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1109950API
curl https://kongchang.com/api/v1/knowledge/claims/1109950MCP
get_claim(id=1109950)