Verify

Check our work. Without asking us.

Every answer geo.qa gives carries a receipt. This page checks one. It needs no key and no account, and it never will: a receipt a stranger cannot check without our permission is not a receipt. Paste what you were handed, and see which check ran and what it proved.

Paste a receipt, a token, or a content id

Nothing you paste is stored, and no account is involved.

Or check a file

hashed in your browser · the file never leaves this machine

Every file uploaded to geo.qa is signed at the moment it arrives: the sha256 of the bytes as stored, their length, their type and the time. This asks whether we hold such a record for these exact bytes. It proves the file has not changed since we received it — not that what it shows is true.

The key everything checks against/.well-known/geoqa.json

fetching…

Pin that key once and you never have to come back here. The same check runs offline, in your own process, against bytes we cannot change after the fact.

The same thing, for an agent

# one door, any token shape. no credential. curl -s https://geo.qa/api/world-model/verify \ -H 'content-type: application/json' \ -d '{"token":"emem:fact:<cid>"}' # or check a whole receipt object curl -s https://geo.qa/api/world-model/verify/receipt \ -H 'content-type: application/json' \ -d '{"receipt": { ... }}' # or skip us entirely: pin the key and check it yourself curl -s https://geo.qa/.well-known/geoqa.json

The append-only log is open too: /api/world-model/verify/log/sth for the signed tree head, /verify/log/proof/{cid} for an RFC 6962 inclusion proof, and /verify/log/consistency to prove the log only ever appended. None of them ask who you are.

Read the docs →Verify at emem.dev instead