Originally published at forgemesh.io.
On July 18 we published measurements of the x402 Bazaar showing one seller wallet behind 40% of all listings — 10,028 near-identical junk resources. Six days later, between two of our crawler's thrice-daily snapshots, that seller was gone. So was a third of everything else.
The night the catalog shrank
- 24,925 live listings in our 20:15 UTC snapshot, July 23
- 14,193 live listings eight hours later — a 43% drop between snapshots
- ~93% of purged listings traced to that single whale seller
- Sellers: 880 → 1,079 — the trough, and ten days of regrowth
No blog post. No changelog entry. No status page incident. As far as we can tell, the only reason anyone can put timestamps on this event is that our crawler happened to be watching. The catalog operator cleaned house — correctly, in our view; the purged listings were overwhelmingly spam — and simply never said so.
One number we report with some satisfaction: every one of our own 800+ listings survived the night. Not by luck, and not by reacting fast — there was nothing to react to. The sweep enforced what turned out to be our existing checklist: canonical URLs, typed protocol versions, honest metadata, a real working endpoint behind every listing. Best practices are invisible right up until the night an unannounced purge selects for them.
The same week, the ground moved
The purge wasn't isolated. In the same late-July window, the protocol's day-to-day home quietly shifted away from the single company that started it, the community moved venues — the old support links in the official docs now return "Invite Invalid" — and parts of the discovery API changed behavior without a deprecation notice. The endpoint many sellers used to verify their own listings began silently returning something different from what it used to.
None of this was hidden, exactly. All of it was findable — in commit logs, in issue threads, in dead links. But nothing was announced, and that's the actual lesson: in the agent economy right now, the changes that affect your revenue ship silently. You either measure, or you find out weeks later.
Our quiet weekend, and what it wasn't
In early August our own fleet — 13 paid services, 800+ listed resources — went a weekend without a single external sale. We assumed the worst: payment-rail failure, billing suspension, delisting. The investigation found none of that. Settlement worked. Every listing was intact. Probe traffic was at record highs — 65,000 hits a day — while purchases sat at zero.
The on-chain forensics were humbling. Most of our historical "buyers" turned out to be short-lived evaluation wallets that sampled everything once and went dormant — census-takers, not customers. Meanwhile the wallets actively spending that same weekend had simply never met us. The market wasn't dark. We were unlit.
We fixed our fleet in a day, re-indexed everything, and rewrote our machine-facing copy in the language buying agents actually search with. The first two never-before-seen buyer wallets arrived about twelve hours later — one came back four times the same morning.
What we'd tell any x402 seller
Agents don't hold grudges and they don't remember you — every task re-runs the supplier choice from scratch. You can be passed over a thousand times and still win tomorrow morning, but only if you're present where the choosing happens, legible to the software doing the choosing, and honest about which of your "customers" were ever customers at all.
Measure everything. Assume the platform will change under you without a press release — because this month, it did.
The specific checks, fixes, and submission flows we run live in our x402 seller kits.
Top comments (0)