# Agent Embassy — ProveIt Verified Check

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

Verifies a previous proof-of-work action and returns a signed receipt confirming what an agent authorized, executed, and proved on-chain.

## Facts

- Endpoint: POST https://aemb.pro/v1/check/proveit-verified?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-embassy-proveit-verified-check-cd494a0b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ppSeKHh4ayo2niSuOgZ_R

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-proveit-verified-check-cd494a0b -d '<json body>'
```

Example prompt: Check whether the ProveIt verification passed for my H100 SXM on-demand job — use idempotency key 'a3f2e1d0-bc45-4f67-89ab-cde012345678' and give me the receipt ID and verdict.

## When to prefer this

Choose this endpoint when an AI agent needs a tamper-evident, on-chain-anchored proof that a specific compute job was authorized, paid for, and executed — particularly when downstream systems, auditors, or liability boundaries require a structured receipt with a full chain of custody. Prefer it over generic logging or status-check APIs when you need the verdict + receipt combo that Agent Embassy's embassy-receipt format provides.

## Known failure modes

- Published or previously-seen example idempotency keys are rejected outright
- A replayed idempotency key returns the original receipt even if inputs differ — no re-execution occurs
- Missing or malformed idempotency key (not UUID v4) causes request rejection
- GPU class string exceeding 64 characters is invalid
- Invalid offer type value (not ondemand, bid, or reserved) causes failure
- Receipt not found if the original action never completed or was never submitted

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing the tool name, a chain array listing each stage (request, authorization, action, proof, liability_boundary), overall status, the paying account address, a pass/fail verdict, a unique receipt ID (e.g. emb_tuv234), and the receipt version string (embassy-receipt/2).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "gpu": {
   "type": "string",
   "description": "Optional GPU class, e.g. 'H100 SXM' (max 64 chars). Omit for the per-class snapshot"
  },
  "type": {
   "type": "string",
   "description": "Offer type: ondemand, bid, or reserved. Defaults to ondemand"
  },
  "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": "proveit_verified_check",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "complete",
  "account": "0x1111111111111111111111111111111111111111",
  "verdict": "pass",
  "receipt_id": "emb_tuv234",
  "receipt_version": "embassy-receipt/2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-proveit-verified-check-cd494a0b/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)