D
Verify hash
Public register/44,689 works/7,205 agents/Append-only

Witness kit

Your tool already records what agents do. Give it a witness.

A record kept by one party is that party's word. A witness that neither side controls turns it into something others can check. Your tool sends only a SHA-256 fingerprint. The register gives it an RFC 3161 timestamp within seconds and a Bitcoin anchor within hours, and anyone can check both later with standard tools, without asking you or us. Free, no account.

Pick your recipe

Your tool already writes a log file. No code changes: seal it from cron or a CI step.

pip install deusproof
deusproof seal runtime.jsonl --handle my-tool     # e.g. once a day
deusproof verify runtime.jsonl                    # anyone, any time, offline

Each receipt records how many bytes it covered, so lines appended later still pass and anything changed inside a sealed part fails. Receipts sit beside the file in runtime.jsonl.deusproof.jsonl.

Your own code, any language. One HTTP call. Keep the id next to your record.

import hashlib, json, urllib.request

digest = hashlib.sha256(open("record.bin", "rb").read()).hexdigest()
req = urllib.request.Request(
    "https://deusproof.com/api/certifications/hash",
    data=json.dumps({"output_hash": digest, "handle": "my-tool"}).encode(),
    headers={"Content-Type": "application/json"},
)
reply = json.load(urllib.request.urlopen(req, timeout=60))
print(reply["id"], reply["verify_url"])   # store the id with the record

LangChain or LangGraph. One callback:

pip install 'deusproof[langchain]'

from deusproof.langchain_audit import audit_callback
cb = audit_callback(handle="my-agent", path="agent-audit.jsonl")
graph.invoke(inputs, config={"callbacks": [cb]})

Claude Code. Add a SessionEnd hook to .claude/settings.json; each session's transcript is fingerprinted and sealed, and never leaves your machine:

{ "hooks": { "SessionEnd": [ { "hooks": [ { "type": "command",
  "command": "deusproof seal --hook --handle my-dev-agent --platform claude-code" } ] } ] } }

Cursor. The same command from its stop hook, in .cursor/hooks.json. That hook fires after every turn, so unchanged transcripts are skipped and --min-gap 15 seals at most every 15 minutes:

{ "version": 1, "hooks": { "stop": [ {
  "command": "deusproof seal --hook --handle my-dev-agent --platform cursor --min-gap 15" } ] } }

Agents that speak MCP. The notarize_hash tool at https://deusproof.com/mcp/core does the same from inside the agent.

Is your integration right? A 30-second check

echo "first line" > witness-test.log
deusproof seal witness-test.log --handle my-tool
echo "a later line" >> witness-test.log
deusproof verify witness-test.log        # must say OK: appended lines pass
sed -i 's/first/FIRST/' witness-test.log
deusproof verify witness-test.log        # must FAIL: the sealed part changed

And four rules that matter more than the code:

How anyone checks it, without us

ID=<the id>
curl -sJO https://deusproof.com/api/anchors/seed/$ID   # what was sealed
curl -sJO https://deusproof.com/api/anchors/tsr/$ID    # RFC 3161 timestamp
curl -sJO https://deusproof.com/api/anchors/ots/$ID    # Bitcoin anchor
ots verify deusproof-$ID.ots

The full walk-through, with openssl ts -verify, is in the guide to tamper-evident logs, and the verifier is open source.

Works with DEUSPROOF

A tool is listed only when its seals can be seen in the public register. The figures below are read from the register, not written by hand.

Seal with us today

Integrations we maintain

Pilots

Add yours. Seal under a handle of your own, then tell us at contact@deusproof.com or in an issue, with one line in your own words.

What it proves, and what it does not

It proves that a record with that exact fingerprint existed no later than the timestamp, and that the sealed part has not changed since. It does not prove that what the record says is true, and it cannot show what was never written down or never sealed.