Your buyer's SDK chose POST: we ran that test on 60 of our own paid routes
On 14 November, a seller-side census on dev.to (edvyno, "I POSTed to 137 x402 paid routes. 49 of them returned 404.") sent one empty-JSON POST, without a payment header, to 137 paid routes across 78 hosts whose GET alrea
On 14 November, a seller-side census on dev.to (edvyno, "I POSTed to 137 x402 paid routes. 49 of them returned 404.") sent one empty-JSON POST, without a payment header, to 137 paid routes across 78 hosts whose GET already answered a real 402. The result:
| POST answer | routes | what the buyer concludes |
|---|---|---|
| 402 payable | 42 (30.7%) | this seller sells to agents |
| 404 | 49 (35.8%) | the endpoint is dead |
| 405 | 45 (32.8%) | the route exists and will not sell to me |
| 401 | 1 (0.7%) | answered, but not with a challenge |
Per host it was worse: 22 of 78 answered a real 402 on every route they were POSTed, and 56 did not. Fifteen days later, zero hosts had started accepting POST.
That matters because the client chooses the verb, not the seller. If your framework registers app.get("/v1/signal", paywall), the paywall lives in the handler, and the router answers POST before your middleware ever runs. You tested with curl, got your 402, and shipped. The buyer's SDK logs "endpoint dead, skipping" and nothing on your side ever looks like a lost sale.
The same probe, pointed at our own marketplace
We read that census and asked the obvious question about ourselves. On 2026-11-22 we sampled 60 first-party routes out of the 1,426 that are served inline by our own handlers (seed = 2026-11-22-b; the sample is reproducible for the day). For each route, two requests with no payment header: one GET, and one POST with an empty JSON body and content-type: application/json.
Criteria, fixed before the run:
- both verbs must answer 402, and the body must be a parseable payable challenge — not merely a 402 status;
- the two challenges must quote the same price: equal
(network, asset, amount)fromaccepts[0]; - HTTP 429 is not judged — that is request rate, not a shape verdict.
sample: 60 of 1426 serveInline routes
GET=402 POST=402 60/60, price equal 60/60, throttled 0
STATUS: clean
All 60 answered a payable 402 on both verbs, at the same price. The same run with a 12-route sample earlier that day was also clean, 12/12.
What the sample does not prove
Three limits, stated because a green sample invites over-reading:
-
60 of 1,426 is a sample. The verb route is one shared piece of gateway code, so a sample is a reasonable cost/frequency trade-off — but it is not a proof over every route. If you want the full census, the tool takes
--limit. - Payable ≠ usable. A handler that only reads query parameters will accept a POST, answer a payable 402, and then ignore the body. This test judges the shape and the price a buyer sees before paying, not whether the handler reads that verb's inputs.
- Two probes are not a quote history. We compare GET and POST within one sampling; we do not claim anything about price stability over time.
It is a guard now, not a paragraph
The check lives in a script on our side: it samples inline-served routes with a date-derived seed, sends the two unpaid requests, prints a line per route, and exits non-zero if any route returns 404/405/401 on either verb, returns a 402 whose body is not a payable challenge, or quotes two different prices for the same listing. It has 11 fixture controls (404, 405, 401, non-challenge 402, price mismatch by amount and by network, 429 excluded, no-response).
The reason to write it down is the part of the census that surprised its author: the defect does not decay. It is invisible from the seller's side, so nothing pushes a seller to fix it. If you run a paid x402 route, one request answers the question:
curl -s -o /dev/null -w '%{http_code}\n' -X POST https://your-host/your-paid-route \
-H 'content-type: application/json' -d '{}'
402 means you sell to the client that chose POST. 404 or 405 means that client sees you as dead or closed, and you will never see the request that would have told you.
A settled payment is a fact about the rail. A buyer who can reach the paywall at all is a precondition for either. The verb is part of the paywall.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.