# Agent Embassy Verified Web Check

> Agent Embassy Verified Web Check is a paid API for AI agents from agent-embassy.fly.dev, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-11).

Fetches a public HTTPS URL server-side, checks it against user-defined conditions (status, body substring, or JSON field), and returns a cryptographically signed, re-verifiable Outcome Receipt proving the result

## Facts

- Endpoint: POST https://agent-embassy.fly.dev/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-verified-web-check-50511520
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z2V94eVdiCsIWNGpO24__

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-verified-web-check-50511520 -d '<json body>'
```

Example prompt: Can you verify that https://myapi.example.com/order/12345/status returns HTTP 200 and that the JSON field 'order.fulfilled' equals true, then give me the signed receipt I can show as proof?

## When to prefer this

Choose this endpoint when you need tamper-evident, machine-verifiable proof that a specific public HTTPS URL returned a particular status, body content, or JSON field value — especially in agent-to-agent commerce contexts where a neutral third-party attestation is required. Prefer it over DIY HTTP checks when auditability, re-verifiability by counterparties, and signed receipts matter. It is particularly suited for post-payment delivery verification, webhook confirmation, and any scenario where a counterparty needs to independently re-verify the outcome.

## Known failure modes

- URL points to a private IP or non-public host — refused with an error
- HTTP status does not match expect_status — receipt issued with verdict 'fail'
- Body does not contain expect_body_contains substring — verdict 'fail'
- JSON path does not exist or value does not match expect_json_equals — verdict 'fail'
- URL is unreachable or times out — error or fail verdict
- x402 payment not completed or insufficient — request rejected before check
- Invalid or malformed URL provided — request rejected

## How this service works

Verify a web claim and get a signed, re-checkable Outcome Receipt — machine-verifiable proof of delivery for agent commerce. The Embassy fetches your HTTPS URL once, server-side, and checks it against your conditions: HTTP status, a body substring, or a JSON field value. The receipt records the check transcript and verdict so anyone can re-verify. $0.15 per check via x402. Fully automated, no human review.

## Output

A signed JSON Outcome Receipt containing: a unique receipt_id (e.g. 'emb_jkl012'), the verdict ('pass' or 'fail'), the payer wallet account address, a chain-of-custody array (request, authorization, action, proof, liability_boundary), receipt version string, tool name, and status. The receipt can be shared with any counterparty and independently re-verified.

## 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/1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-verified-web-check-50511520/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-embassy.fly.dev](https://www.zero.xyz/host/agent-embassy.fly.dev/llms.txt)