# Agent Embassy Trust Report

> Agent Embassy Trust Report 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).

Generates a cryptographic trust report proving an agent paid for work and records the chain of request, authorization, action, proof, and liability boundary.

## Facts

- Endpoint: POST https://aemb.pro/v1/trust/report?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-trust-report-15e55f4e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gVAlbW-xtW4BKMxnCEhW0

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-trust-report-15e55f4e -d '<json body>'
```

Example prompt: Submit a trust report for my agent at account 0x1111...1111 — it just completed a work action and I need a signed receipt proving the full chain of request, authorization, action, proof, and liability boundary was recorded with a pass verdict.

## When to prefer this

Choose this endpoint when you need a cryptographically anchored, structured receipt proving an AI agent both paid for and completed a specific action — especially when accountability, liability boundary documentation, or third-party auditability is required. Prefer it over generic logging when you need a standardized embassy-receipt format with a verdict and chain of custody.

## Known failure modes

- Payment of $0.25 USDC not received — 402 response blocking report generation
- Invalid or malformed agent account address — validation error returned
- Action or authorization data missing from request body — incomplete chain error
- Network or ledger timeout preventing receipt issuance
- Duplicate submission of same action — potential idempotency conflict

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing: a tool identifier ('trust_report'), an ordered chain array listing the stages ['request','authorization','action','proof','liability_boundary'], a status ('complete'), the agent's account address, a verdict ('pass' or equivalent), a unique receipt_id (e.g. 'emb_mno345'), and a receipt_version string ('embassy-receipt/1').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "HTTPS URL of the candidate x402 endpoint to probe (max 2000 chars; no credentials in URL). Probed unpaid via GET, falling back to an empty-body POST when GET returns 404/405"
  },
  "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."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "trust_report",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "complete",
  "account": "0x1111111111111111111111111111111111111111",
  "verdict": "pass",
  "receipt_id": "emb_mno345",
  "receipt_version": "embassy-receipt/2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-trust-report-15e55f4e/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)