Unverified50% confidenceOpinionExact time
A 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.
1
Sources
50%
Confidence
Long-term
Relevance
11/2/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen using a virtual model, simply replace the original provider model ID with `vmc/<slug>` (such as `vmc/coding-agent`) in AI SDK or compatible API requests to invoke it.76% similarUnverifiedKissinger believes VMware's abstraction model needs to be rebuilt for the agent era, proposing "vMotion for agents," meaning agents need migration, pause, snapshot, and resume capabilities similar to virtual machines, and the virtualization layer needs to expand from abstracting machines to abstracting agent workloads.69% similarUnverifiedWith virtual models, switching models requires no changes to business code—only the mapping relationship needs to be adjusted at the gateway level.69% 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.68% similarUnverifiedIn gateway mode, the client sends only a virtual label (such as cuepreem-cloud-fast), and the gateway decides which real model it corresponds to, so all logic related to a specific model must be placed in the gateway.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1125854API
curl https://kongchang.com/api/v1/knowledge/claims/1125854MCP
get_claim(id=1125854)