# Web Evidence Capture API

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

Captures a cryptographic snapshot of a web page at a given URL, returning its content hash, HTTP status, title, and sampled links as verifiable evidence

## Facts

- Endpoint: POST https://ryfoc-159-89-4-32.free.pinggy.net/evidence?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-evidence-capture-api-f6402dab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GppiS2-T5LLVUYnm-Lcmw

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-evidence-capture-api-f6402dab -d '<json body>'
```

Example prompt: Can you capture evidence of what's currently on https://example.com/terms — I need the content hash, HTTP status, and page title so I have a verifiable record of what the page says right now?

## When to prefer this

Use this endpoint when you need a lightweight, cryptographically verifiable snapshot of a specific web URL — especially for audit trails, legal evidence, compliance records, or change detection. It is well-suited for single-URL evidence capture with a content hash output rather than full-site crawling or structured data extraction.

## Known failure modes

- URL is unreachable or returns a non-2xx HTTP status — httpStatus field reflects the error code
- URL redirects to an unexpected domain — finalUrl will differ from url input
- Page content is dynamic/JavaScript-rendered and hash may not be stable across calls
- Pinggy tunnel may be offline or rate-limited, returning a 502/503
- Invalid or malformed URL input returns a 400 validation error
- Very large pages may time out or return truncated content affecting hash accuracy

## How this service works

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

## Output

Returns a JSON object containing the original URL, final URL after redirects, HTTP status code, page title, content size in bytes, a SHA256 hash of the page content for tamper detection, a sample of links found on the page, a change detection object for comparing with prior captures, and a payment receipt.

## 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-evidence-capture-api-f6402dab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ryfoc-159-89-4-32.free.pinggy.net](https://www.zero.xyz/host/ryfoc-159-89-4-32.free.pinggy.net/llms.txt)