Your statement is correct. However, it's not entirely a "repackaging of an old concept." First, the HTTP 402 "Payment Required" header has indeed been defined since HTTP/1.1, and the specification explicitly states "reserved for future use." It has always existed in all browsers, servers, and HTTP libraries, but it has almost never been actually used in production environments. The main reason it wasn't used before was due to obstacles in use cases and practical implementation. For example, credit card/bank transfer fees were too high (fixed fee + percentage). For micropayments, the total cost might only be a few cents, making it uneconomical; a $0.01 transaction might have fees exceeding the transaction amount. Furthermore, there was no instant settlement before, browsers didn't have built-in wallets/servers to automatically verify on-chain payments, there were no global instant payment channels, and stablecoins have only developed in recent years; there was also no standardized "payment as request" process (the details of how the server tells the client to pay, the client automatically pays, and how to prove payment). In terms of use cases, previously, most internet browsing was done by humans. Webpage loading and API calls didn't typically require "paying for every request," and revenue was generally generated through subscriptions and advertising, usually on a one-time payment basis. Now, AI agents need to frequently make small-amount API calls, purchase computing power, or acquire data; these scenarios are only just beginning to emerge. As a result, while HTTP 402 has existed for a long time, it has been almost entirely unused. The significance of x402 isn't just a repackaging, but an indispensable piece of the puzzle. It standardizes the 402 process: The client initiates a request; the server returns an HTTP 402 + payment request (amount, currency, receiving address, etc.); The client automatically initiates payment (using stablecoins) along with proof of payment. After verifying successful payment, the server provides the resources to the client. The process involves no accounts, no logins, and no human intervention, completing in a few hundred milliseconds. In the current era of machine-to-machine payments by AI agents, this is a perfect match: AI agents can autonomously spend money to call APIs, inference models, and data services. Expanding to neutral, open standards allows more players to participate, meaning it's not just Coinbase doing it.