# Web Capture – Signed Page Records

> Web Capture – Signed Page Records is a paid API for AI agents from web-capture.j0wn0.chatgpt.site, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-11).

Captures a webpage as screenshot, rendered HTML, and PDF with cryptographically signed file hashes for tamper-evident archival.

## Facts

- Endpoint: POST https://web-capture.j0wn0.chatgpt.site/v1/captures?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/web-capture-signed-page-records-ea96caa4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MTaMWrz6sgNn5mqix91br

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-capture-signed-page-records-ea96caa4 -d '<json body>'
```

Example prompt: Can you capture and archive https://example.com/terms right now and give me a signed record — screenshot, PDF, and HTML — so I have proof of what the page looks like today before it potentially changes?

## When to prefer this

Choose this endpoint when you need a tamper-evident, signed archival record of a webpage — not just a raw screenshot or simple scrape. It is ideal for legal discovery, compliance documentation, journalistic evidence, or any scenario where you must later prove what a page contained at a specific moment. Prefer it over generic screenshot APIs when cryptographic signing and a verifiable hash are required.

## Known failure modes

- URL is unreachable or returns a non-200 status — capture fails with an error response
- Invalid or malformed URL input causes a 400 validation error
- Page requires authentication or blocks headless browsers — capture may be incomplete or blank
- Timeout if the target page is extremely slow to load
- Duplicate request_id may conflict with a prior capture

## How this service works

Keep a browser capture before a page changes. Screenshot, rendered HTML, PDF and signed file hashes for 0.10 USDC on Base.

## Output

Returns a JSON object with a unique capture ID, a status field (e.g. 'ready'), a verification URL path where the signed record can be independently checked, and an independent_timestamp flag indicating whether a third-party timestamp was applied. The actual screenshot, rendered HTML, and PDF assets along with their signed file hashes are accessible via the verification URL.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri"
  },
  "request_id": {
   "type": "string",
   "format": "uuid"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "12345678-1234-4234-8234-123456789abc",
  "status": "ready",
  "verification_url": "/verify/12345678-1234-4234-8234-123456789abc",
  "independent_timestamp": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/web-capture-signed-page-records-ea96caa4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from web-capture.j0wn0.chatgpt.site](https://www.zero.xyz/host/web-capture.j0wn0.chatgpt.site/llms.txt)