Unverified50% confidenceFactExact time
The virtual model feature supports centralized management of model strings and configurations, instant switching to new models, and enforcement of Zero Data Retention.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/2/2026
First Seen
Valid until: 1/31/2027
Sources
Related Entities
Related Claims
UnverifiedVirtual 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.77% 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% 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.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.69% similarUnverifiedWith virtual models, switching models requires no changes to business code—only the mapping relationship needs to be adjusted at the gateway level.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1125848API
curl https://kongchang.com/api/v1/knowledge/claims/1125848MCP
get_claim(id=1125848)