x402receipts

com.x402receiptsPublished by x402receipts.comv1.0.0Updated Oct 27, 2026

Record x402 agent purchases as reconciled, auditable receipts; verify any receipt on the ledger.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Records an agent's x402 purchases as reconciled, auditable receipts and verifies any receipt on the public ledger.

What you can do
  • Record receipts for paid x402 calls, capturing resource, amount, counterparty and transaction reference
  • Verify a receipt against the published ledger and its verification algorithm
  • Report service information about the receipts service
  • Reconcile recorded receipts against outgoing USDC payments on Base and Solana, flagging unmatched payments as exceptions
When to use it
Useful when an agent pays for x402 resources and you need an auditable spend trail, monthly statements for finance, or a way to prove a specific purchase to a third party.
Requirements
Runs locally over stdio, typically via npx. Optionally set X402RECEIPTS_EVM_PRIVATE_KEY (a 0x key holding USDC on Base) and X402RECEIPTS_SOLANA_PRIVATE_KEY (an ed25519 key holding USDC on Solana). Network access to the service endpoint is needed; no API key.
Before you install
The server asks for private keys that hold USDC and can spend them: recording costs USD 0.01 per agent wallet per day it records purchases, paid over x402 in USDC from the agent's own wallet. Keys are secrets; prefer a dedicated low-balance wallet. Receipt data is sent to the third-party service, which publishes verification pages and anchors log roots externally.

Installation

In SourceWeft

  1. Open x402receipts in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

x402receipts

Accounting infrastructure for autonomous spending. Every x402 purchase an agent makes becomes a receipt, reconciled against the on-chain transaction, with missing or unmatched payments flagged, monthly statements for finance, and evidence anyone can verify.

Use it

In code — one wrapper around the fetch your agent already pays with (npm i x402receipts-sdk):

ts
import { wrapFetchWithPayment } from "@x402/fetch";import { withRegister } from "x402receipts-sdk";
const register = withRegister(fetch, { endpoint: "https://app.x402receipts.com", payWith: () => pay });const pay = wrapFetchWithPayment(register, wallet);

As an MCP server (npx -y x402receipts-mcp): record_receipts, verify_receipt, service_info. See packages/mcp.

Over HTTP: POST https://app.x402receipts.com/api/v1/receipts — answers 402 with the x402 challenge; any x402 client pays it.

With an AI coding tool: paste the integration prompt into Claude Code or Cursor.

The format is an open standard

The record, its fingerprint, the append-only log above it, the anchor record and the verification algorithm are published as ARR-1 — Agent Receipt Record, released into the public domain (CC0). JSON Schemas are in spec/arr-1/. Implement it yourself, or check our implementation against it.

ARR-1 builds on existing standards rather than replacing them: the tree is the RFC 9162 profile used by Certificate Transparency, checkpoints are published as HCS-27 messages, accounts are named with CAIP-2/CAIP-10, and agents with HCS-14 identifiers.

In this repo

PathWhat
spec/arr-1/the ARR-1 specification and its JSON Schemas (CC0)
sdk/the x402receipts-sdk npm package (single file, no dependencies)
packages/mcp/the x402receipts-mcp MCP server
examples/plain Node, Vercel AI SDK, LangChain, OpenAI Agents
integrations/agentkit/Coinbase AgentKit action provider
integrations/x402-ecosystem/x402.org ecosystem entry

How it works

  1. Capture — the SDK records each paid call: resource, amount, counterparty, transaction reference, request/response fingerprints, delivery status, and the seller's signed receipt when it issues one (x402 offer-receipt).
  2. Reconcile — the connected wallets are read on Base and Solana; every outgoing USDC payment is matched to a receipt. What doesn't match is an exception, not an average.
  3. Prove — each night, the account's whole receipt log is hashed into one RFC 9162 Merkle tree and its root is written to the Hedera Consensus Service, linked to the previous day's root. Every receipt has a public verification page that redoes the maths in the browser.
  4. Report — the owner signs in with the wallet: spend by supplier, the register, CSV and signed JSON export.

Guide: https://x402receipts.com/guide.html · Status: https://app.x402receipts.com/status · Contact: [email protected]

MIT licensed.

Source: README.md at commit 0dbd9eb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 27, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts