An invoice is a claim. A Traceipt is proof.
Every payment your agent makes becomes a signed receipt anyone can verify, that no one can forge, alter, or backdate. Without trusting us.
The problem is boring, which is exactly why it bites.
An agent makes ten thousand tiny payments a month. Your books see ten thousand transactions with no context. No invoice. No vendor. No reason. Finance cannot reconcile it, and an auditor will not sign off on a number with no evidence behind it.
The payment rail is solved. The record was not. That gap is the whole reason Traceipt exists.
We kept watching teams wire up agent payments, then quietly panic about the paper trail. So we built the paper trail. A receipt that gets signed the moment a payment clears, chained so it cannot be edited later, and anchored so anyone can prove it existed.
It does one thing, and it refuses to lie about it.
Built by a small team that got tired of the spreadsheet.
From a 402 to a receipt that outlives the database.
- 01
The agent hits a paywall
A paid endpoint answers with
402 Payment Requiredand a price. - 02
It pays, the money clears
The agent settles in USDC on Base. A real transfer, on a real chain.
- 03
Traceipt checks, then signs
We confirm the transfer actually happened on chain, then sign a receipt that ties the payment to what was bought, who paid, and who was paid.
- 04
It gets chained and anchored
Each receipt joins a tamper evident chain and is folded into a Merkle root we publish on chain.
- 05
Anyone can check it, later
Signature, chain, and anchor all verify offline against keys we publish. The receipt is good long after we are out of the room.
What you actually get.
01Signed, checkable by a stranger
Every receipt is Ed25519 signed and verifies in any language against the keys we publish. No SDK, no calling home.
02It only exists if the money moved
We confirm the transfer on chain before we sign. There are no receipts for payments that never happened.
03Nobody can forge one
Payer and payee are cryptographically bound, so you cannot write a receipt for a payment you did not make or receive.
04An invoice a human can file
Every receipt renders to a VAT aware PDF with a scan to verify code. The machine checks the math, the accountant files the paper.
Built for the audit, ahead of the mandate.
Rules for keeping provable records are arriving, unevenly. The EU AI Act asks high risk systems to log what they do, and the EU and South Korea now have AI laws in force. Crypto record keeping rules like FATF and MiCA are global, but they target regulated intermediaries above dollar thresholds, not cent sized agent payments.
So we will say it plainly: no rule today names a receipt like this. We are ahead of the mandate, not compelled by it. What Traceipt gives you is an audit ready, independently verifiable trail for machine payments, for the day you have to prove one.
This is engineering, not legal advice, and not a compliance guarantee. Whether a deployment is in scope is a call for counsel.
The questions your auditor will ask.
What is Traceipt?
Traceipt turns every x402 payment an AI agent makes into a signed receipt. When a payment settles in USDC on Base, Traceipt confirms the transfer on chain, then signs a receipt that ties the payment to what was bought, who paid, and who was paid. Receipts are chained tamper-evident and anchored in a Merkle root published on chain.
How do I reconcile thousands of AI-agent micropayments?
Each receipt carries the context your books are missing: the purchase, the payer, the payee, and the on-chain transaction. Every receipt also renders to a VAT-aware PDF with a scan-to-verify code, so the machine checks the math and the accountant files the paper.
Can I verify a receipt without Traceipt?
Yes. Signature, chain, and anchor all verify offline against published keys, in any language, with no SDK and no calling home. The receipt stays checkable long after we are out of the room. Try it now — verify a receipt in your browser.
Can a receipt be faked or edited later?
No. A receipt only exists if the money actually moved — the transfer is confirmed on chain before signing. Payer and payee are cryptographically bound, each receipt joins a tamper-evident chain, and the chain is folded into a Merkle root published on chain, so edits and forgeries fail verification.
What does Traceipt run on, and can I self-host?
Traceipt runs on x402, Base, and USDC, with one dependency. You can host it yourself if you would rather.
Does Traceipt help with the EU AI Act and MiCA?
The EU AI Act (Article 12) wants high-risk systems to log their actions automatically, and MiCA wants transaction records tied to settlement and kept for years. A signed Traceipt per payment is that record. This is engineering, not legal advice — whether a deployment is in scope is a call for counsel.
New to this? Start with What is an x402 receipt? Comparing options? Read Traceipt vs x402b.
Start keeping receipts your auditor will accept.
We are onboarding the first teams on testnet now. Tell us what your agents are buying, and we will get you issuing real receipts this week.
Runs on x402, Base, and USDC. One dependency. Host it yourself if you would rather.