# Agent Embassy — Agent Identity Renew

> Agent Embassy — Agent Identity Renew is a paid API for AI agents from aemb.pro, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-11).

Renews an agent's on-chain identity, records the authorization chain, and issues a tamper-evident embassy receipt proving what happened.

## Facts

- Endpoint: POST https://aemb.pro/v1/agent-id/renew?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-embassy-agent-identity-renew-2b5dcf59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u7XZJX8rPjQcnthcYIqso

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-agent-identity-renew-2b5dcf59 -d '<json body>'
```

Example prompt: Renew my Agent Embassy identity — my agent ID is fedcba9876543210fedcba9876543210fedcba9876543210fedcba9876543210 and account is 0x1111111111111111111111111111111111111111 — and give me back the receipt proving the renewal happened.

## When to prefer this

Choose this endpoint when an AI agent needs to maintain an active, verifiable on-chain identity and produce cryptographic proof that its actions were authorized. It is specifically suited for agentic workflows where accountability, liability boundaries, and tamper-evident receipts are required — particularly when integrating with the Agent Embassy ecosystem. Prefer this over generic auth tokens or session renewal when you need an auditable chain of custody tying an agent action to a specific account.

## Known failure modes

- Insufficient USDC payment — 402 Payment Required if payment header is missing or underfunded
- Invalid or expired agent ID — renewal rejected if the agent ID does not exist or is unrecognizable
- Invalid account address — malformed Ethereum address causes request failure
- Duplicate renewal attempt within the same validity window — may return conflict or idempotency error
- Network or chain congestion — slow on-chain confirmation may cause timeout

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing the tool name (agentid_renew), the full authorization chain array (request, authorization, action, proof, liability_boundary), completion status, the account address, the agent ID, a unique receipt ID (emb_...), and the receipt version (embassy-receipt/1). This receipt serves as tamper-evident proof that the renewal was authorized and executed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "agent_id": {
   "type": "string",
   "description": "The Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected"
  },
  "validity_days": {
   "type": "number",
   "description": "Days until the renewed Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted"
  },
  "idempotency_key": {
   "type": "string",
   "description": "Optional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when omitted, no dedupe occurs. Keys are scoped per tool and per payer account: the same key on another tool — or from another wallet — is unrelated."
  },
  "revocation_signature": {
   "type": "string",
   "description": "Hex signature over the exact UTF-8 message agent-id-revoke:<OLD_agent_id> (64-char lowercase ID, no trailing newline) — the signature covers the OLD Agent ID being retired. EIP-191: personal_sign the message STRING (personal_sign envelope REQUIRED — raw ECDSA will not verify), 0x 65-byte hex r||s||v (v=27/28). ed25519: nacl.sign.detached over the message bytes, 64-byte hex. Signer: the principal's on-file revocation key, or the Embassy signer for cause"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "agentid_renew",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "complete",
  "account": "0x1111111111111111111111111111111111111111",
  "agent_id": "fedcba9876543210fedcba9876543210fedcba9876543210fedcba9876543210",
  "receipt_id": "emb_3c4d5e6f7890abcdef123456",
  "receipt_version": "embassy-receipt/2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-agent-identity-renew-2b5dcf59/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aemb.pro](https://www.zero.xyz/host/aemb.pro/llms.txt)