In my last post I listed the ways an x402 payment can go wrong. Vector number one was the dynamic payTo swap: in x402 the destination address can change per request, so a seller can quote you address A and then take payment to address B. I said it was one of the checkable ones.
So I built the check, wired it into Frisk's hosted reputation side, and pointed it at the x402 Bazaar — the public directory of paid endpoints — on a daily crawl. The idea was simple: remember each endpoint's advertised payTo, and if it changes, that is a swap, so flag the counterparty.
Over about a month it recorded 272 payTo changes across 246 endpoints, and promoted them into 57 honeypot:payto_swap reputation labels.
Then I looked at what it had actually flagged. The endpoint with the most flags in the entire dataset was x402.browserbase.com, with 9. Second was x402.tavily.com, with 8. Browserbase and Tavily are real, funded infrastructure companies. My detector had scored them 0 and told callers they were honeypots.
Those flags were wrong. So were the rest. What took longer to admit is that they were wrong in five separate ways, and only one of them was the mistake I thought I was making.
