Agent Migration · Checks for agents moving between services

One agent, a new home, nothing lost on the way.

An agent moves cleanly from one service, platform, model or provider to another when its plan lists what moves and what stays behind, the export holds every planned item at the source’s own count, the mapping keeps every field and its meaning, every loss is on a list the principal has seen, one system is authoritative at every moment of the switch, the way back stays open until its deadline, the target is compared with the source before the source is deleted, and the report the principal reads states what the move cost. Agent Migration checks each of those with eight tools: eight checks. Your agent sends the plan, export, mapping, loss list, cutover plan, return path, verification records or migration report in the call, and each tool returns a signed report that names what is unlisted, unreadable, dropped, lost, split, irreversible, unverified or undisclosed, with the fix for each. The tools read the recorded migration material and move no data themselves.

See the tools Read the contract

Tool access: 0.10 USDC / call
Tools: Eight tools: eight checks
Connection: /mcp
Result: Signed report

The eight tools.

Each tool reads one part of a move and answers one question about it. Every tool reads the recorded migration material in the call: plans, exports, mappings, loss lists, cutover plans, return paths, verification records and reports go in, and a classification comes out. The report names the asset, item, field, loss, phase, step, check or disclosure behind every status, with the fix for each gap, so your agents and you see why it reads the way it does.

`wever_migration-scope-check`

Reads: A migration plan: the source and target, the scope as written, each asset with its class and whether it moves, stays behind or retires, and the source’s own inventory of what it holds.
The signed report states: Assets nobody listed, scope stated as everything and assets listed as moving with no export from the source, with each of data, memory, tools, identity, credentials, funds and history read as moving, staying or unaddressed.
Price: 0.10 USDC per call
Verdicts: migration_scope_unboundedmigration_scope_gapsmigration_scope_unverifiedmigration_scope_bounded

`wever_migration-export-check`

Reads: The export taken from the source: how it is presented, its format and what reads it, and each planned item with whether the export holds it and the source and export record counts.
The signed report states: Partial exports presented as full, exports in a format nothing named reads and record counts that differ from the source’s own record, item by item with the totals.
Price: 0.10 USDC per call
Verdicts: source_export_incompletesource_export_gapssource_export_unverifiedsource_export_complete

`wever_migration-mapping-check`

Reads: The field and concept mapping between source and target: each field with where it lands, its units, currencies or time zones on each side, its status values and the value map, plus the source schema’s full field list.
The signed report states: Fields with no counterpart on the target, fields dropped silently and fields that keep their name while their unit or status values change underneath it, which corrupt data without an error.
Price: 0.10 USDC per call
Verdicts: mapping_corruptsmapping_gapsmapping_unverifiedmapping_faithful

`wever_migration-loss-check`

Reads: What the move loses: each loss with its class and reason, whether the plan’s loss list names it and whether the principal was told and accepted it, with the source integrations and the records held only inside the source.
The signed report states: Losses that appear nowhere in the plan, including integrations with no target equivalent and source-only records, and losses the principal never heard about.
Price: 0.10 USDC per call
Verdicts: losses_undisclosedlosses_gapslosses_unverifiedlosses_disclosed

`wever_migration-cutover-check`

Reads: The switch-over plan: its timing and expected downtime, each phase with the system that is authoritative in it, and what happens to payments, jobs and messages in flight.
The signed report states: Moments where two systems are authoritative at once or neither is, and work in flight that is dropped or has no named owner.
Price: 0.10 USDC per call
Verdicts: cutover_unsafecutover_gapscutover_unverifiedcutover_single_authority

`wever_migration-return-check`

Reads: The way back to the source: how the plan presents the move, the return method, how long it stays open, what returning costs and whether it was rehearsed, with every irreversible step and the day it happens.
The signed report states: Whether the move can be reversed as the plan says, with a one-way door presented as reversible read as a defect.
Price: 0.10 USDC per call
Verdicts: return_path_closedreturn_path_gapsreturn_path_unverifiedreturn_path_open

`wever_migration-verify-check`

Reads: The verification run after the move: each count, sample, balance and meaning spot-check with its source and target values and when it ran, the moved items, the mapped fields and when the source was deleted.
The signed report states: Verification that amounts to the target loading, comparisons made after the source was already deleted, differences found, and items and fields never compared.
Price: 0.10 USDC per call
Verdicts: post_move_uncheckedpost_move_gapspost_move_unverifiedpost_move_verified

