Public beta — launching in one week

The court-admissible web evidence capture API

Send a URL, get back a signed, blockchain-timestamped, self-verifiable evidence package — Bitcoin OpenTimestamps, C2PA Content Credentials, RSA-4096 signing and an ISO/IEC 27037 chain of custody. Built for brand protection, eDiscovery and compliance archiving.

Request early access See what's launching

Early-access keys are issued by email as the beta opens.

Request
curl -X POST https://api.getproofsnap.com/v1/captures \
  -H "Authorization: Bearer ps_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://example.com/listing" }'
Response
{
  "capture_id": "cap_a1b2c3d4e5f6g7h8",
  "status": "completed",
  "package_url": "https://… (24h presigned ZIP)",
  "verification_url": "https://verify.getproofsnap.com/cap_…",
  "manifest_hash": "sha256:…",
  "c2pa": { "included": true }
}

What makes the capture court-admissible

Every package carries the three things courts ask for — integrity, an independent timestamp and chain of custody — plus content provenance against deepfake challenges.

Bitcoin OpenTimestamps

Each capture's manifest hash is anchored to the Bitcoin blockchain — a tamper-evident timestamp that needs no trust in us.

C2PA Content Credentials

Every screenshot is signed with C2PA Content Credentials — the open content-provenance standard (ISO 22144) — to withstand deepfake challenges.

RSA-4096 signing & free verification

A fresh ephemeral keypair signs each manifest and is discarded; the public key ships in the ZIP. Anyone can re-verify a package — no API key required.

Single & batch capture

Capture one URL or up to 50 in a single request. Each becomes its own signed package and fires its own completion webhook.

Full-page, social & MHTML

Headless Chromium renders the full page (desktop or mobile), auto-expands collapsed comments and replies, and ships a single-file MHTML snapshot for eDiscovery review platforms.

Signed webhooks & safe by default

HMAC-SHA256-signed capture.completed callbacks with replay protection. Server-side SSRF blocking, TLS-only and per-key authentication.

The endpoints

What's in every package

A self-contained, self-verifiable evidence ZIP:

screenshot.jpeg c2pa.json page.html page.mhtml domtextcontent.txt metadata.json evidence.pdf forensic_log.json chain_of_custody.json manifest.json manifest.sig manifest.json.ots publickey.pem

The same evidence format used by the ProofSnap Chrome extension.

Built for the courtroom

Every package ships with an Evidence Pack PDF describing a reproducible, documented capture process under U.S. Federal Rule of Evidence 901(b)(9) — a process or system that produces an accurate result. Add your custodian details and it pre-fills a FRE 902(14) self-authentication declaration for the qualified person to sign.

Evidence Pack templates are in beta and not a substitute for legal advice; final admissibility is at the court's discretion.

Pricing at launch

Metered and usage-based. Bitcoin OpenTimestamps and C2PA are included on every plan.

On-demand forensic capture services charge from $199 per website. ProofSnap starts at $0.25 per capture — the same court-admissible evidence, as an API call.

Developer

$0/mo

Pay-as-you-go sandbox & production.

$1.50 per capture

Most popular

Startup

$99/mo

200 captures included.

$0.60 per overage capture

Growth

$499/mo

2,000 captures included.

$0.40 per overage capture

Need 10,000+ captures, a custom contract or a DPA? Talk to us.

Who it's for

Brand protection

Preserve counterfeit listings, trademark abuse and copycat sites the moment your scanners find them — before the seller deletes the evidence.

eDiscovery & litigation

Capture public web and social content straight into your case workflow, with MHTML and an FRE 901(b)(9) process record.

Compliance archiving

Tamper-evident, hash-anchored snapshots of the pages you're obligated to preserve, with a verifiable chain of custody.

Frequently asked questions

What is the ProofSnap web evidence capture API?

It's a REST API that turns any URL into a court-admissible evidence package: a full-page screenshot, the page HTML and a single-file MHTML snapshot, sealed with an RSA-4096 signed manifest, C2PA Content Credentials, a Bitcoin OpenTimestamps proof and an ISO/IEC 27037 chain of custody.

Are website screenshots admissible in court?

A plain screenshot is easily challenged — it carries no verifiable timestamp or integrity proof. Web evidence becomes admissible when it's captured by a documented process and sealed with a cryptographic hash, an independent timestamp and a verifiable chain of custody. ProofSnap produces all three.

How is this different from a screenshot API?

A screenshot API returns an image. ProofSnap returns a signed, blockchain-timestamped, self-verifiable evidence package designed to prove a page looked a certain way at a certain time.

What is FRE 902(14)?

A U.S. Federal Rule of Evidence that lets electronic data be self-authenticated through a hash-based digital identification process certified by a qualified person. ProofSnap pre-fills that custodian declaration in its Evidence Pack.

How do I verify a ProofSnap evidence package?

Send the ZIP to the public /v1/verify endpoint, or check it yourself: validate the RSA-4096 manifest signature against the bundled public key and confirm the Bitcoin OpenTimestamps proof. No API key is required.

When does the API launch?

The public beta launches in one week. Request an early-access key by email and we'll reach out as it goes live.

Be first in line

The public beta opens in one week. Request an early-access key and start capturing court-admissible web evidence by API.

Request early access

or email support@getproofsnap.com