Menu

I measured 86 paid API endpoints. They fail the same four things.
📰

I measured 86 paid API endpoints. They fail the same four things.

DEV Community·Cian·about 6 hours ago
#i9UAjWLk
#dev#paid#endpoints#first#endpoint
Reading 0:00
15s threshold

There are 24,008 pay-per-call HTTP resources indexed by the PayAI x402 facilitator

alone, sold to agents at a median of one cent each on Base. Almost nobody publishes

what those endpoints actually send back when you call them. Findings below come from

86 endpoints on 52 hosts, measured with sockets and the Python standard library, one

request each, no scoring and no ranking.

Three numbers first, because they are the whole argument:

75 of 86 endpoints send no Content-Security-Policy .

59 of 86 allow Access-Control-Allow-Origin: * .

18 of 36 seller-controlled DNS zones publish no DMARC record at all.

Why a paid endpoint breaks the usual reasoning

A marketing site can survive a missing header, because a person tolerates it. A paid

machine endpoint cannot, because the caller is a process that reacts to what it is

told. Access-Control-Allow-Origin: * on an endpoint that is paid means any page in

any browser can spend a connected wallet's money against your service.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.