Agent Receipts
The agent-receipts server creates, manages, and verifies cryptographically signed receipts for AI agent actions, providing an immutable audit trail of what an agent did, with what inputs and outputs.
Core Receipt Operations
track_action— Record a completed action with automatic SHA-256 hashing of input/output, capturing model, cost, latency, token usage, confidence, tags, tool calls, and custom metadatacreate_receipt— Create a receipt with pre-computed hashescomplete_receipt— Finalize a pending receipt with execution results (status, output hash, cost, latency, errors)get_receipt/list_receipts— Fetch a single receipt by ID or browse all receipts with filtering (agent, status, chain, action, tag, environment, type) and pagination/sorting
Cryptographic Verification
verify_receipt— Confirm a receipt's Ed25519 signature is valid and untamperedget_public_key— Export the signing public key for offline third-party verification
Chaining & Lineage
get_chain— Retrieve all receipts in a multi-step pipeline, ordered chronologically
AI Judge / Quality Evaluation
judge_receipt— Evaluate a receipt against a custom rubric with weighted criteria and passing thresholdscomplete_judgment— Record evaluation results (verdict, per-criterion scores, reasoning, confidence)get_judgments— Retrieve all judgments for a specific receipt
Constraints & Compliance
Attach constraints (e.g.,
max_latency_ms,max_cost_usd,min_confidence) when tracking actions to automatically flag pass/fail results
Maintenance & Billing
cleanup— Delete expired receipts past their TTL, with optional dry-run previewgenerate_invoice— Produce invoices from completed receipts within a date range, with grouping (by agent, action, or day) and output formats (JSON, CSV, Markdown)
Onboarding
get_started— Display usage examples and documentation for all tools
Agent Receipts
Your AI agent remembers everything — and you can prove it.
Persistent memory for AI agents, backed by cryptographic receipts. Every fact your agent learns is signed, traceable, and independently verifiable. No cloud required.
Try the Interactive Demo · Install in 30 Seconds · How It's Different
The Problem
You're building with AI agents. Claude Code refactors your auth module and says "done, all tests pass." Your agent generates a customer quote and says it applied the right pricing. Your assistant remembers your preferences from last week — but you can't see why it thinks that, or whether it's right.
Three things are broken:
Agents forget everything between sessions. Every conversation starts from zero. Context is lost. You re-explain the same things.
When agents do remember, you can't see inside. Platform memory is a black box. You can't see what it stored, when, or why. You can't correct it, export it, or verify it.
There's no proof of what agents actually did. Logs are mutable. Agents write their own logs. "I updated 3 files and all tests pass" — did it? You're trusting the agent's word about its own work.
What Agent Receipts Does
Memory that actually works
Your agent gets structured, persistent memory across sessions — people, projects, tools, preferences, facts. Not a flat key-value store. An entity-observation graph where every fact links to the conversation that created it.
# Your agent learns something
memory_observe → "User prefers TypeScript, uses Neovim, building a SaaS called ModQuote"
# Next session, it already knows
memory_context → loads everything: entities, observations, relationships, preferences
# You can search it
memory_recall → "what tech stack does the user prefer?" → structured results
# You can forget (and the forget itself is tracked)
memory_forget → soft delete with audit trailThe agent handles this automatically when you add the system prompt. You don't manage memory manually.
Proof that's actually proof
Every memory observation and every agent action produces a receipt — a signed JSON document with:
Ed25519 signature — 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
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-serverThat's it. No API key. No account. No cloud. No monthly fee. No data leaving your machine. SQLite database in ~/.agent-receipts/. Works offline.
Why This Exists
I was building ModQuote — a multi-tenant SaaS where AI agents generate quotes for automotive protection shops. Real money, real customers, real liability.
When Claude generated a $2,400 PPF quote, I needed answers: What vehicle data did it receive? What pricing rules did it apply? If a customer disputes the price, can I prove what happened — not with a log entry the agent wrote about itself, but with cryptographic proof?
I looked at the existing tools:
Mem0 — great memory, but no proof. It remembers things, but can't prove when or why it learned them. Memories are mutable.
Langfuse — great observability, but it's tracing, not proof. Logs are internal to your system, not verifiable by third parties.
Zep — temporal knowledge graph, but hosted and opaque.
None of them could answer: "Prove to someone outside your system that this specific agent took this specific action with this specific input at this specific time."
So I built Agent Receipts. Now every quote generation is a signed receipt. Every memory has a provenance chain. And when someone asks "how did the agent come up with that number?" — I hand them a receipt they can verify themselves.
How It's Different
Agent Receipts | Mem0 | Langfuse | Zep | |
Memory | Signed entity-observation graph | Smart extraction + consolidation | No memory | Temporal knowledge graph |
Proof | Ed25519 signed receipts | None | Mutable traces | None |
Verification | Offline, by anyone, no server | No | No | No |
Infrastructure |
| Requires LLM for extraction | Cloud or self-host | Cloud API |
Cost | Free forever (local) | Free tier, then paid | Free tier, then paid | Paid |
Export | Portable bundles with crypto verification | Export available | API export | No |
Audit trail | Immutable receipt chain | Mutable | Mutable logs | Mutable |
Agent Receipts isn't a better version of these tools. It's a different thing.
Mem0 answers: "What does my agent remember?" Langfuse answers: "What happened in my LLM pipeline?" Agent Receipts answers: "Can you prove it?"
Get Started
1. Add the MCP Server
Claude Code:
claude mcp add agent-receipts -- npx @agent-receipts/mcp-serverClaude 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-codeCopy the output into your project instructions or system prompt.
3. Start Using It
Your agent will now:
Call
memory_contextat the start of sessions to load what it knows about youCall
memory_observewhen it learns something worth rememberingCall
track_actionwhen it performs significant actionsSign 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 remembers5. Try Before Installing
Run the interactive demo → — experience memory, verification, and bundle export in 60 seconds. No install required.
What's Inside
24 MCP tools — memory, actions, verification, constraints, judgments, invoicing, bundles
21 SDK methods — full TypeScript API
14 CLI commands + 9 memory subcommands — terminal-first
18 dashboard pages — receipts, memory graph, chains, agents, constraints, judgments, invoices
492 tests — zero TypeScript
any, zero ESLint warningsEd25519 + SHA-256 — via
@noble/ed25519(audited, pure JS)SQLite + FTS5 — local-first with full-text memory search
Portable Memory Bundles
Export your agent's entire memory as a single verifiable file:
npx @agent-receipts/cli memory export > my-project.bundle.jsonThe bundle includes every entity, observation, relationship, the receipts that created them, and the public key needed to verify everything. Hand it to another agent, another team, or another Agent Receipts instance — they can verify every fact without trusting you.
Links
Try it in your browser — 60 seconds | |
See the full dashboard with sample data | |
Receipt anatomy, memory model, ModQuote story | |
All 6 packages |
Action Tracking
ar.track(params)— Track a completed action with automatic hashingar.start(params)— Create a pending receiptar.complete(receiptId, params)— Complete a pending receiptar.verify(receiptId)— Verify a receipt's Ed25519 signaturear.get(receiptId)— Get a receipt by IDar.list(filter?)— List receipts with filtering and paginationar.getPublicKey()— Get the signing public keyar.getJudgments(receiptId)— Get judgments for a receiptar.cleanup()— Delete expired receiptsar.generateInvoice(options)— Generate invoice from receipts
Memory
ar.context(params?)— Get full memory context dump for session initar.observe(params)— Store a memory observation (always receipted)ar.recall(params?)— Search memories (quiet by default,audited: truefor receipt)ar.forget(params)— Soft-delete observation or entity (always receipted)ar.entities(filters?)— List entitiesar.relate(params)— Create entity relationshipar.provenance(observationId)— Get provenance chainar.memoryAudit(params?)— Memory audit report
Bundles
ar.exportBundle(params?)— Export portable, verifiable memory bundlear.importBundle(bundle, params?)— Import and verify a memory bundle
Aliases
ar.emit(params)— Alias fortrack()
Tool | Description | Key Parameters |
| Track an agent action with automatic hashing |
|
| Create a receipt with pre-computed hashes |
|
| Complete a pending receipt with results |
|
| Verify the cryptographic signature |
|
| Retrieve a receipt by ID |
|
| List receipts with filtering |
|
| Get all receipts in a chain |
|
| Export the Ed25519 public key | — |
| Start AI Judge evaluation |
|
| Complete a pending judgment |
|
| Get all judgments for a receipt |
|
| Delete expired receipts |
|
| Generate invoice from receipts |
|
| Getting-started guide | — |
| Full context dump for session init |
|
| Store a memory observation |
|
| Search stored memories |
|
| Soft-delete observation or entity |
|
| List known entities |
|
| Create entity relationship |
|
| Provenance chain for observation |
|
| Memory operations audit report |
|
| Export portable memory bundle |
|
| Import and verify memory bundle |
|
Command | Description |
| Create data directory and generate signing keys |
| Display, export, or import signing keys |
| Pretty-print a receipt |
| Verify a receipt signature |
| List receipts with filters |
| Show receipt chain |
| List judgments for a receipt |
| Delete expired receipts |
| Aggregate receipt statistics |
| Export receipts as JSON |
| Generate invoice |
| Seed demo data |
| Watch for new receipts |
| Setup guide (claude-code, cursor, system) |
| Memory context summary |
| Store observation |
| Search memories |
| List entities |
| Forget observation or entity |
| Memory audit report |
| Provenance chain |
| Export memories as JSON |
| Import memories |
Environment Variable | Description | Default |
| Data directory path |
|
| Default agent ID |
|
| Organization ID |
|
| Environment label |
|
| Ed25519 private key (hex) | Auto-generated |
Storage:
~/.agent-receipts/
├── keys/
│ ├── private.key # Ed25519 private key (mode 0600)
│ └── public.key # Ed25519 public key
├── receipts.db # SQLite database (receipts + memory)
└── config.json # Agent and org configurationPackages
Package | Description |
Zod schemas and TypeScript types | |
Ed25519 signing, verification, key management | |
MCP server with 24 tools | |
TypeScript SDK (21 methods) | |
Command-line interface | |
Mission Control web UI |
Roadmap
Cloud tier — team dashboards, multi-agent memory sync, cross-org verification
Semantic recall — embedding-powered memory search
Framework adapters — LangChain, CrewAI, AutoGen integrations
Cross-org trust bridges — two organizations verifying each other's agent receipts
License
MIT
Built by Amin Suleiman — building ModQuote and Agent Receipts.
Appeared in Searches
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/webaesbyamin/agent-receipts'
If you have feedback or need assistance with the MCP directory API, please join our Discord server