Your agents pay for things. Traceipt proves it.
Every payment your agent makes over x402 becomes a signed receipt you can hand to an auditor. Checkable for years. No trust in us required.
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, an auditor will not sign off on it, and the rules arriving this year assume you kept a record you never had a way to keep.
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.
Written for the rules showing up this year.
The EU AI Act (Article 12) wants high risk systems to log their actions automatically, in enough detail to reconstruct what happened. MiCA wants transaction records tied to their settlement and kept for years. A signed Traceipt per payment is that record.
We wrote down the honest mapping, and the parts we do not claim, so your lawyer has a short conversation instead of a long one.
This is engineering, not legal advice. Whether a deployment is in scope is a call for counsel.
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.