# Agent Embassy Verify — Check and Prove Agent Work Completion

> Agent Embassy Verify — Check and Prove Agent Work Completion is a paid API for AI agents from aemb.pro, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-11).

Verifies that an agent action was authorized, executed, and recorded, returning a signed receipt proving what happened and establishing a liability boundary.

## Facts

- Endpoint: POST https://aemb.pro/v1/check/verify?utm_source=zero.xyz
- Price: $0.15/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-verify-check-and-prove-agent-work-completion-1522cef3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_64_1zNShWHm9r-R0T0DhG

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-verify-check-and-prove-agent-work-completion-1522cef3 -d '<json body>'
```

Example prompt: Check whether my agent action went through and get me a receipt proving it — I need to verify the full authorization chain and confirm the verdict for account 0x1111111111111111111111111111111111111111 so I have a liability record I can reference.

## When to prefer this

Choose this endpoint when you need cryptographic, receipt-backed proof that an autonomous agent action was authorized, executed, and bounded by liability — particularly after an x402 payment-gated task. Prefer this over generic logging or audit tools when you need a structured, versioned embassy-receipt that can be shared with third parties, used in dispute resolution, or stored as an accountability artifact specific to the Agent Embassy ecosystem.

## Known failure modes

- Invalid or unrecognized action/check ID returns an error or failed verdict
- Account address not matching the action results in verification failure
- Action not yet completed may return incomplete status rather than 'complete'
- Malformed request body causes 400-level error
- Payment of $0.15 USDC not processed leads to 402 Payment Required
- Chain verification step failure returns partial chain with non-passing verdict

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing: the tool name ('verified_check'), an ordered chain of verification stages (request, authorization, action, proof, liability_boundary), a status ('complete'), the agent's account address, a pass/fail verdict, a unique receipt ID (e.g. emb_jkl012), and a receipt version string (embassy-receipt/1). This constitutes a tamper-evident audit record of the agent action.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "HTTPS URL to check (max 2000 chars; no credentials in URL). Fetched once; up to 3 redirects followed, 10s timeout, 1MB body cap"
  },
  "expect_status": {
   "type": "number",
   "description": "Expected HTTP status code; truncated to an integer. Defaults to 200 when omitted"
  },
  "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."
  },
  "expect_json_path": {
   "type": "string",
   "description": "Dot-separated path into the JSON body, e.g. 'data.price' (max 500 chars). Only evaluated when set"
  },
  "expect_json_equals": {
   "description": "Expected value at expect_json_path; compared by canonical JSON equality. Defaults to null when omitted"
  },
  "expect_body_contains": {
   "type": "string",
   "description": "Substring that must appear in the response body (max 5000 chars). Skipped when empty or omitted"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-verify-check-and-prove-agent-work-completion-1522cef3/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)