Verify your payout address
An x402 or MPP listing can name any wallet (or none), and nothing in either protocol proves the wallet getting paid belongs to whoever runs the endpoint. This page helps you prove it, for free, in about five minutes. Once you do, the board shows a green mark on your endpoints, and if one ever asks to be paid anywhere else, it gets flagged right away.
How it works
You publish two things that only the real owner could publish together:
Your site or domain names the address. Either a small file on the same host as your endpoints, or a DNS record on your domain. That shows whoever controls the site chose this wallet.
The wallet signs a message naming your domain. That shows whoever holds the wallet agrees. It's a free signature, not a transaction. Nothing is sent and no gas is spent.
The board checks once a day. DNS is the stronger option: someone who breaks into a web server usually can't change your domain's DNS. If your endpoints live on shared hosting (onrender.com, workers.dev, vercel.app and similar), use the file.
Make your proof
For the file: the exact host your endpoints run on. For DNS: that host or your main domain (a record on example.com covers api.example.com too).
The address your 402 responses ask to be paid to.
Fill in the domain and address above.
No browser wallet? Sign the exact message with any wallet's "sign message" feature, or from a terminal:
cast wallet sign --private-key $KEY "$(cat message.txt)". Smart wallets (like Coinbase Smart Wallet) work
too, as long as the wallet is deployed on Base.
Option A: a file on your site
Serve this at , as JSON, with no redirect. Got more than one payout address?
Add each one to the payTo list.
Option B: a DNS record
TXT
One record per payout address. Some DNS providers want the name without your domain on the end
(just ).
After you publish, the board picks it up within a day. Want it checked right away? Email ben.mcalilly@gmail.com.
Your file and DNS record appear here once there's a signature.
The details
Anyone can check these proofs; nothing here depends on the board. This is the exact format.
The message
x402 payout verification Domain: <domain, lowercase> Pay-to: <address, lowercase> Issued: <YYYY-MM-DD>
Lines are separated by a single newline, with one blank line after the first. It's signed as an ordinary
wallet message (EIP-191 personal_sign). Ordinary wallets are checked by recovering the signer; smart-contract
wallets through ERC-1271 on Base.
The file: https://<host>/.well-known/x402-payto.json
{
"version": 1,
"domain": "api.example.com",
"payTo": [
{"address": "0x…", "issued": "2026-11-04", "signature": "0x…"}
]
}
domain must be the exact host serving the file. A signature is optional; without one the
address counts as listed by the site, but not verified.
The DNS record: _x402-payto.<domain>
v=x402payto1; a=0x…; d=2026-11-04; s=0x…
Covers the domain and all its subdomains. Not accepted on shared-hosting domains.
What it proves, and what it doesn't
It proves the site (or domain) and the wallet are controlled by the same party, and it lets the board catch any endpoint that asks to be paid somewhere else. It can't stop someone who has taken over both your web server and your wallet. If you use the file and your server is breached, an attacker could change the file too. That's why DNS counts as the stronger proof, and why the board still alerts on any change. Services that hand out a fresh deposit address for every payment can't use this, since there's no fixed address to sign.
This format is a proposal, not an official x402 standard. Feedback is welcome.