For software

Send a SHA-256, get the proof.

curl -X POST https://bitgraph.ing/api/commit \
  -H 'content-type: application/json' \
  -d '{"digests":[{"digestB64":"<sha-256, base64>","hashAlg":"sha256"}]}'

Every BitGraph is kept. Fetch one by its hash, here or on the ledger:

curl https://bitgraph.ing/api/proofs/<sha-256, base64url>

For an AI agent:

claude mcp add bitgraph -- npx -y @mikeargento/bitgraph-mcp

A proof checks offline with @mikeargento/bitgraph-verify. Pin the enclave’s measurement, reproducible from the published source:

d9128d67c406a30f988f74ece8b5cced5c9a96491289037f50bddb5f10aac2bc9d1d315dd7bf65428899ccde72b95b86

Anyone can put a recent block hash in a file or write a file’s hash to a blockchain. Neither requires BitGraph, and neither gives the file a position of its own.

BitGraph does. It binds the file to a fresh, unpredictable value used exactly once, at a unique position in an unbroken sequence. That position can never be reused, reassigned, or occupied by anything else.