Seal where the work happens

Anchoring one file by hand settles one argument. The stronger habit is a workspace that seals itself: every delivered folder, every release, every dataset carries a checkable timestamp the day it is made — without anyone remembering to do it. Each integration below hashes locally and submits only the fingerprint. Your files never leave your machine.

Folders

Watch-folder sealer

A single-file, dependency-free Python daemon. Point it at a delivery folder; anything new or changed is fingerprinted and anchored once it stops changing. Receipts accumulate in a ledger inside the folder.

curl -O https://orphograph.com/dist/orphograph-watch.py
python3 orphograph-watch.py ~/Deliveries

Download orphograph-watch.py →

Releases

GitHub Action

Anchor your build artifacts on every release. The receipt table lands in the job summary; a receipts file ships with the workspace.

- uses: Orphograph/Orphograph/integrations/github-action@master
  with:
    paths: "dist/*"

Action documentation →

AI agents

MCP server

Give any MCP-capable agent the ability to anchor files and folders it produces — proof of existence becomes part of the agent's output, not an afterthought.

Set up the MCP server →

Datasets

Dataset provenance

Anchor a training set, its licenses, and its acquisition log as one Merkle-committed bundle, and hand auditors a certificate that verifies in the browser.

Dataset provenance →

Build your own

Everything above sits on one small API: hash locally, POST /api/anchor, keep the receipt. Free tier is three anchors per day; an API key or a pack lifts the limit. Webhooks can tell your systems when a proof pins to Bitcoin — see webhook docs. Running a platform that RECEIVES receipts? See accepting receipts.

A receipt proves that a file existed in exactly this form by a recorded date, and that it has not changed since. It does not prove who created the file, who owns it, or that its contents are true — and it is not, on its own, a legal determination. See Terms.