Google Cloud's VM Migration API is the product that matches this request: it exposes MigratingVm operations to create a migrating VM in a source, start the migration, and get its details 111. None of the other candidates offers a comparable VM migration API; the rest are general cloud, container, database or email platforms that do not show VM migration operations.
- 1
Google Cloud VM Migration APIgoogle.comverified and signed
Google Cloud's VM Migration API creates MigratingVm resources in a source, starts VM migrations with replication cycles, and gets migrating VM details 11.
official:API · VM Migration API
for agents: vmmigration.projects.locations.sources.migratingVms.create · vmmigration.projects.locations.sources.migratingVms.startMigration · vmmigration.projects.locations.sources.migratingVms.get
Sources
- 1AI and Cloud Computing Services | Google Cloudcloud.google.com · read 2026-10-29
- 11VM Migration API: declares "vmmigration.projects.locations.sources.migratingVms.create" (the record we read and signed)unfragile.ai · read 2026-10-24
For agents: the 10 actions behind this answer
vmmigration.projects.locations.sources.migratingVms.create · VM Migration API verified and signed
Creates a new MigratingVm in a given Source.
add-new-jit-ee-api · add-new-jit-ee-api verified and signed
Add a new API to the JIT-VM (aka JIT-EE) interface in the codebase.
docker-sandboxes-lifecycle · docker-sandboxes-lifecycle verified and signed
Use this skill when creating, running, reattaching to, listing, stopping, or removing Docker Sandboxes (the standalone `sbx` CLI that runs AI coding agents in isolated microVMs), even if the user just says they want to "run claude in a sandbox", "isolate an agent from my repo", "give an agent its ow
vitest · vitest verified and signed
Vitest API and config reference (Jest-compatible) — mocking with vi.*, spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering. Use for Vitest API and configuration questions anywhere in the monorepo; for Studio-specific test strategy and component-test setup, start with
issue-fields-migration · issue-fields-migration verified and signed
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values
vss-manage-video-io-storage · vss-manage-video-io-storage verified and signed
Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add/delete sensors and streams). Not for VLM inference or search.
PUT /api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName} · VSOnline verified and signed
PUT /api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName}
API · python-http-client verified and signed
databricks-serverless-migration · databricks-serverless-migration verified and signed
Migrate Databricks workloads from classic compute to serverless compute. Use when migrating notebooks, jobs, pipelines, or Scala JARs (`spark_jar_task`) from classic clusters to serverless, checking if existing code is serverless-compatible, or writing new serverless-compatible code. Provides concre
qdrant-model-migration · qdrant-model-migration verified and signed
Guides embedding model migration in Qdrant without downtime. Use when someone asks 'how to switch embedding models', 'how to migrate vectors', 'how to update to a new model', 'zero-downtime model change', 'how to re-embed my data', or 'can I use two models at once'. Also use when upgrading model dim
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.