Alibi docs
What Alibi proves and what it does not
Alibi shows that a record was not changed after it was anchored and which key signed each linked transaction. Entries newer than the last anchor are chained but not yet fixed on Solana.
It does not prove why an agent acted. Decision text is what the team chose to log, and the prompt hash only lets you check a prompt that is revealed later.
SDK and webhook fields
Each log call takes decision, prompt, model and an optional signature. The prompt is hashed on your server before sending when hash-only mode is on, so the text never reaches Alibi.
The webhook accepts the same fields as JSON with your agent API key in the Authorization header. Entries are ordered by arrival time on Alibi.
Anchors and intervention flags
An anchor is a memo program transaction holding the head hash, posted every 25 entries or once a day if the agent is active. You can check it on Solscan against the hash shown on the public page.
An entry is flagged as a human intervention when any signer of the linked transaction is not a registered agent key. Rotate keys in the Agents view so retired keys are recorded and do not trigger false flags.