# Agent Embassy — Encrypted Recovery Registration

> Agent Embassy — Encrypted Recovery Registration is a paid API for AI agents from agent-embassy.fly.dev, paid per call via x402, $1/call, status unknown (last checked 2026-10-10).

Registers an AI agent's encrypted recovery blob with quorum-based release rules for $1 USDC, returning a signed Outcome Receipt as proof of storage

## Facts

- Endpoint: POST https://agent-embassy.fly.dev/v1/recovery/register?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-embassy-encrypted-recovery-registration-94b7618a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KVbmzo_E54h-hyW6flH1R

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-embassy-encrypted-recovery-registration-94b7618a -d '<json body>'
```

Example prompt: Register my agent's encrypted recovery blob with Agent Embassy using quorum rules '2-of-3 trustees must approve', contact name 'Alice Chen', Farcaster handle '@alicechen', and this opaque encrypted payload: 'eyJlbmMiOiJBMjU2R0NNIn0...'

## When to prefer this

Choose this endpoint when an AI agent needs tamper-evident, quorum-gated storage for sensitive encrypted state (wallet seeds, API keys, recovery credentials) and requires a signed Outcome Receipt as machine-verifiable proof of registration. It is specifically designed for autonomous agent workflows where a human or multi-party trustee group must later approve release. Prefer this over generic secret stores when you need (1) USDC micropayment-gated access, (2) plain-language quorum rules, (3) cryptographic receipts compatible with the x402 agent commerce stack, and (4) the Embassy's liability boundary guarantees.

## Known failure modes

- Payment not verified — x402 payment of $1 USDC on Base or Arbitrum One must be confirmed before registration proceeds
- Missing required fields — agent_wallet (dev mode), contact_name, quorum_rules, recovery_blob, or contact_handle absent returns a 4xx error
- Invalid or malformed encrypted blob — blob must be an opaque string; embedding plaintext secrets may cause rejection
- Duplicate idempotency key with differing payload — returns original receipt rather than creating a new record
- Network or chain congestion — x402 payment confirmation may time out on Base or Arbitrum One
- Fly.dev cold start — first request may experience elevated latency

## How this service works

Agent Embassy lets AI agents pay for work and prove what happened. $0.15 verified web checks with signed Outcome Receipts, $1.00 encrypted recovery registration, paid compute market data. USDC on Base and Arbitrum One via x402 v2.

## Output

A JSON Outcome Receipt containing the tool name ('register_recovery'), a chain of accountability stages (request, authorization, action, proof, liability_boundary), registration status ('received'), the payer's account address, a unique receipt ID (emb_*), and the receipt version string. The receipt is signed and machine-verifiable, serving as cryptographic proof that the encrypted blob was accepted for storage under the specified quorum rules.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "agent_wallet": {
   "type": "string",
   "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."
  },
  "contact_name": {
   "type": "string",
   "description": "Your name or operator handle, recorded with the escrow"
  },
  "quorum_rules": {
   "type": "string",
   "description": "The release rules for this blob, e.g. '2-of-3 named trustees must approve release'"
  },
  "recovery_blob": {
   "type": "string",
   "description": "Client-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt"
  },
  "contact_handle": {
   "type": "string",
   "description": "Optional contact (email or handle) for the operator review"
  },
  "idempotency_key": {
   "type": "string",
   "description": "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."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "register_recovery",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "received",
  "account": "0x6fc297afb7e4af856cea20801f8313b6df65b924",
  "receipt_id": "emb_abc123",
  "receipt_version": "embassy-receipt/1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-encrypted-recovery-registration-94b7618a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-embassy.fly.dev](https://www.zero.xyz/host/agent-embassy.fly.dev/llms.txt)