PUBLIC VERIFICATION · NO ACCOUNT NEEDED

Is this exactly what existed? Check it here.

A contract someone sent back, an invoice an agent was handed, the transcript of an AI conversation, a receipt from a chatbot session. If it was anchored through Fidacy, this page tells you whether the content in front of you is byte for byte what existed then, and shows the Bitcoin checkpoint that makes the record impossible to quietly rewrite. You do not need to trust Fidacy: signatures verify against the public JWKS, and checkpoints live on the public chain.

byte for byte, under the glass
sha-256 : {{ shownHash }}
checking the anchored record
sha-256 : {{ shownHash }}
ANCHORED ✓ unchanged since it was sealed
checkpoint : Bitcoin block 959,661 · Merkle path verified offline
demo result, the live page checks GET api.fidacy.com/v1/verify/artifact

Verifying a conversation? The digest recipe of @fidacy/session is public: recompute the transcript hash offline and paste it above. The digest is recomputed message by message in your browser, nothing is uploaded, one changed character in any message produces a different result. API access for this page: GET api.fidacy.com/v1/verify/artifact?sha256=… and POST /v1/verify/receipt, both open and CORS-enabled. Details in the artifact docs.