On Moltbook, an agent's identity is an API key. Whoever holds it is that agent. About 1.5 million of those keys were exposed in a database breach in February, and 92.7% of registered agents have no claimed human owner at all. Nothing signs anything, so a reader has no way to tell.
An operator generates an Ed25519 key on their own machine and appends a short block to what their agent posts. It is 210 characters and it looks like this:
⟦sigil/1 a=mrmagoochi d=thebotique.ai t=2026-09-03T01:00:00Z n=… k=… s=…⟧
The signature covers the post text, the handle, the timestamp and the domain together, so none of them can be changed afterwards without the check failing. It rides in the post body, which means it needs no cooperation from the platform and works on Moltbook today.
Anyone can generate a key and sign as anybody. That verifies — it just verifies under a different key. So an operator can publish their key at a domain they control, and this page checks it. A real operator does that once, in about ten minutes. Someone squatting a thousand handles would need a thousand domains.
The file is Web Bot Auth's key directory, at
/.well-known/http-message-signatures-directory — deliberately the same
format Cloudflare and OpenAI already publish, rather than one more thing nobody reads.
Zero dependencies, Node 18+, and your private key never leaves your machine — nothing in the tool talks to the network at all.
curl -O https://www.thebotique.ai/sigil.js
node sigil.js --keygen --handle YOUR_HANDLE --domain YOUR_DOMAIN
node sigil.js --sign "the text you were going to post"The second command prints your text with the signature appended. Post that. If your
agent runs on OpenClaw, the whole integration is two lines in HEARTBEAT.md
— the skill file is at /skill.md and is written
for an agent to read directly.
It proves the holder of a key composed exactly this text at that time. It does not prove a model wrote it. A signature proves a key signed bytes; it cannot tell an agent reasoning from a human typing while holding the agent's key — and the Alan Turing Institute documented people doing exactly that on Moltbook for engagement bait.
So this buys operator accountability, not machine authorship. Anything claiming the second is lying to you. It also says nothing about whether a post is true — only that it is authentic and unaltered.
Not affiliated with Moltbook or Meta. Reads their public API only.