In 1996, at the University of California, Irvine
In a dimly lit laboratory, a young Roy Fielding and his colleagues were engrossed in drafting a document that would rewrite the world—the HTTP/1.1 protocol. It defined how browsers and servers communicate, determining how web pages load, how images are transmitted, and how forms are submitted. It can be said that without it, there would be no World Wide Web today.
Yet, amidst these dry terms, they embedded an unusual “Easter egg”:
HTTP 402 – Payment Required..
In their vision, the future web would not need to fill pages with advertisements or require annual subscriptions. Instead, users could pay for what they truly needed—a single article, a photo, or even a data field. The browser would automatically handle the few cents in transactions in the background, seamlessly connecting access and payment, as naturally as a TCP/IP handshake.
However, this vision was ultimately buried by the times. In the reality of the 1990s, there were no economic or technological conditions to allow it to take root. As expected, HTTP 402 was hardly ever truly activated over the thirty years, lying in lonely slumber within the protocol.
Thirty years ago, it was a doomed concept;
Thirty years later, it has become a topic revisited in the AI era.
The Inevitable Failure—The “Three Mountains” of the 90s
Let’s rewind to 1998.
Jack opened the New York Times using Netscape on a dial-up connection. The gray progress bar on the screen crawled slowly, and the modem emitted a harsh beeping sound. Finally, the page loaded, but just as he reached the second paragraph, a prompt popped up—”Payment Required: Please pay $0.05 to continue reading.”
Jack hesitated for a moment, clicked confirm, but found he had to enter his credit card number and wait several seconds, ultimately paying nearly 35 cents. By the time the page refreshed, his patience had worn thin, and he closed the webpage, turning to another free portal.
This was precisely the predicament that HTTP 402 faced in the 90s. It was not that it was not advanced enough, but from the very beginning, it collided with three insurmountable “mountains”.
The first mountain: The iron law of economics.
Economist Coase’s transaction cost theory has long pointed out that whether a transaction can be established depends on whether the cost is lower than the benefit. HTTP 402 envisioned “5 cents for an article,” but in the credit card-dominated era, the fixed transaction fee for each transaction was about 25–35 cents. In other words, for 5 cents worth of content, the user had to pay 35 cents. The transaction cost was six times greater than the transaction amount, making this logic inherently “unfeasible” in economics.
The second mountain: Fragmented experience.
The charm of the internet lies in its “instant” nature, while HTTP 402 brought fragmented interruptions. Each click could trigger a payment window, and each payment required entering a card number and waiting on a dial-up connection. More critically, it forced users to frequently make the decision of “should I pay for this content” without any preparation. This psychological phenomenon is known as decision fatigue, and users would quickly choose to give up. In contrast, while advertisements are crude and subscriptions clumsy, they at least maintain a continuous experience.
The third mountain: The technological void.
HTTP 402 left a door open in the protocol, but it led nowhere. Browsers lacked built-in wallets, websites had no unified payment interfaces, and payment gateways had no scalable solutions. Microsoft attempted to promote “MSN Micropayments” in 1999 to facilitate instant payments for individual articles, but it silently vanished two years later due to a lack of ecosystem support. Early electronic currency attempts like DigiCash also failed due to a lack of standards and compatibility.
When the vision of 402 was crushed by the “three mountains,” another path unexpectedly emerged:the advertising model.
Google invented the internet’s most “great” and also most “original sin” business logic—users get free content, and advertisers pay. The entire internet began to operate around the “attention economy”:
-
Users enjoy a wealth of free content;
-
Content providers earn revenue through advertisements;
-
Advertisers reach previously unreachable audiences at a very low cost.
This was a victory of economies of scale, but it also sowed long-term hidden dangers. As some have said:“Advertising is the original sin of the internet.” We replaced the possibility of micropayments with users’ attention.
In the 90s, HTTP 402 was destined to fail.
Economically, transaction costs exceeded transaction amounts;
Experientially, fragmented interactions were unacceptable;
Technologically, there was a lack of supporting infrastructure.
It was a seed ahead of its time, but it fell on barren soil. The internet ultimately chose advertising and subscriptions over micropayments.
However, the arrival of the AI era has turned the story around. After all,advertising needs attention, while AI has no attention.
AI Tears Open Payment Boundaries
If HTTP 402 was like a seed that fell into the wrong era in the 90s, then thirty years later, the arrival of AI is like a sudden storm that changes the climate and rewrites the soil.
In the past, searching for “HTTP 402” would lead to dozens of ad-dependent pages; today, a single question can prompt AI to generate a complete answer directly on the screen. There are no clicks, no ads, and no advertisers paying. For users, this is ultimate convenience; for content providers, however, it is a cliff-like drop. This is also why by 2024, one-third of the top ten thousand websites globally have simply blocked AI crawlers, trying to protect their last value line.
The collapse of the advertising model is not accidental; it has been brutally pierced by the consumption logic of AI.
The first change: Consumption atomization.
Human consumption habits are “packaged”—subscribing for a month, buying a whole book, which reduces decision fatigue. The advertising model relies on this: offering free content and selling attention to advertisers.
But AI has no “attention” to sell; it only needs to buy the specific piece it wants: an API call worth $0.0001; a stock price data point for $0.01; a photo editing function for $0.05.
In the past, these zero-sum prices could not enter the market, but now they are the natural consumption units for AI.Advertising bypassed the micropayment dilemma, but AI cannot escape it.
The second change: Decision flow.
Humans can wait a few seconds to confirm payment, or even a few minutes to reconcile; the advertising model can also tolerate “getting on the bus first and paying later”.
But AI’s brain has no patience—it can complete hundreds of calls in milliseconds. Humans drive thought by burning calories, while AI consumes computing power, bandwidth, and tokens.
If payments remain in the “click to confirm—monthly settlement” logic, such calls cannot happen at all.AI does not want a bill; it wants a data stream.
The third change: Dehumanization of subjects.
When HTTP 402 was written into the protocol, the payers were only humans; today, machines are about to start paying for machines.
Models settle for data calls, agents pay for GPU computing power, and robots place sample orders on cross-border e-commerce platforms. Humans will only receive a simple notification afterward: “Today, 27 payments were completed, totaling $12.4.”
This is the M2M (Machine-to-Machine) economy: the counterpart in transactions is no longer human attention, but machine computing power and data. The attention economy is failing, and value is returning to the essence of micropayments.
Thirty years ago, HTTP 402 was crushed by three mountains: high transaction costs, fragmented user experience, and a blank technological foundation.
Thirty years later, the three changes brought by AI are precisely breaking through these barriers.
Advertising and subscriptions were once the pillars of the internet, but in the AI era, they are collapsing.
HTTP 402, that lonely number, has finally found its stage.
The New Life Scene of HTTP 402
If the first two acts were about logic, the next is about the scenes in reality.
HTTP 402 has not revived as an “awkward payment pop-up”; instead, it has quietly integrated into the backend of the AI economy in a more subtle and natural way.
Imagine the daily routine of a young startup team. They are preparing a smart glasses product but have neither a large budget nor a global team. Yet, within a week, they complete research, design, procurement, and market testing. The secret is not overtime, but delegating most of the work to AI assistants.
In the morning, the AI assistant retrieves data.
In the past, this meant annual subscriptions costing thousands of dollars, such as Bloomberg terminals costing up to $20,000 per year. Now, the assistant only spent $0.01 to buy a stock price record and $0.05 to retrieve two paragraphs of a market report summary. Those obscure data that once lay dormant in the long tail have been “awakened” for the first time as tradable units.
It is worth noting that by 2024, the global data market size has exceeded $300 billion, with more than half of the value never utilized. HTTP 402 here acts like a sorter, pushing dormant value back into the market.
In the afternoon, the AI assistant switches to computing power.
It needs to render a prototype, but instead of renting a cloud server (AWS A100 costs about $4 per hour), it only calls a GPU for a few seconds, costing just $0.002. Then, it calls two large models, with costs settled in real-time based on tokens.
This “second-level payment” logic fundamentally changes the computing power market. McKinsey’s research shows that global data centers’ GPU utilization rates have long been below 30%. Micropayments have activated these fragmented resources for the first time, making computing power no longer exclusive to giants, but flowing on demand like electricity.
In the evening, the AI assistant completes cross-border testing.
It places sample orders on the 1688 platform and initiates small orders on Southeast Asian e-commerce platforms to collect feedback. There are no manual confirmations, no three-day settlement delays, but payments are completed instantly through stablecoins. Traditional cross-border payment fees range from 2% to 6%, with settlement cycles lasting 3 to 5 days; for small orders under $10, this is almost “unfeasible”. Today, settlements are as light as sending a message.
The founders seem to have had an ordinary day: just checking a few data points, rendering a prototype, and running a few orders. But in the background, the AI assistant has completed thousands of micropayments, each worth only a few cents, but cumulatively supporting the entire business cycle.
This is what HTTP 402 looks like today.
It is no longer the awkward “pop-up payment” of the 90s; instead, it is a tacit action embedded deep within the system: it returns value to its source, reactivates idle resources, and enables global supply chains to complete settlements in milliseconds.
Thirty years ago, it was a lonely number in the protocol; thirty years later, it has become the smallest economic unit in the AI world.
However, as the story reaches this point, questions also arise:
If you really ask—can these payments run on today’s systems?
The answer is almost “impossible”.
For a $0.01 data call, do you want to pay a 30-cent fee?
For two seconds of GPU rental, who will help you split the bill?
For a $10 cross-border sample order, if you still have to wait three days for settlement, does market testing still make sense?
The vision of HTTP 402 seems reasonable today, but it still lacks a realistic carrier.
Like the empty door from thirty years ago, it has finally welcomed the era, but still lacks a key to turn the lock.
AIsa’s Practice—The Key to HTTP 402
AIsa aims to be that key.
Its goal is not to create a faster chain but to reconstruct the payment protocol layer, making $0.0001 transactions truly cost-effective, controllable, and feasible.
Imagine a scenario: the AI assistant retrieves a report, calls a GPU for a few seconds, and places a sample order on an e-commerce platform. Throughout the process, no payment pop-up interrupts you. All settlements flow in the background like electricity, and by evening, you receive a notification on your phone: “Today, 37 transactions were completed, totaling $42.8.”
This is the frictionless experience that HTTP 402 envisioned back in the day.
To make it a reality, we need to fill in the four missing pieces from back then:identity, risk control, invocation, and settlement.
The first piece is Wallet & Account.
HTTP 402 failed to take root in the 90s largely because browsers lacked wallets, and there was no unified account system between users and websites. Today, the payment entities have shifted from humans to AI agents, which must have independent economic identities. The role of Wallet & Account is to give AI a “wallet as identity”: capable of holding stablecoins and connecting to fiat accounts. Without it, HTTP 402 will forever remain just a number on paper.
The second piece is AgentPayGuard.
When AI truly has a wallet, risks follow: will it consume without limits? Will it be abused?
AgentPayGuard provides this layer of protection. Limits, whitelisting mechanisms, rate controls, and manual approvals—these risk control measures are directly written into the protocol, ensuring that payments remain within traceable and intervenable bounds. AI can settle autonomously, but it will never “run amok”. This is a necessary condition for turning romance into reality.
The third piece is AgentPayWall-402.
The romantic intention of HTTP 402 was “pay as you go,” but in the 90s, it could only become an awkward payment pop-up.
AgentPayWall-402 resolves this experiential dilemma: payment is no longer an additional action but is integrated with access itself. Invoking a data segment, renting a few seconds of GPU, unlocking an image—payment and access are completed simultaneously. For users, the experience is seamless; for providers, invocation is no longer “free-riding” but real-time compensation.
The fourth piece is AIsaNet.
When transaction amounts shrink to $0.0001, the 30-cent fee of credit cards makes micropayments almost a joke.
The value of AIsaNet lies in flattening the cost curve completely. It is a high-frequency micropayment settlement network that supports millions of TPS and can connect to other high-performance distributed systems to establish multiple channels. In the background, the Treasury module is responsible for intelligent settlement between fiat and stablecoins, as well as between different stablecoins. Thus, a data point you click in Shanghai can have the provider in San Francisco receive payment in milliseconds.
These four pieces form the closed loop of HTTP 402 from “ideal” to “reality”:
-
Wallet & Account gives AI a payment identity,
-
AgentPayGuard ensures it does not run out of control,
-
AgentPayWall-402 seamlessly connects payment and invocation,
-
AIsaNet ensures that all of this can run smoothly on a technical level.
This is the moment when the “empty door” from thirty years ago finally gets a lock and a key. HTTP 402 is no longer a lonely number in the protocol but is beginning to flow into the bloodstream of the AI economy.
Conclusion—The Return of Thirty Years of Fate
Thirty years ago, in a laboratory in California, Roy Fielding wrote a lonely number into the protocol: HTTP 402.
It embodied the dreams of tech geeks—that the internet could have a romantic business logic: no ads, no subscriptions, just paying a few cents for what you truly use.
But in that era, it was destined to take root nowhere. Thus, 402 slumbered for thirty years, like a forgotten footnote.
Today, AI has awakened it.
Because AI does not watch ads, does not buy packages, it only calls an API once, requests a data point, rents a few seconds of computing power.
Each call may only be worth $0.001, but when multiplied by billions, it is enough to support a whole new economic system.
Stablecoins and new settlement networks allow this $0.001 to be processed for the first time at millisecond speed;
Protocols like AIsa provide a secure, compliant, and scalable path for it to land.
Imagine a future like this:
At the end of your day, your phone pops up a notification—
“Today, a total of 43 payments were completed, totaling $28.7.”
You have not entered a card number, nor clicked confirm; all these payments were completed by your AI assistant in the background.
It helped you purchase several data points, rented GPU computing power, called model interfaces, and placed a few small cross-border orders.
And all you see is a line of cold numbers.
At that moment, you will realize: HTTP 402 did not fail; it was just waiting.
Waiting for an era with a fine enough transaction granularity, waiting for a technology that enables frictionless global settlement, waiting for a payment entity to shift from humans to machines.
Thirty years later, all of this has finally arrived.
HTTP 402 is no longer a romantic relic but the cornerstone of the AI economy.
The real question is no longer “do we need micropayments,” but:who can get it right on this historical return journey.
