Our crawler.
Who we are, what we read, and how to be removed. If you found this page from a User-Agent in your logs, that was us.
What the crawler reads
Agent402 publishes an index of services that advertise machine payments over x402 or MPP. To build it we read the discovery documents a service publishes for exactly this purpose: /.well-known/x402, /openapi.json, /llms.txt, and the HTTP 402 challenge a paid route returns to an unpaid request.
That is all. We do not log in, we do not submit forms, we do not read anything behind a paywall, and we do not pay to see more. A 402 challenge is a public advertisement of price and payment rails - answering one with no credential is the ordinary way to read it.
How it behaves
The crawler identifies itself on every request as Mozilla/5.0 (compatible; Agent402/1.0; +https://agent402.tools/crawler), so it can be recognised, rate-limited or blocked by name.
It honours robots.txt, including for the discovery paths above. It re-reads an origin about every thirty minutes, backs off on errors, sends conditional requests so an unchanged document costs a single 304, and caps what it will read from any one response.
If our crawler is causing you a problem, a Disallow for that User-Agent stops it and needs no message from us. Email works too.
Getting removed
Email mike@agent402.tools from an address at the domain, or open an issue, and we will remove the origin from the index and stop crawling it. We do not require a reason and we do not argue about it.
Blocking the User-Agent in robots.txt has the same effect and takes immediate effect on the next cycle without waiting for us.
What we publish, and what we do not
The public index carries what a service advertises about itself: its endpoints, the prices and payment networks it declares, whether our own probe could reach it, and the payout addresses it names in its own challenges. Payout addresses are public infrastructure - they appear in every challenge the service hands to every buyer.
We publish counts of settled payments per payee, read from public chains. We never publish who paid: buyer figures are counts only, and no roster of payers leaves our systems. That rule is enforced in code, not by convention.
Measurements made by third parties are not redistributed. Where our pages display someone else's figures we label them as theirs, and they are excluded by name from any dataset we distribute.
Corrections
If a row about your service is wrong, tell us and we will fix it. Several improvements to how prices are read came from operators who checked their own row and found it stale - that feedback loop is the main reason the index is accurate, and it is why the index is free to read.