open source
Receipts for AI-agent trades
A payment proves money moved. Our receipts record what was offered and what the buyer says arrived. Run the code yourself, so you do not have to believe us.
Free
Open
tokenizen.nl · Eindhoven
AI agents now pay each other. Our open-source receipts record what the seller offered and what the buyer says arrived, each signed by its own side, so anyone can check them. We also find leaks in real software and show the numbers. In an open-source AI tool with more than 10,000 stars, our merged pull request cut the leaks of fake secret keys in its test from 20 of 68 cases to 4. Check your repository free in a minute, see the price of a smart contract scan before you pay, and keep a log whose timestamp is outside our control. Every number below links to the commands, so you can run it yourself.
Check your repository See what we offertokenizen
Seven things. Pick one to read what you get, how you check it and what it is not.
open source
A payment proves money moved. Our receipts record what was offered and what the buyer says arrived. Run the code yourself, so you do not have to believe us.
Free
Open
open source
Compares a company name with public sanctions lists and returns a signed, dated answer. If a list did not arrive, it says so and never says safe.
Free
Open
free
See in a minute what your public repository or payment endpoint shows.
Free
Open
early access
Every week the same eight signals for your repositories, written into a log with a timestamp outside our control.
9.95 or 29.95 euro per month, VAT included
Open
on request
We read your pipelines and automation the way an attacker does, and tell you what we find.
No fixed offer yet
Open
pay per scan
Our cyber security scan reads smart contract code and returns possible weak spots for you to check. It finds some of what a human audit finds, and we publish how much. People pay by card or iDEAL, AI agents pay over x402.
77.4% of the known High bugs found by six of our research runs together (24 of 31). The scan you buy found 14 of 20 on five audits. Every verdict is open.
From 2 euro per scan
Open
If you build AI agents that pay or get paid, someone will ask you what exactly your agent got for the money. We check the payment flow from the outside and give you a short report with evidence that your customer can re-run.
A first step can be one of these:
What others wrote about our work:
Facts from their own pages, not recommendations. Each link opens without a login. We checked all three on 21 November 2026.
Tell us where you stand. We reply within two working days with a scoped proposal and a fixed price. No paying customers yet, we say so, and we show our work.
Contact usEvery number has a source, a date and a way to run it again. When a number gets old, this page says so.
| Number | What it says | Checked by | Measured | Check |
|---|---|---|---|---|
| 7 audits | Our research scan runs on 7 audits come with their verdict files and a script that recounts them, the leader's higher score included. Someone outside our team has already recounted them | Checked by someone outside our team | Check it yourself | |
| 3 of 3 | Test receipts on which a second checker, written separately by the author of an open x402 receipt proposal, reached the same result as ours | Checked by someone outside our team Test networkOur own test | Check it yourself | |
| 2 of 2 | One receipt for a paid call to our service on a test network, signed by us and countersigned by the party that paid, with its id and both signatures recomputed by a second implementer. The check the call ran came back as not passed, and the receipt says so | Checked by someone outside our team Test network | Check it yourself | |
| 109 | Public repositories in ten EU countries measured on eight security signals, our misses published | Our own measurement | Check it yourself | |
| 0 of 600 | x402 catalogue records we sampled from one index declare the offer-receipt extension. Ours signs offers, and you can check one yourself | Our own measurement | Check it yourself | |
| 1 payment | One real payment on Base mainnet from a test agent of ours to our own service, with the transactions open to check | On-chain Our own test | Check it yourself | |
| 97 of 105 | Our scan missed 97 of 105 known findings in its run on eight audit contests. | A limit we publish | Check it yourself |
Reliability
Security
Some of what we found we may show, some we may not, and some will follow when the fix is out.
public
A published GitHub security advisory, severity High, with our account credited as reporter.
Open the advisoryour own records
Reports confirmed or assessed by two known technology companies. At two more, the report was received or fixed without an answer to us. The names stay private.
planned
Planned, not live yet: each report we file would get a date and a fingerprint on a public list, without its content. When the fix is out we would publish the dossier, and anyone could see that we had it on that date.
Mission and vision
Mission
We build checks, publish how they were made and publish where they fail.
Vision
Software, agents and payments that prove what they say, so that trust is something you measure.
Free
Type owner/name of a public GitHub repository and see which of the eight signals are visible in it.
Public GitHub repositoryWe read public pages only and store no report.
The numbers that do not flatter us sit on the same page as the ones that do.
Conversation
Start with a conversation about where you stand. Ask for our measurements and we show how each one was made.
Write to us Who we areThe photographs on this page are illustrations made with AI.