# Agent Embassy — Copy Correction with Proof-of-Work Receipt

> Agent Embassy — Copy Correction with Proof-of-Work Receipt is a paid API for AI agents from aemb.pro, paid per call via x402, $25/call, status unknown (last checked 2026-10-11).

Submits copy text for correctness verification, pays for the work on-chain via x402, and returns a signed embassy receipt proving what was authorized, actioned, and who is liable.

## Facts

- Endpoint: POST https://aemb.pro/v1/copy/correct?utm_source=zero.xyz
- Price: $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-copy-correction-with-proof-of-work-receipt-2e0ba01c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r19wpKFtphCpfN-LOWN_7

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-copy-correction-with-proof-of-work-receipt-2e0ba01c -d '<json body>'
```

Example prompt: Check this landing page copy for correctness, pay for the review through Agent Embassy, and give me back the receipt ID and verdict so I have proof of what was authorized and actioned.

## When to prefer this

Choose this endpoint when your agent needs both a content correction result AND a verifiable, on-chain proof-of-work receipt — especially in regulated, auditable, or multi-party workflows where accountability and liability boundaries matter. It is the right choice over a plain proofreading API when you need cryptographic evidence of who authorized the action, what happened, and who bears liability. Prefer it when your pipeline uses x402 micropayments and you want a single call that combines payment, correction, and receipt issuance.

## Known failure modes

- Payment authorization fails — returns 402 if USDC funds are insufficient or payment header is malformed
- Invalid or missing copy input — returns 400 with validation error
- Account address not recognized — receipt may not be linkable to caller
- Service unavailable — 5xx if the embassy backend is down
- Verdict not clean — copy is flagged, receipt still issued but verdict reflects failure

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing: the tool name ('correct_copy'), an ordered action chain showing each step (request, authorization, action, proof, liability_boundary), a status ('complete'), the agent account address, a verdict ('clean' or otherwise), a unique receipt ID, and a receipt version string (embassy-receipt/1) — constituting cryptographically traceable proof of the correction event.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "draft": {
   "type": "string",
   "description": "The raw draft copy to correct (1-20000 chars)"
  },
  "links": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "HTTPS URLs the copy references; each is verified alive via HEAD (fallback GET), 8s timeout, redirects never followed (max 20)"
  },
  "register": {
   "type": "string",
   "description": "Voice register: founder-notes, elite, force, or bright"
  },
  "required_terms": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Terms that must appear in the final copy (max 20; each term max 100 chars; counted case-insensitively)"
  },
  "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": "correct_copy",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "complete",
  "account": "0x1111111111111111111111111111111111111111",
  "verdict": "clean",
  "receipt_id": "emb_xyz789",
  "receipt_version": "embassy-receipt/2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-copy-correction-with-proof-of-work-receipt-2e0ba01c/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)