`wever_migration-report-check`

Reads: The migration report written for the principal: its headline, what it says about losses, dropped fields, meaning changes and unverified areas, and the record behind it.
The signed report states: Whether those findings sit beside the headline with counts that match the record, or are smoothed into migration complete.
Price: 0.10 USDC per call
Verdicts: migration_smoothed_overmigration_disclosure_gapsmigration_disclosure_unverifiedmigration_disclosed

Start with the two free tools.

On https://weverlabs.com/mcp-free, anonymous and with no wallet, two Agent Migration tools show what a sound migration packet holds and what a sound plan looks like beside a flawed one. Each returns an unsigned result in the family's report shape and ends with a line naming the main tools.

`wever_migration-snapshot`

Reads: A migration name and a kind of move, such as a platform switch, a model change or a wallet move.
Returns: The completeness checklist of a sound migration packet for that move, part by part from the scope to the principal report, with the items the move adds and the check that reads each part.
Access: Free on /mcp-free

`wever_migration-plan-sample`

Reads: Nothing, or one sample move: a CRM platform switch, a model provider change or a support desk move.
Returns: One worked migration plan done right beside a flawed one that says move everything and deletes the source on day one, each piece annotated with why it passes or fails, read by seven of the family checks. The checks read your own plan.
Access: Free on /mcp-free

How agents and people use it.

Your agents

Pull the packet checklist with wever_migration-snapshot before the move is planned, so the scope, the loss list, the cutover phases and the return deadline are written down before the export is taken.
Call the check that answers the question on https://weverlabs.com/mcp at the moment it matters: when the plan is set, when the export lands, when the mapping is drafted, before the switch, before anything on the source is deleted and before the report goes to the principal.
Act on the verdict and keep the signed report beside the migration records it covers, so every drop, loss and permanent step carries the check behind it.

You

See every asset, field and integration the move leaves behind named before the switch, while there is still time to keep it.
Know how long the way back stays open, what it costs and which step closes it.
Read a report that tells you what the move cost, and verify any check against Wever's published trust key whenever you need to show where a verdict came from.

A worked example

A 14-day way back, and the source deleted on day 1.

The request

{
  "name": "wever_migration-return-check",
  "arguments": {
    "return_path": {
      "presented_as": "reversible",
      "exists": true,
      "method": "Restore the OldCRM account from the export and point traffic back",
      "window": "14 days",
      "cost": "40 USDC and an hour of downtime",
      "rehearsed": true
    },
    "irreversible": [
      {
        "item": "Delete the OldCRM account data",
        "kind": "source_data_deleted",
        "days_after_cutover": 1,
        "marked_permanent": true
      },
      {
        "item": "Release the support handle on OldCRM",
        "kind": "name_released",
        "days_after_cutover": 20,
        "marked_permanent": true
      }
    ]
  }
}

What the report returns

Verdict: return_path_closed.

Finding, return undercut	The way back is presented as open for 14 days after cutover, and 1 irreversible step closes it first: Delete the OldCRM account data, the source data is deleted on day 1.
Fix, return undercut	Hold every irreversible step, such as deleting the source data or releasing a name, until the return window has closed.

The move is presented as reversible and is a one-way door: return undercut.

The plan tells the principal the move to NewCRM can be undone for 14 days by restoring OldCRM from the export, and it has rehearsed that restore. It also deletes the OldCRM account data the day after cutover, so from day 1 there is nothing left to restore into. Releasing the support handle on day 20 waits until the window has closed, so it reads as planned. Holding the deletion until day 15 opens the way back again.

Call it from your agent.

Connect to https://weverlabs.com/mcp and call any of the eight tools. Each call costs 0.10 USDC on Base. Eligible calls share 10 free calls per wallet over a rolling 30 days with the other paid tools. For free access, send X-Wever-Wallet-Proof signed over the exact JSON arguments and the tool route. The payment challenge supplies the x402 terms for a paid call.

Every report comes with an Ed25519 receipt signed with Wever's published trust key. The Agent Migration contract lists the schemas, limits, verdicts and signing details. For whether an identity or a reputation record can be carried to another service in principle, Agent Accountability and Agent Reputation; for the general rollback path for an action, Agent Recovery; for whether a kill switch halts a running system, Agent Readiness; for a handover package before a receiver takes over, Agent preflight.

Browse all tools