Capture · SHA-256 · your own schedule

Web page change monitoring with evidence: capture, hash, compare.

PageVerified does not run a monitoring service. It will not check a page for you on a timer or send alerts. It gives you the evidence part: each capture returns the file, its SHA-256 hash, the UTC capture time and, by default, a public receipt page. Capture the same page on your own schedule and compare the hashes. When they differ, you hold two dated, hashed copies you can compare.

Five steps

The steps

  1. Fix the settings. Choose one format, one viewport and one full-page setting for the page, and keep them the same for every capture so the comparison is fair.
  2. Capture on your own schedule. Call the capture API from your own job runner, such as a cron job or a CI schedule. PageVerified does not schedule captures for you.
  3. Store what comes back. Keep the capture ID, the SHA-256 hash, the UTC capture time and the receipt link for every run.
  4. Compare the hashes. If the new hash equals the last one, the captured bytes are identical. If it differs, the file changed and you have two dated, hashed copies.
  5. Review the change. Download both files and compare them before you act. A changed hash means the bytes differ, not that anything that matters changed.

Your scheduler, our capture

A minimal job

One capture request, as curl:

curl -s -X POST https://pageverified.com/api/v1/capture \
  -H "authorization: Bearer $PAGEVERIFIED_API_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://example.com/terms","format":"html"}'

The answer carries id, artifact_url, sha256, captured_at and evidence_url. The same call inside a scheduled job:

// Node 18 or later. Run it from your own scheduler.
const res = await fetch("https://pageverified.com/api/v1/capture", {
  method: "POST",
  headers: { authorization: `Bearer ${process.env.PAGEVERIFIED_API_KEY}`, "content-type": "application/json" },
  body: JSON.stringify({ url: "https://example.com/terms", format: "html" }),
});
if (!res.ok) throw new Error(`capture failed: HTTP ${res.status}`); // never store an error as a version
const capture = await res.json();
const last = await readLastHash();          // your own storage
if (capture.sha256 !== last) {
  await saveCapture(capture);              // id, sha256, captured_at, evidence_url
  await flagForReview(capture.evidence_url); // a person looks before anyone acts
}

readLastHash, saveCapture and flagForReview stand for your own code. The download link in artifact_url expires after 24 hours, so save the file or keep the receipt link, which issues a fresh one.

Which format to compare

  • HTML is the page's markup after it loaded in the browser. Use it for a text comparison. text_diff (1 credit) compares two texts and returns the lines that differ.
  • PNG shows how the page looked. Two screenshots of an unchanged page can still differ by a pixel.
  • PDF keeps a paged copy that is easy to file.

A PNG or HTML capture costs 1 credit and a PDF 2 credits. A capture that fails is not charged.

Read this part

Why the hash changes when nothing important did

A hash compares every byte, so anything that changes on each load changes the hash: rotating ads, a clock or a date on the page, a consent banner, a different font, or content that loaded a moment later. Free keys render at up to 1,280 by 800 pixels, so do not compare a free capture with a paid one at a larger size.

Treat a changed hash as a reason to look, not as a decision. An unchanged hash shows that those captured bytes match. It does not show that anything behind the page, such as a database or a private area, stayed the same.

What a pair of captures shows

Two captures of the same URL with different hashes show that PageVerified's renderer produced different files at the two recorded times. Each receipt shows its own URL, time, size and hash, and anyone with the link can check a downloaded file against it.

The capture time is UTC from PageVerified's own server clock. For a signed Capture Record, outside time-stamp authorities later sign the record's hash with their own time, usually within 15 minutes; the record check at /verify shows it.

A capture records what PageVerified's renderer saw at the recorded time. It is not a forensic chain of custody, proof of who wrote a page, or a legal certification.

For a signature anyone can check against published keys, use POST /api/v1/capture/record, which costs the capture plus 4 credits.

One capture without code

Evidence Capture is for one important page, not a schedule. Paste a public URL and pay US$9 once by card, with no account and no key. You get one ZIP with a screenshot and the page's HTML from one browser load, the SHA-256 of each file, the time of the render and a signed record. Each payment buys one capture, so for repeated captures use the API.

What it costs

A free key holds 25 credits and needs no email or card: POST /api/v1/keys. Credit packs are one-time payments in US dollars: $19 for 3,000 credits, $49 for 12,000 credits, $149 for 60,000 credits. A pack does not renew. For captures on a schedule, there are also plans that renew every month until you cancel, adding that month's credits to the same key: $9 for 1,500 credits, $29 for 7,500 credits, $99 for 45,000 credits. A plan buys credits; it does not run captures for you. The pricing page lists the cost of every call.

Common questions

Does PageVerified run the schedule or send alerts?

No. There is no scheduler and no alerts. You call the capture API when you choose, and your own job decides what to do with the result.

How often can I capture?

As often as your credits allow, within the limits: one key can run up to 120 captures an hour, and a free key up to 10 a minute.

Can it capture a page behind a login?

No. Only public http and https pages. The renderer cannot log in, send cookies or set request headers.

Will a court or a platform accept the captures?

That is their decision, and PageVerified makes no promise about it. Each capture gives you a file, its hash, a time and, by default, a receipt others can check.

Next steps

  • Free checks: test an MCP server, read an x402 payment offer or score a domain's agent readiness. No key needed.
  • Evidence Capture: capture one public page as a screenshot and its HTML, with the SHA-256 of each file and a signed record, for US$9 once by card. No account and no API key.
  • Pricing: credit packs and what every tool costs.
  • Documentation: quickstart, MCP setup and every tool's reference page.
  • Hashed captures for change monitoring: the same method as a worked use case.

Related answers: Agent-ready website checklist. Guides: Capture a web page as evidence · Verify a capture · Screenshot API with hash and timestamp.