canonical: https://jentic.com/apis/googleapis.com/rapid-migration-assessment

# Google Rapid Migration Assessment API

The Google Cloud Rapid Migration Assessment API drives the Migration Center collector workflow used to inventory on-premises and other-cloud workloads ahead of a Google Cloud migration. It exposes operations to register collectors, pause and resume their data collection, attach annotations, and manage the long-running operations that back collector lifecycle changes. Output from this API feeds Migration Center cost and fit analyses and the recommended landing-zone shape for Google Cloud.

## For AI agents

Provision and operate Google Cloud Migration Center collectors that inventory on-premises workloads, including registration, pause, resume, and annotation management.

## Scope

Does not perform actual VM, storage, or database migration to Google Cloud - use only to drive Migration Center collector lifecycle and annotations during the assessment phase.

## Capabilities

- Register a Migration Center collector tied to a Google Cloud project and region
- Pause and resume collector data collection without losing previously collected inventory
- Attach annotations to collectors to track ownership, environment, or migration wave
- Cancel and inspect long-running operations associated with collector lifecycle changes
- List collectors and their operations across a project to monitor assessment coverage
- Drive collector workflows from CI or infrastructure-as-code rather than the console

## Use cases

### Pre-Migration Inventory

Stand up Migration Center collectors against on-premises or other-cloud environments to inventory VMs, applications, and dependencies ahead of moving to Google Cloud. The API drives collector registration and lifecycle so the inventory work can be scripted alongside the rest of the landing zone bootstrap.

Example prompt: Register a collector in projects/p/locations/us-central1 named onprem-dc-east, wait for the operation to complete, then attach annotation environment=production.

### Wave-Based Migration Tracking

Large migrations are sequenced into waves, each covering a subset of workloads. Annotations on Migration Center collectors track which wave a collector belongs to so migration program managers can correlate inventory data with their wave plan and report progress.

Example prompt: List all collectors, then annotate each with the wave identifier from the migration plan spreadsheet via the annotations resource.

### Maintenance and Pause Windows

When source environments are under maintenance or going through firewall changes, collectors should be paused so they do not raise spurious connectivity errors. The API exposes pause and resume operations so this can be scripted around change windows.

Example prompt: Pause collector projects/p/locations/us-central1/collectors/onprem-dc-east before a 2-hour change window, then resume it once the change ticket is closed.

### Agent-Driven Migration Bootstrap

An infrastructure agent uses Jentic to register collectors, attach annotations, and monitor long-running operations as part of an automated landing-zone bootstrap, replacing manual console clicks during the discovery phase of a Google Cloud migration.

Example prompt: Search Jentic for register a migration center collector, load the schema, and execute it with the project, region, and collector name from the migration plan.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/{+name}:register | Register a Migration Center collector |
| POST | /v1/{+name}:pause | Pause a collector's data collection |
| POST | /v1/{+name}:resume | Resume a paused collector |
| POST | /v1/{+name}:cancel | Cancel a long-running collector operation |
| GET | /v1/{+name}/operations | List long-running operations under a parent |
| GET | /v1/{+parent}/collectors | List collectors in a parent location |

## Key resources

- **collectors** — Migration Center collectors with register, pause, resume, and lifecycle operations
- **annotations** — Free-form annotations attached to collectors for tagging and grouping
- **operations** — Long-running operations spawned by collector lifecycle changes
- **locations** — Regional locations where collectors and operations live

## Why Jentic

- **Setup:** Wiring the Rapid Migration Assessment API by hand means configuring Google OAuth 2.0 with the cloud-platform scope, refreshing scoped access tokens, and tracking collector resource names across the long-running operations on rapidmigrationassessment.googleapis.com. Through Jentic you install once, import the Rapid Migration Assessment API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** This API puts the collector in the URL path (/v1/{+name}), so a rule can pin your agent to one collector: it can register and list within that scope and nothing else. You choose the operations it may call, so state-changing ones like pausing or cancelling a collector are not included unless you add them.
- **Credential handling:** Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a Migration Center collector' or 'list assessment operations', and Jentic returns the matching Rapid Migration Assessment operation with its input schema so the agent calls the right endpoint without reading the discovery doc.

## Related APIs

- **Compute Engine API** — Provisions the target VMs that workloads land on after migration
- **Identity and Access Management API** — Grants service accounts permission to operate Migration Center collectors
- **Cloud Storage API** — Stores assessment artefacts, exports, and migration plan documents

## FAQ

### What authentication does the Rapid Migration Assessment API use?

The API uses Google OAuth 2.0 with the cloud-platform scope, sent as a Bearer token. Through Jentic the OAuth credentials are stored encrypted in the vault and short-lived access tokens are minted per call, so the refresh token never enters the agent context.

### Does this API perform the actual workload migration?

No, it manages the assessment phase by driving Migration Center collectors that inventory source environments. The actual move of VMs and data is performed by Migrate to Virtual Machines, Storage Transfer Service, or Database Migration Service depending on the workload type.

### What are the rate limits for the Rapid Migration Assessment API?

Quotas follow standard Google Cloud project conventions and are documented in the Migration Center quotas page. The API surface is small and most calls are control-plane operations, so quota is rarely the bottleneck - long-running operation latency is the more common consideration.

### How do I register a collector through Jentic?

Search Jentic for register a migration center collector, load the schema for the projects.locations.collectors.register operation which maps to POST /v1/{+name}:register, and execute it with the project, region, and collector name. Then poll the returned operation until it completes.

### Is the Rapid Migration Assessment API free?

Migration Center is free to use for assessment workloads at the time of writing; pricing for advanced features is published on the Google Cloud Migration Center pricing page. The collector software you install on premises is also free.

### How do I pause a collector during a change window?

Call POST /v1/{+name}:pause with the full collector resource name to suspend data collection without unregistering, then POST /v1/{+name}:resume after the change is complete. Inventory collected before the pause is preserved.

### Can I limit what my agent is allowed to do with the Rapid Migration Assessment API?

Yes. Jentic One runs self-hosted, so your own rules decide which operations and credentials the agent may use. Because this API puts the collector in the URL path (/v1/{+name}), you can pin the agent to a single collector and grant only read-oriented calls like listing collectors and operations while withholding state-changing ones such as register, pause, resume, or cancel. The agent can call an operation only if you have added it to its allowed set, and the Google OAuth credential is injected at execution time rather than exposed to the agent.