One line of @fidacy/session in your chat loop hashes every message into a tamper-evident chain. The transcript never leaves your infrastructure, so a hospital or an insurer keeps its PII and Fidacy only ever sees a hash. The session closes and the digest is anchored to Bitcoin, third-party verifiable, that not even you can rewrite after the fact.
The conversation ends and the customer gets a verify link, no account, no key. They confirm what was said, byte for byte, against a neutral third party that holds no custody. Proof only settles a dispute when the other side can check it too, and a company cannot issue trustworthy proof of itself. Every receipt carries a quiet line of distribution: verified by Fidacy.
We do not judge what the bot said. Moderation is a detection arms race and we chose not to be detection. We gate commitments. A refund, an approved claim, a quote above a threshold, a document sent, each is an action that needs a signed grant. A promise made without a grant does not bind, and your terms of service say so, pointing at the open spec. The bot can talk freely. It cannot obligate you outside what you authorized.
Anchoring alone does not prove completeness, a company could anchor only the flattering conversations. That is why the receipt goes to the customer in real time. When both ends hold the same proof, selective anchoring stops working. The consumer side is not a nice extra, it is what closes the logical hole.
Selling a hospital or an insurer direct is a twelve-month procurement. The fast path is the company that already ships the chatbot. One integration covers a thousand end customers, and audit-proof AI support becomes their sales differentiator. Same distribution playbook we run with MCP, ClawHub and CrabTrap.
One integration covers every customer you serve. Auditable, dispute-proof AI support becomes the reason an enterprise picks you over the vendor that cannot prove what its bot said.
An AI agent that discusses coverage carries the same question a claims adjuster does: what was represented, and does it bind. Anchor the conversation, gate the commitment, keep selling faster than the incumbent.
Patient conversations are heavy PII. The conversation receipt is hash-only: the transcript stays inside your walls and Fidacy holds a proof any auditor can check. The action trail is yours to tune: one switch keeps message text out of it entirely, so what leaves the building is your call, recorded either way.
Send an agent action. Get back approve / review / deny and a cryptographically signed verdict you can check against our public JWKS. No trust in us required.
The market says this layer has to exist. It's running, self-serve: spin up your org, connect an agent in one MCP install, and verify the verdict yourself. No sales call.
The payment is denied. Fail-closed, in every adapter and in the engine itself.
Start with the local firewall. Hosted signed verdicts use volume pricing from $0.04 per verdict. Full pricing →
Built by Lucas de Lima and team. Meet the team →