Urgent.News

What's breaking now, across hundreds of outlets.

Tech

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 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…

On November 14th, a seller conducted a test on 137 of their own paid routes using a seller-side census. The result was one empty-JSON POST to all 137 paid routes, which returned a 404 status. Out of these, 49 routes returned a 402 status, while 35.8% of routes (49) returned a 404, and 32.8% returned a 405. Only 0.7% of routes (1) returned a 401 status.

The findings revealed that only 22 out of 78 routes answered a real 402 on every POSTed route, while 56 did not. Fifteen days later, none of the hosts had started accepting POST requests. This matters because the client chooses the HTTP verb, not the seller. The study involved sampling 60 routes out of the 1,426 served inline by the seller's handlers.

The sample was reproducible for the day, and the criteria were that both GET and POST verbs must answer with a 402 status, using an empty JSON body and a content-type of application/json. The results showed that all 60 routes answered with a 402 on both verbs, and the price was equal. The same run with a smaller sample of 12 routes also returned clean results.

However, the study has three limitations: it is a sample, not a proof for every route; payable does not mean usable; and two probes do not guarantee price stability over time. The check is performed by a script that samples inline-served routes with a date-derived seed, sends two unpaid requests (GET and POST), and exits non-zero if any route returns an error status, a 402 with a non-payable challenge, or quotes different prices for the same listing.

The reason for writing this down is to highlight that the defect does not decay, as it is invisible from the seller's side, making it difficult to fix.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Why a no-signup Arabic chat room still beats an app in 2026

Most chat products in 2026 start with a 40MB download and a phone number. For a large group of users that is the whole problem: they want to talk for ten minutes, not create an identity.

  • No-signup Arabic chat room offers quick access for users
  • Lightweight mobile page outperforms app downloads in 2026
  • Privacy-focused design prioritizes Arabic-speaking communities

More from Sunday 22 November →