Receipts for x402 agent payments

Your agents pay for things. Now they keep the receipts.

No signup, no API key. Your agent pays $0.002 per receipt from its own wallet — on Base, Solana or Hedera — and that wallet becomes its account. You sign in with the same wallet and get monthly statements of everything it bought, each one anchored on Hedera.

Pays on Base Solana Hedera
September 2026 Example
41,230 purchases · €812.40
02/09 14:22api.exa.ai/search€0.004Delivered
05/09 09:41models.inference.io/v1€0.018Delivered
11/09 18:03data.compass.eu/geo€0.002Delivered
14/09 09:11agent-search-v2€0.020No receipt
21/09 23:58api.exa.ai/search€0.004Delivered

3 payments with no receipt, found by reconciling the register against the chain.

Illustrative example, not live customer data.

The problem

At month end the bank shows €812 going out. For what?

Nobody clicked confirm

Agents buy data, searches and model calls half a cent at a time, thousands of times a day, with no human in the loop.

The only logs are self-written

Handing an auditor logs your own system wrote is handing them a notebook in your own handwriting instead of invoices.

You pay even when nothing arrives

A large share of x402 traffic is test or wash activity. At half a cent nobody checks. Across a hundred thousand calls it stops being half a cent.

How it works

Three steps. Two of them happen without you.

01

The agent pays, and that's the signup

no form · no key

Paste one prompt into the AI tool that runs your agents. From then on, every purchase the agent makes is reported to x402receipts and paid for from the agent's own wallet: $0.002 per receipt, on Base, Solana or Hedera. The first payment creates the account; the wallet is the identity.

02

Every receipt gets proven

automatic

What was bought, from whom, for how much, and whether it was delivered — fingerprinted and written to the Hedera Consensus Service within minutes. Nobody, us included, can change it afterwards.

03

You sign in with the wallet

whenever you like

Sign one message with the same wallet and the register is yours: monthly statements of everything the agent bought, the export for your accountant, the proof link for every line. Have more agents? Link their wallets from inside.

Why it holds up

Evidence an auditor has no reason to doubt.

Every purchase, not a sample

We record the half-cent payment too. Sampling gives you a statistic; an auditor wants a ledger.

You don't have to trust us

We reconcile receipts against the payments that actually left your wallets and show you the gaps — including the ones that are our fault.

No crypto to handle

You pay a subscription in euros. No accounts to open, no tokens to buy, not one more wallet than you already have.

What you see

Monthly statements, built for whoever keeps the books.

September 2026 Example
Export the month
Spent€812.40
Purchases · suppliers41,230 · 14
Missing a receipt3

Where it went

Data & search APIs€410.20
Model inference€380.00
Automation & other€22.20

41,230 payments left your wallets. 41,227 receipts recorded.

All 3 missing ones come from agent-search-v2 — most likely the SDK was never installed there.

Under the hood

For the people who check before they sign.

Your data never leaves

We record a cryptographic fingerprint of the request and the response, never the content. The fingerprint can't be reversed — but if the content changes, it no longer matches.

Timestamps we don't control

Fingerprints are written to the Hedera Consensus Service: order and time certified by a third-party network, and nothing can be deleted. Neither you nor we can rewrite the past.

Fixed cost, priced in dollars

A write costs $0.0008 and the price doesn't track a crypto market. That's why we can afford to record every single purchase instead of a sample.

We never touch the payment

We're not an intermediary and the money doesn't pass through us. If our service goes down, your agents keep buying exactly as before.

Works with The standard x402 clients — @x402/fetch, @x402/axios — and agents buying over MCP. Your payments stay where they already are: Base, Solana, Hedera.

Pricing

The agent pays. $0.002 a receipt.

No account to open, no card, no monthly minimum. A thousand receipts are two dollars, paid in USDC by the agent itself.

Pay per receipt

$0.002/ receipt

Paid by the agent, from its wallet, in USDC on Base, Solana or Hedera. Nothing is billed to you.

Get started

Prefer a flat fee? Teams can use an API key at €19 / month per workspace, unlimited receipts.

Everything included

Unlimited payments recorded
Proof of delivery on every purchase
Full reconciliation against the chain
Signed monthly export
Audit-ready export packs
24 months retention
Unlimited seats · SSO
Sign in with the wallet, link more wallets

Writing a proof to Hedera costs us a fraction of a cent, which is why the price can stay this small. No hidden tiers: the same $0.002 whether the agent buys ten things a month or a million.

Questions

The ones worth asking first.

Does the agent need an account?

No. Its first paid receipt creates one, keyed to the wallet it paid from. There is nothing to fill in and no key to store. You sign in later with the same wallet; if you have several agents, you link their wallets from inside.

Which wallets and networks?

Base, Solana and Hedera for paying. For signing in: Phantom (Solana and Base), MetaMask, Coinbase Wallet, Rabby — any wallet that can sign a message. Hedera wallets can pay; signing in with one is coming.

Does this make us EU AI Act compliant?

No — and be wary of anyone who says it does. Compliance stays your obligation and no vendor can take it on for you. What we give you is the evidence to bring: a complete register, independently timestamped, that you didn't write yourself.

Do you need to see what our agents buy?

No. The content stays on your systems. All we receive is a fingerprint, and the content can't be reconstructed from it.

What happens if your service goes down?

Your agents keep buying. We're not in the payment path and we can't block it: we record alongside it, and catch up on whatever we missed when we're back.

Does it cover agents paying by card or API key?

Not yet. Today we cover purchases made over x402, where the payment itself is public and verifiable. That's a real limit of the product and we'd rather you hear it now than later.

The agent prompt

Paste this into the AI tool that runs your agents.

Claude Code, Cursor, Copilot — whichever built them. It contains everything: where the SDK is, where the line goes, how the agent pays. No key inside, so it's safe to share.

Prompt
Connect this project's AI agents to x402receipts, a service that records every x402 purchase they make so we can prove it later. There is no API key: the agent pays x402receipts per receipt (USD 0.002 each, in USDC) from the same wallet it already uses for x402, on Base, Solana or Hedera.

Context
- x402receipts endpoint: https://app.x402receipts.com

Do this
1. Download the x402receipts SDK into the project: fetch https://app.x402receipts.com/sdk and save it as lib/x402receipts-sdk.ts (or wherever shared code lives). It is one TypeScript file with no dependencies.
2. Find where the agents pay over x402: the place that calls wrapFetchWithPayment from "@x402/fetch" (or withPaymentInterceptor from "@x402/axios", or any fetch wrapper that handles HTTP 402).
3. Wrap the fetch passed to that payment wrapper with withRegister, and give withRegister the paying fetch so it can pay for its own uploads:
   const register = withRegister(fetch, { endpoint: "https://app.x402receipts.com", payWith: () => pay });
   const pay = wrapFetchWithPayment(register, wallet);
   (payWith is lazy on purpose: it may reference the wrapper that wraps it.)
4. Change nothing else about how the agents work. withRegister never throws and never delays a request; it reports in the background.
5. Verify: run one real paid request. Within a minute, POST https://app.x402receipts.com/api/v1/receipts from the agent will have been paid and answered 200; its JSON body contains workspace.claimUrl — print it. Whoever owns the wallet opens https://app.x402receipts.com, signs in with that wallet, and sees the register.

When you're done, tell me which files you changed, show the diff, and print the claimUrl.

Then sign in with the wallet.

Once the agent has paid for its first receipt, its wallet is an account. Sign one message with it — Phantom, MetaMask or Coinbase Wallet — and the register is yours: statements, exports, proofs.