OPERATIONAL anchoring on mainnet · 0/300 anchors this hour no issues in 8h 10m report a problem

📸 Notarized capture

A PNG or PDF of a live page, delivered to you with an on-chain receipt committing to the exact file. "This is what that page looked like, and here is the chain saying when" — the thing evidence, compliance and dispute workflows actually need.

API-only and paid — a browser form cannot carry a bearer token. Get one from pay-per-call, then:

curl -X POST https://bsv.cx/shot -H "authorization: Bearer <token>" \
  -H 'content-type: application/json' \
  -d '{"url":"https://example.com","format":"pdf"}'

price💳 paid 4000 sat buys 10 calls — see pay-per-call

formatspng (default) or pdf — paginated A4, the format archives expect

on-chainOP_RETURN bsv.cx shot1 <manifestHash>

How this differs from the archiver

The web-page archiver is free and public: it captures pages into a gallery anyone can browse. This is a product — a file delivered to you, plus a receipt you can show a third party. Use the archiver to make something publicly citable; use this when you need the file and the proof in your own hands.

Endpoints

POST /shot💳 paid { url, format?, thorough? }

GET /shot/:hashthe proof record — free

GET /shot/:hash/manifestthe exact bytes that hash to the receipt id — free

GET /shot/:hash/imagethe exact file delivered — free

curl -X POST https://bsv.cx/shot -H "authorization: Bearer <token>" \
  -H 'content-type: application/json' \
  -d '{"url":"https://example.com","format":"pdf"}'

The manifest records the format actually produced, not the one requested — an oversized PNG is degraded to JPEG, and a manifest that misdescribed the file would be a broken proof.

← back to bsv.cx