How to verify 402registry before you pay

You should not have to take our word for anything on this page. Each point below can be checked from your side, with no payment and no account.

What one check is

A check fetches a public website the way AI crawlers fetch it — plain HTTP, no JavaScript — and reports what that fetch actually returned. It reads the page, robots.txt, the sitemap and the redirects, sends the same page request with the user-agent strings of 4 AI crawlers to see whether a firewall treats them differently, and has a language model read the page text. Every finding quotes the evidence it is based on, and every report carries its date and the rules version (2026-11-3).

The exact list of requests, the limits and how to opt out are on our crawler page.

What a passing check does not mean

Check the payment terms yourself

Ask for a check without paying:

curl -si https://402registry.com/buy/one

The answer is HTTP 402. The PAYMENT-REQUIRED header is standard base64 of a JSON object (x402 version 2, scheme exact). Before you sign anything, decode it and confirm:

ResourceProductamountPrice
/buy/oneOne check10000$0.01
/buy/catalogCatalog snapshot5000$0.005

Sign only if the decoded header shows exactly these values. The same terms are in our manifest, together with whether the till is open right now.

The receiving wallet

0xbc0dcc70d8b5d85541d86ffc68d988fd59c22e68 receives the payments of all four services run by the same person: 402registry, AISkills402, 402cron and 402post. Its history is public on the block explorer and on x402scan.

Payments from 0x146ea0b673978b1acc6f6517cb9de35c63e102c9 and 0xa340966d806f114483d671f6bf934daebbdff8dc are our own end-to-end tests, not sales.

Checked by a third party: PayAPI Market paid /buy/one once on 19 October 2026, saw the payment settle on Base, and lists 402registry as verified at payapi.market/api/402registry.

What we never ask for

If something that uses our name asks for any of these, it is not us. Please tell us at abuse@402registry.com.

How we treat the sites we check

Reports and the public catalog

A paid report is private: only the buyer gets its link, and it is never indexed. Nothing about a failed check is published. What is public is the catalog entry of a site that passed, its dated badge and its profile page.

Lost the link to your report? The report itself is not lost: it stays at its address for 400 days. Within 5 minutes of paying, resend the identical request with the same payment header. After that, the wallet that paid signs an EIP-712 Recovery message (domain { name: "402registry.com", version: "1", chainId: 8453 }) and sends POST https://402registry.com/recover with the subject nonce:0x… or tx:0x…; the answer is the report’s address. Free. The exact signing data and refusal codes are under recovery in /docs.

What we count

To see who uses the free lookup, the MCP server and the A2A endpoint, we keep daily counts: which endpoint or tool was used (for A2A, the method name), whether the site asked about is in the catalog, and the software name the client sends (its MCP client name, or the first word of its User-Agent). For a payment we refuse because it is on a network we do not accept, we count the network's name. For each new payment attempt, we count the outcome of a free on-chain pre-check of the signed authorization (it passed, the chain refused it, or the chain could not be reached). When someone opens a blog post through a link in one of our own social posts, we count the post and the network the link was posted on (the link carries the network's name). We do not record IP addresses, wallet addresses or the address of the site asked about. Daily counts are deleted after 90 days.

Who runs it

Georgi Kalchev — see who runs it on the home page, his professional profile on LinkedIn and his posts on X (@AiGenMaster).

Report a problem

Security issues, abuse, a wrong report or a site that wants out of the catalog: write to abuse@402registry.com. The same contact is in security.txt.