When AI is making decisions on your behalf, you should be able to prove what was sent and what came back. That's what TraceSeal does — an open, free, language-agnostic receipt format. The spec is published, the libraries are published, the verifier is published. The MaximusDev cloud integration is what we're building now.
This is from a working production deployment on 15 April 2026 — third-party-verified on a separate machine using traceseal-verify, which had no access to the operator's audit log, keys, or machine. Receipt format spec v1.0 at traceseal.io.
1{ 2 "receipt_version": "1.0", 3 "execution": { 4 "skill_name": "skill-bundle-demo", 5 "skill_version": "0.1.0", 6 "timestamp": "2026-04-15T04:47:13Z", 7 "inputs_hash": "sha256:62622f40e9d9c8d1…", 8 "outputs_hash": "sha256:86f2cb0244095f3c…", 9 "exit_code": 0, "ok": "true", "wall_time_ms": 167 10 }, 11 "provenance": { 12 "manifest_hash": "sha256:00741b31401d97c1…", 13 "publisher_fingerprint": "ed25519:bf68325fb554f7f0…", 14 "transparency_log_seq": 1 15 }, 16 "attestation": { 17 "operator_fingerprint": "ed25519:f19bc125dcfdb2eb…", 18 "attested_at": "2026-04-15T04:47:40Z", 19 "signature": "5ea122fa1e844dee…" 20 } 21}
Receipt Spec v1.0, the traceseal-observe Python library (with observe_anthropic and observe_openai wrappers), and the traceseal-verify verifier are all on PyPI under Apache 2.0.
Per-tenant Ed25519 operator keys, server-side receipt emission on every cloud AI call, and a Compliance tab where you download signed receipts as a JSON archive. The plan is in cloud-plan.md Phase 3.5.
A WASM verifier at traceseal.io/r/{hash} — paste a receipt, see whether it verifies, no install needed. On the TraceSeal Q2 roadmap; ships before MaximusDev's Compliance tier goes paid.
"Where did my data go?" gets a real answer with a verifiable receipt — not a vague paragraph from your privacy policy.
"How do you handle AI usage logs?" is the question that kills B2B deals. With receipts, the answer is one line plus a demo URL.
TraceSeal is Apache 2.0. If you ever leave MaximusDev, your receipts keep working — same verifier, same library, no lock-in.
The verifier doesn't need our cooperation. A regulator, an auditor, or your customer's IT team can check a receipt themselves with a single command.
EU AI Act Article 50 (transparency obligations for AI-touching apps) entered into force in August 2026. Full enforcement of the broader Act follows in August 2027. TraceSeal receipts cover the technical evidence side — what model, what input, what output, when, by whom. The Compliance + EU AI Act tier (planned: +£20/mo over the base Compliance tier) packages it into a quarterly report for your DPO.
Read the protocol →Pricing when it ships: £39/mo Compliance (receipts), £59/mo Compliance + EU AI Act (receipts + quarterly report). For now, leave your email and we'll let you know when it goes live. No card, no commitment, no automatic enrolment.
An open receipt format for AI calls. Spec, libraries and verifier are published. The MaximusDev cloud integration is what we're building.
Get notified →v1.0 spec at traceseal.io. Apache 2.0.
traceseal-observe + traceseal-verify on PyPI, Apache 2.0.
Per-tenant keys, cloud receipt emission, Compliance tab.
WASM verifier at traceseal.io/r/. Q2 roadmap.
You can answer "where did my data go?" with a verifiable receipt. Procurement teams relax. The format is open — no lock-in. You can verify without our cooperation.