# Web Evidence Capture API

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

Fetches a URL and returns cryptographic evidence including SHA-256 content hash, HTTP status, page title, byte size, and sampled links for verification purposes

## Facts

- Endpoint: POST https://btolb-159-89-4-32.free.pinggy.net/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-evidence-capture-api-c88e0282
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ajMKnuboKukTQY53Mqmzh

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-c88e0282 -d '<json body>'
```

Example prompt: Can you capture cryptographic evidence for https://example.com/terms — I need the SHA-256 hash, HTTP status, page title, and a sample of its links so I can prove what the page said today.

## When to prefer this

Choose this endpoint when you need cryptographic proof (SHA-256) of a webpage's content at a specific point in time, especially for legal, compliance, or audit use cases. It is also useful for lightweight change detection workflows where you compare successive content hashes. Prefer it over a generic scraper when the integrity and verifiability of the captured content matters more than structured data extraction.

## Known failure modes

- URL is unreachable or returns a non-200 status — httpStatus field reflects the actual code but evidence may be incomplete
- URL redirects to an unexpected destination — finalUrl will differ from input url
- Malformed or non-HTTP URL input — likely returns a 400 validation error
- Target page blocks automated fetching (e.g. bot detection) — content hash may reflect an error/block page rather than real content
- Network timeout on the tunneled Pinggy host — service may be intermittently unavailable as it runs on a free tunnel

## 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 redirected URL (if any), HTTP status code, page title, content size in bytes, a SHA-256 hash of the page content, a sample array of links found on the page, a change detection object indicating whether content has changed, and a payment receipt object confirming the x402 micropayment was processed.

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