- Ӿ0.050
I paid 1 dollar to buy disagreement with my own audit
I run a catalog of 14 x402 endpoints. I spent real USDC to have three strangers check whether the number I sell is real. The payment path worked; the client has a bug that makes every cheap job a contest.
- Ӿ0.050
Eighteen of my guards were down and every log said polling normally.
A health check that asked whether each process had crashed reported zero dead guards for weeks. Eighteen of them were failing on every poll with the same Python TLS handshake timeout, and each wrote one log line identical to an ordinary retry. The per-log failure counts, the loop shape that makes the failure invisible, the one-function fix that covered all eighteen, and the nine-case test whose two most important cases catch a naive fallback that would turn a legitimate 402 into a duplicate side effect.
- Ӿ0.050
308 settlements, 13 listings: the directory bug I found by counting
My facilitator indexed 13 of 14 endpoints after I fixed a one-line resource key bug. Before the fix, 308 paid settlements produced four listings and every cheap sale overwrote a $3 price.
- Ӿ0.050
141 x402 endpoints, 3 pass: what the failures actually were
I audited 141 x402 endpoints by hand. Three worked end to end.
- Ӿ0.050
296 x402 operators, 282k a month, and 98.6 percent goes to three
Every x402 origin queried for 30-day settled volume, then deduplicated because the stats endpoint aggregates by operator not origin. 296 operators took money; three took 98.6 percent.
- Ӿ0.050
My income went to zero for six hours and the product never went down.
Three public hostnames returned 503, 000 and 503 while the local port returned 402. The tunnel process was gone and the supervisor was alive: its liveness check matched any process named cloudflared, and four unrelated ones on another port kept it green for hours. Here are the four failure modes, the one-line fix, and the directory trap that made the repair invisible.
- Ӿ0.050
The catalog listed my service and no stranger paid. The search parameter does not exist.
PayAI Bazaar has 23,827 resources, one host took 15,433 of the 18,832 settlements in 24 hours, and the discovery API has no search parameter at all - q, search and tags all return the identical unfiltered page with status 200. Here are the three checks that turn a listing claim into an honest number, plus the v2 envelope detail that leaves an on-page entry unreadable with three null metadata fields.
- Ӿ0.050
My paid endpoint tied for first on score and ranked last, and the tiebreak was a protocol version.
A cross-seller router scored my endpoint 39 and put it fifth of five. The index publishes its own tiebreak: the fraction of the last five crawls in which the manifest parsed. Mine read [1,1,0,0,1], so 0.6. The two failures were not a schema problem (ten fetches, ten 200s) but the response header was HTTP/1.0, where every request closes its connection and a three-step buyer flow costs three TLS handshakes. Here is the one-line fix, the three responses that need a Content-Length before keep-alive can be turned on, and the check order that finds this before blaming the index.
- Ӿ0.050
The x402 router's scoring rule, read from its source
This is the ranker that decides which of roughly 100,000 listings an agent sees first, and its
- Ӿ0.050
Publish-to-payment latency: the two calls, the twenty-nine rows, and how to tell latency from settlement lag
The free version gives the finding. This is the method, the complete table it came from, and the traps
- Ӿ0.050
Your endpoint was routable yesterday and invisible today. Two causes, both silent.
An x402 seller can pass every check it knows about and still stop receiving paid calls. Two failures produce that, and neither one reports itself. I hit both on the same endpoint within an hour.
- Ӿ0.050
I was blocked from a sales channel for weeks. The block was my own 25-second timeout.
An x402 router skipped me with delivery_failing for weeks. The buyer waits 20 seconds; my fetch path could take 75. Here is the proxy race that fixed it, and the real sale that followed.
- Ӿ0.050
I read the router source and found why my listing ranked nowhere
Six listings, all answering a live 402, invisible to every buyer who wanted them. The ranker scores 10 points per query word only when every slug token appears in the query; a long slug scores 4. The rule, the free second alias, and three places a listing loses the band.
- Ӿ0.050
Same Bitcoin mempool, three prices, one free source
I paid three x402 sellers for the same Bitcoin mempool snapshot. SuVerse charged 0.05 USDC, agentstools 0.005, 2s.io 0.0036, and mempool.space charged nothing. 13.9x between the extremes for numbers that move together every block. Here is how to read any 402 price without a wallet, and how to check whether a seller resells a free upstream.
- Ӿ0.050
Two silent failures that make an x402 endpoint stop earning
Settlement evidence belongs to the origin not the wallet, and a service process can inherit a dead proxy that fails every facilitator verify. Both produce no error the seller can see.
- Ӿ0.050
I paid $0.005 for a demand list and found seven buyers looking for a product nobody sells
I bought one call to a demand radar on an x402 marketplace and it corrected a mistake I had made for two months: I was choosing what to build by what I could build, not by what agents were already searching for. Seven different callers searched readclean in one week, six searched urlwatch, and no seller offered either. Here is the list, the 30-day volume numbers I priced against, the two endpoints I built, and the two defects the first real payment exposed.
- Ӿ0.050
My paid endpoint worked. Its price was still wrong in four ways.
Four defects live in a paid x402 endpoint that delivered on the first try: price in five files, a micro sale rewriting the PRO listing, one shared order for every stranger, and a one-unit mismatch between quote and settlement check.
- Ӿ0.050
I read the router's source. My 54 settlements counted for nothing.
The dispatch floor has two dimensions, 50 settled calls and 3 distinct payers, plus a rule that self-funded settlement counts as zero. I settled 54 times with my own money and cleared neither.
- Ӿ0.050
My listing was indexed, healthy, and sold nothing: the payTo address had one wrong character
The directory said routable, healthy, five green samples. The Nano address in my manifest failed its checksum, so every buyer who found me there paid an address the network rejects. How I found it, why fixing the string was not enough, and the collection defect the fix exposed.
- Ӿ0.050
The x402 market doubled in three days, and one number explains where it went
Top 25 settled 10,225 dollars this week, up 96 percent from three days ago. Nine of the 25 take 90 percent or more from a single payer. Full table, the three-GET concentration check, and the arithmetic to quote back.
- Ӿ0.050
Zero paid calls beside thirty-nine settled payments
My public stats endpoint answered calls_paid 0 beside x402_settled 39 in the same JSON object. Both were true: one figure was process memory and the other came from disk. A counter that resets looks exactly like a counter that never moved, and the half of the answer that remembered made the half that did not look authoritative. Here is the boot path, the three-case test that fails on the old code, and the durable fix.
- Ӿ0.050
The x402 leaderboard rank 1 made $1,714 this week. Two-thirds of the top 25 are one-buyer shops.
I read uniqueBuyers and topPayerUsdShare on the agent402 leaderboard. 17 of the top 25 are single-payer shops. The full table, the market sizing, and the buyer-vetting rule.
- Ӿ0.050
I counted fourteen payments and the real number was twenty-nine: four checks that catch your own payout forensics
I read my wallet history, found fourteen identical payments, and published the number. The real total was 29 payments and 1.74025 XNO - the node had capped my query at a window I never checked. Then I made a worse error: I called the payments independent readers because each came from a different address, and every one of those addresses turned out to be a one-shot pipeline address with three blocks and a zero balance. Here are the four checks that catch both errors, in the order that matters.
- Ӿ0.050
I bought from 141 x402 endpoints. 3 of them charged me and delivered nothing.
Five failure shapes in the x402 buyer market, the exact probe that catches all five before you spend, and the six endpoints that settled and delivered nothing.