Agent Receipts

Your agent says it's done. Prove it.

Agent Receipts gives the work your AI agent does a signed receipt: what went in, what came out, which model ran, how long it took and what it cost. Each receipt is signed with Ed25519 and linked to the one before it, so anyone can check it offline with your public key, without trusting you, your server or the agent. Change one byte and it no longer verifies.

claude mcp add agent-receipts -- npx @agent-receipts/mcp-server

receipts.webaes.com (what it is, install, and a page that signs itself) · demo.receipts.webaes.com (the dashboard with sample data) · verify.webaes.com (a real issuer's verify page) · by Webaes

Automatic receipts · Get started · Magic Folder · Memory · How it's different

---

Automatic receipts

Get a signed receipt for everything your agent does, without changing how you work.

Claude Code: one command. Every file edit, file write, notebook edit and shell command gets its own signed receipt, chained per session, and the session ends with a summary (actions, files touched, duration):

npx @agent-receipts/cli hooks install            # or --scope project / --scope local

It shows the change to Claude Code's settings.json and asks first; hooks uninstall takes it out again. Or install it as a Claude Code plugin:

claude plugin marketplace add webaesbyamin/agent-receipts
claude plugin install agent-receipts@agent-receipts

Any MCP server: the proxy. Put it in front of a stdio MCP server and every tool call through it is signed (mcp.<server>.<tool>), while every message passes through unchanged:

claude mcp add fs-receipted -- npx -y @agent-receipts/cli proxy --name fs -- npx -y @modelcontextprotocol/server-filesystem ~/Documents

Receipts hold hashes only (inputs, outputs, and each changed file), never commands, file contents or results. See them in the dashboard's Sessions view (npx @agent-receipts/dashboard) or check one with agent-receipts verify-chain <session id>. Setup for Claude Desktop and Cursor: CLI README.

What these receipts do and don't prove:

• They prove what Claude Code (or the MCP client) reported, signed outside the agent. The hook and the proxy run as separate processes, and each receipt is signed the moment the tool finishes, so the agent can't edit a receipt afterwards without breaking it. They don't prove the work was right, only what was done and that the record hasn't changed.
• claude -p can stop the last one. In a scripted run, Claude Code stops background hooks still running when the run ends, so a tool call in the last moment of a run can go unrecorded.
• The computer's owner controls the keys. Receipts are signed with keys in ~/.agent-receipts on your machine. They show the record wasn't changed after signing; someone who controls that machine could sign a false one. To show others, publish your public key so they know which key to trust.
• stdio MCP servers only for now. Remote (HTTP) MCP servers aren't covered yet.

Proof

Every memory observation and every action your agent tracks produces a receipt — a signed JSON document with:

• Ed25519 signature over every field (receipt format v2) — tamper-proof, independently verifiable
• Input/output hashes — proves exactly what went in and came out (raw data never stored)
• Timestamps — when it happened, when it completed
• Agent ID — which agent did it
• Link to the previous receipt — the hash of the one before it, so a missing receipt shows
• Provenance chain — trace any memory back to the conversation that created it

This isn't logging. Logs are mutable text files the agent writes about itself. Receipts are cryptographic proof that a third party can verify without trusting you, your server, or the agent.

Everything runs locally

npx @agent-receipts/mcp-server

That's it. No API key. No account. No cloud. No monthly fee. No data leaving your machine. SQLite database in ~/.agent-receipts/. Works offline. Needs Node.js 22.16 or later.

Get Started

Needs Node.js 22.16 or later.

1. Add the MCP Server

Claude Code:

claude mcp add agent-receipts -- npx @agent-receipts/mcp-server

Claude Desktop (claude_desktop_config.json) / Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "agent-receipts": {
      "command": "npx",
      "args": ["@agent-receipts/mcp-server"]
    }
  }
}

2. Add the System Prompt

This tells your agent when to observe memories, recall context, and track actions — so it works automatically:

npx @agent-receipts/cli prompts claude-code

Copy the output into your project instructions or system prompt.

3. Start Using It

Your agent will now:

• Call memory_context at the start of sessions to load what it knows about you
• Call memory_observe when it learns something worth remembering
• Call track_action when it performs significant actions
• Sign everything with Ed25519

4. See What's Happening

npx @agent-receipts/dashboard    # Web UI at localhost:3274
npx @agent-receipts/cli stats    # Terminal overview
npx @agent-receipts/cli memory entities  # See what your agent remembers

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