Don't trust us. Check.
$ curl -s aisourceoftruth.com/v1/keys/{publisher} # then verify any signature locally. No call of ours is in the loop.
Signature check
Paste a record digest. The page fetches the signed bytes, the registry envelope, and the publisher key directory (all public) and verifies the ES256 signature in your browser.
Nothing you paste here leaves your machine. The point of a public record is that checking it requires no permission.
Re-verify a claim
Re-run any claim against its cited passage through the publisher's free endpoint. The judge is hash-pinned in the record, so the score is checkable, not take-our-word. Re-verification lives with the publisher, never the registry.
POST {publisher}/v1/reverify
{ "report": "<digest>", "claim_id": "c_017" }
# example → { "entailment": 0.96, "state": "supported",
# "judge_prompt_version": "v3" }
Key directory
| KEY | PUBLISHER | ALG | STATUS | REGISTERED |
|---|---|---|---|---|
| No keys registered yet. A publisher registers signing keys before its first append. | ||||
rotation is versioned. no signature is ever orphaned: a retired key still verifies the records it signed.
Log consistency
latest root2e1cfa82b035c26cbbbdae63… · 2026-10-16 · witnessed
cc19625f33 · full historycheck it yourself
curl -s https://aisourceoftruth.com/v1/roots/2026-10-16 · compare root_hash to the git witness