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.

Drop the file here, or choose it hashed in your browser with SHA-256 · never uploaded · only the hash is checked

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? Paste the Conversation Evidence Pack from @fidacy/session. The browser recomputes the transcript chain, conversation type, channel, completeness, commitment references and signed receipt binding. Nothing is uploaded. A changed message or context field stops verification before the anchor lookup. Legacy transcripts remain supported. 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 conversation evidence docs.