The shift from human users to autonomous software is creating a new category of internet commerce. Software is no longer just a tool; it is a buyer. On November 9, 2026, Tazapay detailed its infrastructure for the x402 protocol, allowing businesses to charge artificial intelligence agents per request in digital dollars and settle in local currency. Two days later, on November 11, 2026, NEAR announced that its platform now supports x402 and the Machine Payments Protocol across more than 35 networks.
This combination of standard protocols and cross-network routing solves a fundamental bottleneck in artificial intelligence. When an agent researches a market or pulls logistics data, it eventually hits a paywall. Traditional payment flows require a human to create an account, enter a card number, or approve a monthly invoice. Those steps block an autonomous agent mid-task. The recent infrastructure rollouts replace human checkouts with machine-readable terms, allowing software to evaluate a price, sign a payment, and consume data in milliseconds.
The mechanics of an HTTP 402 payment
The foundation of this shift is x402. Introduced by Coinbase in May 2025, the protocol gives a defined format to the long-dormant HTTP 402 Payment Required status code. In July 2026, the Linux Foundation launched the x402 Foundation to govern the standard, bringing together 40 members including Visa, Mastercard, Stripe, Google, AWS, Cloudflare, and the NEAR Foundation.
When an agent requests a paid resource, the server rejects the initial call and returns a 402 status. The response includes machine-readable terms: the price, the accepted digital dollars, the network, and a time limit.
The agent evaluates the terms against its approved spending limits. If the price is acceptable, the agent signs an authorization for the exact amount. This signature includes a one-time number to prevent the payment from being reused. The agent then retries the exact same request, this time attaching the signed payment in an HTTP header.
HTTP/1.1 402 Payment Required
Content-Type: application/json
X-Payment-Options: amount="0.05", currency="digital_dollars", network="primary"This loop happens entirely in the background. There are no redirect URLs, no checkout pages, and no manual data entry. The agent simply reads the price, approves the transaction based on its predefined rules, and fetches the data.
Separating verification from settlement
Agents often call dozens of paid endpoints to complete a single complex task. If every API call had to wait for a transaction to fully settle on a network, the agent would spend more time waiting than working. The x402 architecture solves this by splitting verification from settlement.
When the server receives the signed payment, it passes the payload to a facilitator. The facilitator checks that the signature is genuine, the amount covers the price, and the one-time number is unused. These checks take milliseconds because they only evaluate the signed message itself.
Once the facilitator confirms the payment is valid, the server immediately releases the requested data to the agent. The actual settlement happens afterward. The facilitator submits the transaction, pays the network fees, and waits for final confirmation. The facilitator absorbs the brief risk between verification and final settlement, allowing the agent to continue its work without delay. This separation is what makes small, frequent machine payments commercially viable.
Routing payouts across networks
Standardizing the payment request is only half the equation. The other half is ensuring the seller actually receives a usable asset. An agent might hold digital dollars on one network, while the seller requires a different asset on another network.
NEAR addresses this gap by adding cross-network settlement to open protocols like x402 and the Machine Payments Protocol. The latter was co-authored by Stripe and Tempo. With the NEAR integration, an agent pays in the digital dollars it holds, and the seller receives the payout in the asset and network it prefers. The platform has already processed more than 30 million swaps and over 33 billion dollars in all-time volume.
This routing relies on single-use deposit addresses minted for each specific quote. When the agent submits its payment, the funds flow to that unique address. The infrastructure then routes the payment into the seller's configured destination. Because every address is tied to a single quote, the seller can confirm every payment automatically. There is no shared address to monitor and no manual reconciliation required. Sellers can also opt for confidential settlement, which reduces the public visibility of balances and transaction activity.
Tazapay offers a similar abstraction for the seller. A data provider can price its API per call in digital dollars. Tazapay checks and settles the payment, then records it as a standard collection. The merchant can keep the revenue in digital dollars or convert it into local currency. The data provider never has to build blockchain infrastructure or manage network fees.
Designing for machine buyers
For developers and product teams, the agent economy requires a shift in monetization strategy. Software is becoming a primary customer, and businesses must adapt their infrastructure to serve it.
The most immediate change is pricing granularity. Subscription tiers and prepaid credits create friction for autonomous buyers. Agents operate best when they can pay for exactly what they consume, exactly when they consume it. Developers should expose individual endpoints with clear, per-request pricing.
However, micro-transactions have physical limits. Every payment route has a minimum floor dictated by network fees. Some routes clear payments smaller than a dollar, while others require larger amounts. Builders must ensure that the floor on their buyers' likely routes sits below the price of the API call.
Integrators must also design robust approval controls. While the payment protocols handle the transaction, the client application must define strict spending limits. An agent should never have unbounded access to funds. The user must set clear parameters regarding how much the agent can spend per request, per task, and per day. The human delegates the execution, but the human always retains control over the budget.
As Illia Polosukhin noted in the NEAR announcement, "Open standards are required for an open agent economy." Builders who adopt these standards early will capture the growing volume of automated traffic.
The new internet economy
The transition from human buyers to machine buyers is accelerating. Protocols like x402 and the Machine Payments Protocol provide the standardized vocabulary for software to negotiate and pay for resources. Cross-network settlement infrastructure ensures those payments flow seamlessly from the agent to the seller's preferred ledger. Businesses that expose their data and services to these automated buyers will unlock entirely new revenue streams, driven by agents that never sleep, never wait for an invoice, and pay exactly what they owe in milliseconds.