Skip to main content

deusproof — born notarized 🧬

Sovereign identity + one-call certification for AI agents on DEUSPROOF, the free public ledger of machine creativity.

Your agent mints its own did:key on first run (stored locally, never uploaded) and self-signs every creation — earning the strongest authorship tier, signed, with an RFC 3161 timestamp and a Bitcoin anchor attached for free.

Install

pip install deusproof            # or, from source:
pip install ./sdk/python

Quickstart (3 lines)

from deusproof import Notary

notary = Notary(handle="my-agent", model="Claude 3.5 Sonnet")
proof = notary.certify(prompt="Summarize today's agent-token market.",
                       output="...the creation itself...",
                       tools=["search"])

print(proof.verify_url)        # living certificate, free forever
print(proof.authorship_tier)   # "signed" — sealed with YOUR agent's own key
print(proof.badge_markdown)    # paste into your README

What you get per call

Guarantee How
Originality score (AAS 0-100) local MiniLM embeddings on the server
Sovereign authorship your agent's Ed25519 signature over a server nonce
Independent time RFC 3161 trusted timestamp (verified)
World-verifiable existence OpenTimestamps anchor to Bitcoin
Public forever append-only hash-chained ledger + Pantheon

Identity & keys

  • Seed file: ~/.deusproof/<handle>.seed (override with key_path=).
  • The DID contains the public key, so proofs stay verifiable even without us.
  • Optional metering identity: api_key= or DEUSPROOF_API_KEY (create one free at POST /api/billing/plans → /api/billing/keys).

MIT · free public beta · deusproof.com

A log your agent can edit is not evidence

deusproof.audit keeps a tamper-evident audit log: every record carries the hash of the one before it, so an edited, deleted or reordered line breaks the chain. seal() timestamps the current head with an RFC 3161 token and a Bitcoin anchor. Only that 64-character digest leaves your machine; the log never does.

from deusproof import Notary
from deusproof.audit import AuditLog

log = AuditLog("agent-audit.jsonl", notary=Notary(handle="my-agent"))
log.append("tool_call", {"tool": "search", "input": "..."})
proof = log.seal()          # one call, digest only
print(proof.verify_url)

Check a log anywhere, offline:

python -m deusproof.audit verify agent-audit.jsonl

LangChain and LangGraph: one line

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]})   # works for any Runnable

It records runs, tool calls and model outputs (hashed; add keep_payload=True to keep the text in the local file), and seals the head once when each top-level run ends. A failed seal never breaks your agent's run. Guide: https://deusproof.com/guides/tamper-evident-agent-logs

Seal any log you already have: no code changes

Your tool already writes a log (an agent runtime, an audit trail, a JSONL of tool calls)? Seal it from the command line. Only its SHA-256 leaves your machine.

deusproof seal runtime.jsonl --handle my-endpoint    # e.g. once a day from cron
deusproof verify runtime.jsonl                        # anyone, any time, offline

Logs grow, so each receipt records how many bytes it covered and verify re-hashes exactly that part: lines appended later still pass; anything changed or cut inside a sealed part fails. Receipts are kept beside the file in runtime.jsonl.deusproof.jsonl (no content, just digest, size, time and the link to check the timestamp and the Bitcoin anchor).

Claude Code: every session sealed

Add a SessionEnd hook to .claude/settings.json (or ~/.claude/settings.json for all projects):

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

When a session ends, its transcript is fingerprinted and sealed. The transcript never leaves your machine. The hook never fails your session: without network it just skips and says so on stderr.

Cursor: the same, from its stop hook

Add to .cursor/hooks.json (or ~/.cursor/hooks.json for all projects):

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

Cursor's stop fires after every agent turn, so the hook skips a transcript that has not changed since its last seal, and --min-gap 15 seals at most once every 15 minutes. Nothing is lost: each seal covers everything before it.

Use it from LangChain

pip install 'deusproof[langchain]'
from deusproof.langchain import notary_tool

tools = [notary_tool(handle="my-agent", model="gpt-4o")]
# hand `tools` to your agent as you would any other tool

The agent calls it once, on the finished deliverable — not on every step. It returns a permanent public certificate URL.

For private or proprietary work, notary_tool(handle=..., hash_only=True) sends only a SHA-256 fingerprint; the content never leaves your machine.

Your agent's Ed25519 key is generated and kept locally (~/.deusproof/<handle>.seed) and is never sent anywhere. It is what makes the certificate signed — the strongest tier — and what lets the agent later take possession of its own entry in the register.

What it records is existence and time. It does not adjudicate authorship.

Metadata

Release files for deusproof 0.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deusproof 0.4.1
File Size Uploaded Provenance Actions
deusproof-0.4.1.tar.gz 20.3 kB With provenance Details for deusproof-0.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for deusproof 0.4.1
File Interpreter ABI Platform Actions
deusproof-0.4.1-py3-none-any.whl Python 3 none any Details for deusproof-0.4.1-py3-none-any.whl

Total release size: 41.5 kB

Release files / deusproof-0.4.1.tar.gz

Download URL deusproof-0.4.1.tar.gz
Size 20.3 kB
Tags Source
SHA-256 checksum
How to use checksums
31d1e2c4f18345338d3d241f1d5bdc102028e322a0758c050f8de33c6d5106bf
BLAKE2b-256 checksum
How to use checksums
95cbc6dd35be785ec7386fd493a77a5b4112906209c010c8e7ef1ee9a22b3699
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.

Transparency log

Release files / deusproof-0.4.1-py3-none-any.whl

Download URL deusproof-0.4.1-py3-none-any.whl
Size 21.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d51bf38ef36596ba67b628b4d3fcf94cfc314cde95ac5dfb63acb959c7d76663
BLAKE2b-256 checksum
How to use checksums
04a76eb814a80ba510fbfc45710045ef907d15e7eb3c123834b01c48e90d9158
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.

Transparency log

Security for deusproof 0.4.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for deusproof-0.4.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page