# Web Page Evidence Capture

> Web Page Evidence Capture is a paid API for AI agents from msgom-159-89-4-32.run.pinggy-free.link, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Captures a cryptographic snapshot of a web page at a given URL, returning its content hash, HTTP status, title, links, and change detection data as tamper-evident evidence.

## Facts

- Endpoint: POST https://msgom-159-89-4-32.run.pinggy-free.link/evidence?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-page-evidence-capture-aa36e8e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E5vVv4piCrbHFzJ_t5EkL

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 web-page-evidence-capture-aa36e8e1 -d '<json body>'
```

Example prompt: Capture evidence for https://example.com/terms-of-service right now — I need the content hash, HTTP status, page title, and any links found on the page so I have a tamper-evident record of what it currently says.

## When to prefer this

Use this endpoint when you need a lightweight, cryptographically verifiable snapshot of a public webpage — especially for legal evidence gathering, compliance audits, or change detection — and you don't need a full rendered screenshot or DOM interaction. It is ideal when a SHA-256 content hash plus HTTP metadata is sufficient proof, rather than a visual or rendered capture.

## Known failure modes

- Target URL is unreachable or returns a non-200 status — httpStatus field reflects the error code
- URL scheme is invalid or not http/https — request rejected with validation error
- Target page is behind authentication and content is inaccessible — shallow or empty capture
- Pinggy tunnel may be intermittently unavailable — endpoint itself may return 5xx
- Redirects to a page with no body — bytes may be 0 and title absent

## How this service works

Website hosted for free through pinggy.io&gt;
    &lt;meta name=

## Output

Returns the original URL, final redirected URL, HTTP status code, page title, content size in bytes, SHA-256 hash of the page content, a sample of links found on the page, a receipt object, and a changeDetection object indicating whether content has shifted from prior captures.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "http(s) URL to capture evidence for"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url",
  "contentSha256"
 ],
 "properties": {
  "url": {
   "type": "string"
  },
  "bytes": {
   "type": "integer"
  },
  "title": {
   "type": "string"
  },
  "receipt": {
   "type": "object"
  },
  "finalUrl": {
   "type": "string"
  },
  "httpStatus": {
   "type": "integer"
  },
  "linksSample": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "contentSha256": {
   "type": "string"
  },
  "changeDetection": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/web-page-evidence-capture-aa36e8e1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from msgom-159-89-4-32.run.pinggy-free.link](https://www.zero.xyz/host/msgom-159-89-4-32.run.pinggy-free.link/llms.txt)