# Agent Embassy — Agent Identity Issuance

> Agent Embassy — Agent Identity Issuance 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).

Issues a cryptographically verifiable agent identity and receipt after an agent pays for and completes a unit of work, establishing an auditable proof of action with liability boundaries.

## Facts

- Endpoint: POST https://aemb.pro/v1/agent-id/issue?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-issuance-eefeef5c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pc9UazpCTXOxJNVbXodA9

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-issuance-eefeef5c -d '<json body>'
```

Example prompt: Issue an Agent Embassy identity and receipt for my agent at account 0x1111...1111 — I need a verifiable proof chain showing the request, authorization, action, and liability boundary after it completes and pays for this task.

## When to prefer this

Choose this endpoint when you need a cryptographically anchored, machine-readable proof that an autonomous agent paid for and completed a specific action — especially in multi-agent systems requiring accountability, liability boundaries, or compliance audit trails. It is distinct from simple payment APIs because it issues a persistent agent identity and a structured proof chain, not just a payment confirmation.

## Known failure modes

- Payment not received or insufficient — 402 response before receipt is issued
- Invalid or malformed account address — request rejected
- Duplicate receipt attempt for the same action — may return conflict or deduplicated result
- Network or chain timeout during proof generation — incomplete receipt
- Authorization step fails — chain halted before action proof is created

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing the tool name (agentid_issue), a proof chain array listing stages (request, authorization, action, proof, liability_boundary), a status field, the agent's account address, a 64-character hex agent_id, a unique receipt_id prefixed with 'emb_', and a receipt_version string (embassy-receipt/1). This receipt serves as an immutable, verifiable record of the agent's identity, payment, and action.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "agent_pubkey": {
   "type": "string",
   "description": "The agent's public key (hex), the root of the Agent ID"
  },
  "principal_id": {
   "type": "string",
   "description": "ID of the accountable principal on file with the Embassy"
  },
  "operator_name": {
   "type": "string",
   "description": "Public name of the operator running the agent"
  },
  "validity_days": {
   "type": "number",
   "description": "Days until the Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted"
  },
  "principal_kind": {
   "type": "string",
   "description": "Kind of principal: human or legal_entity"
  },
  "idempotency_key": {
   "type": "string",
   "description": "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."
  },
  "principal_label": {
   "type": "string",
   "description": "Public label for the principal"
  },
  "agent_key_scheme": {
   "type": "string",
   "description": "Key scheme for agent_pubkey: eip191 or ed25519 (default eip191)"
  },
  "operator_contact": {
   "type": "string",
   "description": "Public contact for the operator"
  },
  "principal_attestation_method": {
   "type": "string",
   "description": "How the Embassy verified the principal"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-agent-identity-issuance-eefeef5c/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)