Verification for every AI agent.

A successful tool response is not independent proof of delivery. Receipts records the destination account and object, the action, the approved package digest, and when the observation was made. It keeps two evidence paths clearly separate.

GitHub issues is the first independent provider connector. It verifies the exact repository and issue ID, then checks the title and body against the approved package. Labels, comments, assignees, and issue state are outside that package identity. Read the connector details.

Receipts binds the observed object to the exact approved package. When delivery is uncertain, its executor wrapper blocks another write and supports reading back the existing object. A verdict never authorizes an automatic retry or a second write.

completeA matching observation.

An observed destination object is bound to the approved package. Check its proof source and observation time; recheck when you need a current view.

delivery_unknownRead before another write.

The action may have landed, even if its response was lost. Read the destination to find the existing object. Do not automatically retry or create a second one.

package_unverifiedCheck the existing object.

An object exists, but its approved package binding is missing or does not match. Inspect and bind that object instead of creating another.

prewriteResolve what stopped the action.

There is no destination evidence, or the action is confirmed never to have reached it. Rearm only with affirmative prewrite evidence, a fixed cause, a new digest, and a new attempt.

These protections apply to writes routed through the executor. Cooperating writers must share a durable audit store and retain the original action and destination identity. Receipts records host authorization; it does not authenticate your approval UI or control code outside the wrapper.

Connect through MCP, the TypeScript SDK, or REST. Build verification into workflows with Claude, ChatGPT, Cursor, Grok, LangChain, or your own agent, using the interface your host supports.

Setup depends on the host; these are integration interfaces, not native integrations with every named tool. A Claude plugin is included. Hosted chat connectors need a separately secured gateway; the included HTTP and REST servers listen locally.

The audit stays on your disk. Destination content is read in local memory to calculate its digest; the audit does not store issue titles, bodies, or credentials. There is no Receipts-hosted service or telemetry.

Entries are hash chained. A retained head checkpoint helps detect local edits or truncation. This is not a blockchain, a provider signature, or an externally witnessed proof: someone who can rewrite both the log and its checkpoint can forge the history.

A receipt records an observation at a particular time. The destination can change later. Recheck to append a fresh observation without rewriting the original receipt.