Unverified50% confidenceSolutionExact time
With virtual models, switching models requires no changes to business code—only the mapping relationship needs to be adjusted at the gateway level.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/2/2026
First Seen
Valid until: 1/31/2027
Sources
Related Entities
Related Claims
UnverifiedA virtual model ID is similar to a service-name abstraction in a gateway: the caller depends only on a stable logical identifier, while the real backend (specific model, provider, version) is mapped and switched on the gateway side.69% similarUnverifiedThe virtual model feature supports centralized management of model strings and configurations, instant switching to new models, and enforcement of Zero Data Retention.68% 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.67% 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.67% 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.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1125851API
curl https://kongchang.com/api/v1/knowledge/claims/1125851MCP
get_claim(id=1125851)