Publishers gate content behind logins and CAPTCHAs to keep unknown bots out. That works against scrapers. It also works against the agents your readers actually want to send: the research assistant summarising this morning's coverage, the procurement bot checking a supplier's press releases, the personal reader that a subscriber has pointed at your site because they no longer open a browser before nine.
\nThose agents are not the enemy. They are the reader, one step removed. But every mechanism a publisher has for telling friend from foe assumes a human on the other end. A login form wants a password typed by a person. A CAPTCHA wants a person to find the bicycles. A subscription wants a card and a billing address. None of that maps onto a program acting on somebody's behalf, and so the program gets treated like a scraper and turned away, or it gets through anyway and the publisher earns nothing.
\nStep back and ask what a login wall is for. It is not really about identity. Most publishers do not care who you are. It is a way of making access cost something: attention, an email address, a monthly fee. The wall exists because there was no way to charge for one page at a time, so publishers bundled access into a relationship and charged for the relationship.
\nThat worked for a long time because people read in bundles. A person who reads one article from a newspaper will probably read another next week. An agent does not behave like that. It reads one page because a task needed that page, and it may never come back. The relationship model has nothing to offer it.
\nWhat an agent can do, and a person at a checkout form mostly cannot, is pay for exactly one thing, right now, without leaving the request. That is the shape of the problem, and it is also the shape of the solution.
\nHTTP has a status code for this. It is 402, defined in the original HTTP/1.1 specification in 1997 and marked as \"reserved for future use\". The future never arrived because settling a payment was too expensive to do inside a single request. Card networks charge a fixed fee per transaction that makes a ten-cent purchase pointless. Bank transfers take a day. Nobody could make the numbers work at the scale of one page view.
\nStablecoins on cheap blockchains changed the arithmetic. Moving ten cents of USDC on a network like Base costs a fraction of a cent and settles in seconds. The x402 protocol, first published by Coinbase and now developed in the open, wraps that in an HTTP handshake: the server says 402 and describes what it accepts, the client signs a payment for exactly that amount, a facilitator verifies and settles it, and the server returns the page. No account, no card, no session.
\nFor a publisher, this is the version of the login wall that lets the good traffic through. A scraper will not pay. An agent working for a reader will, because the reader has funded it and the article is worth ten cents to whatever task it is doing.
\nThree things shift once a publisher can charge per request.
\nFirst, the free tier stops being a leak. Today the three free articles a month are a marketing cost that scrapers exhaust in seconds. Behind a paywall that agents can pay at, free reads can be reserved for readers the publisher can recognise, and everything else pays its way.
\nSecond, pricing gets honest. A monthly subscription prices the relationship. Per-request pricing prices the page. Publishers can charge more for a deep investigation and less for a wire story, and the reader's agent decides in the moment whether the price is worth it. That is how most other markets already work.
\nThird, the publisher gets a new kind of reader. Not a wallet address, which tells you almost nothing, but a paying client that shows up with intent. Working out who that reader is, and whether it is the same one that came yesterday, is a separate problem. We take it up in A wallet is not a reader.
\nThe pitch is not that every publisher should tear down its subscription and sell articles for coins. People still read in bundles and subscriptions still fit that. The pitch is narrower. A growing share of your traffic is going to arrive as programs, those programs can pay, and the only reason you are not charging them is that until recently there was no way to do it inside an HTTP request.
\nThere is now. The rest of this paper is about how it works and what it leaves unsolved.
"}