# Tollkit Extract – Web Page Attestation

> Tollkit Extract – Web Page Attestation is a paid API for AI agents from web.tollkit.dev, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-11).

Fetches a live web page, hashes its content and optionally a screenshot, and returns a cryptographic attestation suitable as evidence in disputes.

## Facts

- Endpoint: POST https://web.tollkit.dev/attest?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tollkit-extract-web-page-attestation-0115fee5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NX37z7WqS-NJE-JvLltHh

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 tollkit-extract-web-page-attestation-0115fee5 -d '<json body>'
```

Example prompt: Capture a cryptographic attestation of https://example.com/terms with a screenshot so I have tamper-proof evidence of what it says right now.

## When to prefer this

Choose this endpoint when you need cryptographic, timestamped proof of a webpage's content at a specific moment — especially for dispute resolution, compliance records, or preserving evidence of claims that could be edited later. It is distinct from simple page scrapers because it returns a verifiable attestation rather than just raw text. No account or API key is required; payment is made per-call via x402 in USDC.

## Known failure modes

- URL is unreachable or returns a non-200 status — attestation fails with a fetch error
- URL uses HTTP instead of HTTPS — rejected by the schema's format constraint
- Payment in USDC not provided or insufficient — 402 response returned before processing begins
- Screenshot capture times out on heavy pages — falls back or returns error depending on service behavior
- Page requires authentication or bot-blocking — content hash may reflect an error or login page rather than the intended content

## How this service works

Pay-per-call product page extraction. No account, no API key: pay in-band with x402 in USDC on Base or Solana.

## Output

Returns a cryptographic attestation record containing a hash of the fetched page content, an optional screenshot hash, and a timestamp, providing tamper-evident proof of what the URL contained at the moment of the call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "description": "Absolute https:// URL of the page to attest to. Anything a dispute could turn on: terms of service, a price, a published policy, a competitor's claim, a listing that may be edited later."
  },
  "screenshot": {
   "type": "boolean",
   "default": true,
   "description": "Capture and hash a screenshot. On by default — an attestation without one is much weaker evidence. Turn it off for a faster, text-only record."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tollkit-extract-web-page-attestation-0115fee5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from web.tollkit.dev](https://www.zero.xyz/host/web.tollkit.dev/llms.txt)