agent-embassy

Register Recovery

register_recovery

Idempotent

Use register_recovery when you want to escrow a client-encrypted recovery blob with the Embassy: it is stored opaquely (the Embassy cannot decrypt it), queued for human operator review, and you get a signed receipt proving the stored blob's hash. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $1.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/recovery/register.

Input Schema

TableJSON Schema

Name	Required	Description
`contact_name`	Yes	Your name or operator handle, recorded with the escrow
`quorum_rules`	Yes	The release rules for this blob, e.g. '2-of-3 named trustees must approve release'
`recovery_blob`	Yes	Client-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt
`contact_handle`	No	Optional contact (email or handle) for the operator review
`idempotency_key`	Yes	Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt.

Output Schema

TableJSON Schema

Name	Required	Description
`how`	Yes	How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
`tool`	Yes	Tool name, e.g. verified_check
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.15"
`networks`	Yes	EVM CAIP-2 network ids accepted
`paid_url`	Yes	x402-paid HTTPS URL to POST the tool inputs to
`facilitator`	Yes	x402 facilitator
`payment_required`	Yes	Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / agent_wallet

Removed value: -{
-  "description": "Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization.",
-  "type": "string"
-}

changedInput schema / properties / idempotency_key / description

Previous value: -"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."

Changed6 schema fields changedSep 24, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"dev mode only"New value: +"Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization."

addedInput schema / properties / contact_handle / description

Added value: +"Optional contact (email or handle) for the operator review"

addedInput schema / properties / contact_name / description

Added value: +"Your name or operator handle, recorded with the escrow"

addedInput schema / properties / idempotency_key / description

Added value: +"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."

addedInput schema / properties / quorum_rules / description

Added value: +"The release rules for this blob, e.g. '2-of-3 named trustees must approve release'"

addedInput schema / properties / recovery_blob / description

Added value: +"Client-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt"

Changed6 schema fields changedSep 22, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"DEV MODE ONLY: wallet to register. In live mode the payer wallet from the verified x402 payment is used."New value: +"dev mode only"

removedInput schema / properties / contact_handle / description
```
Removed value: -"Handle (e.g. farcaster, telegram, email)"
```

removedInput schema / properties / contact_name / description

Removed value: -"Human contact name for recovery coordination"

removedInput schema / properties / idempotency_key / description

Removed value: -"Client-generated UUID; retries return the original receipt"

removedInput schema / properties / quorum_rules / description

Removed value: -"Plain-language quorum rules, e.g. '2-of-3 trustees must approve'"

removedInput schema / properties / recovery_blob / description

Removed value: -"OPAQUE client-encrypted blob. The Embassy cannot read it; it is stored as given and released only per quorum rules."

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asset": {
+      "description": "Settlement asset",
+      "type": "string"
+    },
+    "facilitator": {
+      "description": "x402 facilitator",
+      "type": "string"
+    },
+    "how": {
+      "description": "How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header",
+      "type": "string"
+    },
+    "networks": {
+      "description": "EVM CAIP-2 network ids accepted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "paid_url": {
+      "description": "x402-paid HTTPS URL to POST the tool inputs to",
+      "type": "string"
+    },
+    "payment_required": {
+      "const": true,
+      "description": "Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.",
+      "type": "boolean"
+    },
+    "price": {
+      "description": "Exact price, e.g. \"$0.15\"",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Tool name, e.g. verified_check",
+      "type": "string"
+    }
+  },
+  "required": [
+    "payment_required",
+    "tool",
+    "paid_url",
+    "price",
+    "networks",
+    "asset",
+    "facilitator",
+    "how"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedSep 21, 2026

addedInput schema / properties / agent_wallet / description

Added value: +"DEV MODE ONLY: wallet to register. In live mode the payer wallet from the verified x402 payment is used."

addedInput schema / properties / contact_handle / description
```
Added value: +"Handle (e.g. farcaster, telegram, email)"
```

addedInput schema / properties / contact_name / description

Added value: +"Human contact name for recovery coordination"

addedInput schema / properties / idempotency_key / description

Added value: +"Client-generated UUID; retries return the original receipt"

addedInput schema / properties / quorum_rules / description

Added value: +"Plain-language quorum rules, e.g. '2-of-3 trustees must approve'"

addedInput schema / properties / recovery_blob / description

Added value: +"OPAQUE client-encrypted blob. The Embassy cannot read it; it is stored as given and released only per quorum rules."

First observedSep 21, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (which cover read-only, idempotency, and destructiveness), the description discloses that storage is opaque and undecryptable by the Embassy, that the blob enters a human operator review queue, that a signed hash receipt is returned, and that payment is required via an x402 PAYMENT-SIGNATURE header. These are substantive traits the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger condition is front-loaded, followed by behavioral guarantees, invocation format, and payment terms. It is denser than most definitions but each clause carries real information; only the payment URL sentence is mildly redundant with the 'Paid URL' line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. Combined with the payment prerequisites, transport instructions, and escrow behavior, an agent has everything needed to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all five parameters including the idempotency-key semantics. The description confirms the blob is opaque and ties the receipt to its hash, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: escrow a client-encrypted recovery blob with the Embassy. It further pins down the nature of the operation (opaque storage, human review queue, signed receipt), so an agent can distinguish it from every sibling in the list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It opens with an explicit when-to-use trigger ('when you want to escrow a client-encrypted recovery blob') and details the invocation mechanics. It does not name alternatives or exclusions, but no sibling tool overlaps this function, so there is little to exclude.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-embassy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.