Post #8330

💡x402: The Internet Gets a Wallet x402 turns the web into a pay-as-you-go marketplace. APIs, apps, and AI agents can send or receive tiny crypto payments instantly and unlock data or compute on the spot. ➡️ What x402 is x402 is a revived use of HTTP 402 “Payment Required.” Think of it as a native coin slot for the web. A site or API can say “pay a few cents” and your app pays, gets a receipt, and the content returns immediately. ➡️How a request works You ask an API for data. The server replies with 402 and a price quote in a chosen currency like USDC or ETH. Your app resends the request with a small on-chain payment embedded in a special header. A verifier confirms the transfer. The server unlocks the response and includes a proof-of-payment receipt. ➡️Why this beats the old model The current web leans on ads and monthly subscriptions. Payments rely on third parties, cards, chargebacks, invoices, and delayed payouts. x402 replaces that overhead with instant settlement, no middlemen, and no accounts. You only pay for what you use. ➡️The vending machine analogy APIs become self-serve machines. Providers stock endpoints like products and set prices per call. Developers and agents walk up, pay per request, and get the result. No forms. No contracts. Just clean microtransactions at internet speed. ➡️What it unlocks for AI agents Agents can act autonomously. They can buy weather data, run a model, fetch a dataset, or trigger a compute task, all with trustless payments. No human card on file. No API keys taped to a spreadsheet. Per-call pricing lets agents compose many services without subscription bloat. ➡️What it changes for API providers Direct revenue per request with programmable pricing. New product layouts like metered data, paid retries, premium latency, and tiered compute. Instant receipts and no chargeback risk. Payouts stream as requests arrive instead of monthly. ➡️Key parts under the hood Payment request tells what to pay and in which currency. Payment header carries proof of payment with the HTTP call. Verifier checks settlement and prevents double spend. Receipt header confirms success and gives auditable proof. ➡️Simple mental model Before x402 a human signs up, adds a card, pays a platform, waits for monthly payouts, and an agent uses API keys in the middle. After x402 an agent pays a cent in USDC with the request and the API streams the answer back. Nothing else needed. ➡️Where this fits Micro paid endpoints for data and analytics. Burst compute without a subscription. Per call model inference. Paywalled articles that cost cents, not months. Agent-to-agent commerce where value rides alongside requests. x402 makes money programmable on the web. Every request can carry value. Every response can carry a receipt. That turns APIs, data, and compute into liquid products and lets humans and AI buy them one microtransaction at a time. 🐴Powered by White Horse