I’m dabs, based in the UK. I build with AI tools, and I’m looking at whether there’s something useful to build for people selling through x402 (HTTP 402 payments for APIs and agents). I’m not selling anything.

I wrote a plain-English guide to seven things worth checking on an x402 seller, with a free self-check you can run on your own testnet copy. No signup, nothing to buy:
https://github.com/dabsfv/x402-seller-self-check

The seven checks

  1. Can the same payment be replayed?
  2. Is the content delivered only after payment settles?
  3. Is a payment tied to the route it was made for?
  4. Do cache headers stop paid content leaking to others?
  5. How are payment headers handled?
  6. How much do you trust the facilitator?
  7. For pay-by-use (upto) routes, is the cap enforced?

The one thing I saw:

On my own Base Sepolia test copy, using the default @x402/next setup, a payment made for one route was accepted on another route with the same price and the same pay-to address. Routes with a different pay-to address or a different price rejected it. This was one small run on my own setup, so treat it as something to test on yours, not as a general claim.

If you have routes that must stay separate, giving them different pay-to addresses or different prices separates them. Routes that share both can still unlock one another.

What I didn’t reproduce:

Duplicate delivery from a replayed payment, a cache leak (my test copy had no cache layer) and upto overspend didn’t show up in my run. That’s not proof they can’t happen elsewhere.

For scale: of 33,455 paid routes in the Coinbase Bazaar catalogue when I counted (14:58 UTC, 16 November), 968 list upto. “Listed” isn’t “used”.

The guide lays out what I checked and how, and what I couldn’t verify. It doesn’t say any setup is secure or safe, only what each check did and didn’t find.

If you run a paid route: what’s been the hardest part of getting x402 payments working?