Algorand Foundation's Aug 25 x402 workshop follows a 75M-transaction month

Most of the internet's payment plumbing was built for humans: forms, subscriptions, API keys, someone waiting to approve a charge. The web has had a status code for payment — HTTP 402, 'Payment Required' — but no standard way to execute it. The Algorand Foundation¹ is spending the summer teaching developers to build on x402, the standard that finally gives that code a job, and it is doing so at a moment when the protocol's own traffic counters and an independent audit tell sharply different stories about how large the machine-payments economy really is.

The next session of the Foundation's hands-on x402 workshop runs Tuesday, August 25 at 12:00 PM ET / 6:00 PM CEST, a roughly 90-minute build-along hosted by Sara Jane Kenny, a Technical Ecosystem Specialist at the Foundation, with registration open on the Algorand developer workshops² page.

The dormant status code that became a payments rail

x402, also called the Machine Payments Protocol, does not invent a new transport. It repurposes the existing 402 response code so the payment lives inside the ordinary HTTP request-response cycle. An AI agent or automated client requests a resource; the server answers with HTTP 402 plus structured payment requirements — which network, which token, what amount, which wallet should receive it, carried in a PAYMENT-REQUIRED header. The client signs and settles an on-chain transfer; a facilitator verifies that settlement, enforcing pricing and access rules and preventing replay or double-spend attempts; the client retries the request with a PAYMENT-SIGNATURE header as cryptographic proof; the resource returns in the same cycle. There are no accounts to create, no API keys to store and rotate, no KYC queue, no prepaid credits. A seller opens an endpoint to paid access with a single line of middleware, as x402.org³ puts it: 'That's it. Add one line of code to require payment for each incoming request. If a request arrives without payment, the server responds with HTTP 402, prompting the client to pay and retry.'

The protocol charges no fee of its own — users pay only the underlying network fee — and is deliberately chain-agnostic, with implementations on EVM networks, Solana, Algorand, TON and Stellar, and stablecoins, chiefly USDC, as the primary settlement asset. x402 began at Coinbase, which contributed the code to the Linux Foundation; the x402 Foundation launched operationally under Linux Foundation governance on July 14, 2026 with 40⁴ organizations signed on. Premier members include Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Ripple, Shopify, the Solana Foundation, the Stellar Development Foundation, Stripe and Visa. Linux Foundation CEO Jim Zemlin framed the stakes: 'AI agents and automated systems are becoming active participants in the global economy, yet they have lacked a native, secure way to transact.' The core protocol repository remains under active development, with commits landing as recently as August 20.

Algorand's role: workshop, facilitator, and a prize pool

Algorand is one settlement network inside that multi-chain standard, and the Foundation's x402 program runs three tracks: this workshop series, the Global x402 Challenge⁵, and a dedicated facilitator⁶ built with GoPlausible that verifies and settles x402 payments on Algorand, Base and Solana.

The Foundation's x402 materials argue Algorand's layer-1 is built for this traffic. The chain's roughly four-second deterministic finality — a block is final the moment it lands, with no probabilistic settlement — means an agent never has to implement confirmation logic or wait for several blocks before trusting a payment. Sub-cent transaction fees make the micropayments that dominate x402 traffic economically viable, and native atomic transaction grouping lets payment, authorization and usage logic settle together in one transaction group rather than in intermediate states. Smart-contract composability allows programmable pricing and access rules to be embedded directly in the payment flow.

The facilitator's public dashboard shows what that integration has carried so far: $278.6K of all-time settled volume across 537.3K settlements — a 99.16% verify-to-settle success rate — from 926 unique payers, with an average settle time of 0.5 seconds. By event count, 78.5% of the facilitator's all-time traffic sits on Algorand Mainnet (853.4K events), against 15.4% on Base and 6.2% on Solana.

The prize track carries the same thesis to developers: $100K USD⁷ plus 500K⁸ ALGO, administered by Algorand Foundation Cayman, for teams that launch a paid API endpoint on Algorand Mainnet and drive real usage through the GoPlausible facilitator, with ten finalists presenting at Devcon 8 in India. The rules are designed to force real commerce rather than demo traffic — an entry is not competition-ready until at least one real Mainnet payment has settled, USDC lands in the team's payTo address, and the endpoint appears in the Bazaar discovery catalog under the x402-global-challenge tag. As of this outlet's most recent look at the leaderboard, the challenge had passed 60 live paid endpoints with $19.8K settled. Underneath it all sits the decentralized base: Nodely's telemetry counted 2,695 full-time mainnet nodes on August 19.

What the traffic counters and the audit each show

The trailing-30-day counter published on x402.org is the number most coverage quotes, and the one an independent audit does not reproduce. x402stats.io⁹, a read-only data project that publishes raw and filtered figures side by side, applies an organic filter: a wallet's revenue counts only if it cleared at least $100¹⁰ in the window, drew at least three distinct buyers, shows an average payment of at least $0.001¹¹, and is not a known facilitator settlement wallet. The methodology is blunt about why the filter exists — raw on-chain totals count wash trading, self-dealing and facilitator settlement flows as seller revenue.

Source: 12 x402.org

Reported (raw)Organic (filtered)

The same audit that produces the filtered figure is unsparing about what remains: 73% of volume sits in 10¹⁶ wallets, just 84 wallets cleared the organic bar out of 47.3K that received anything at all, and the tracked economy contracted over the last week — daily volume and the paying-agent count both fell 22%. Coinbase's facilitator clears 59.2% of the indexed 30-day volume. One caveat matters for Algorand specifically: the audit's index covers facilitators on Base and Solana, and the GoPlausible channel that handles Algorand settlement publishes its own dashboard instead. The audit's organic figure and the facilitator's all-time settled volume described above are different populations, not different opinions about the same money.

What the workshop will build

The August 25 session walks participants through two components of an x402-enabled system. The payer client automatically handles HTTP 402 responses, initiates the payment on Algorand, and retries the request with proof of payment — removing the human from agentic workflows. The payment-gated API responds to incoming requests with HTTP 402 when payment is required, verifies settlement on-chain, and grants access to the resource, using Algorand smart contracts to enforce access control and pricing rules.

It is the second run of the session: the same curriculum ran June 3, co-hosted by Kenny and Camilo Molano Herrera, the Foundation's Head of Builder Programs, and a recording is sent to registrants who miss the live session. An attendee's LinkedIn recap of the June session described hands-on work with the @x402/fetch and @x402/avm packages, the ExactAvmScheme, Algorand Testnet and algokit-utils, concluding: 'The future isn't just AI making decisions — it's AI making payments. And x402 is the standard that makes it possible.' The June build ran on Testnet; the challenge, by contrast, credits only Mainnet settlement with real USDC.

The sequence is deliberate: the workshop gets developers to a working testnet flow, the challenge leaderboard credits only mainnet payments that actually settle, and the standard's governance sits with the Linux Foundation. Whether the raw counters ever translate into revenue that a meaningful number of sellers keep will show up on the same leaderboards the Foundation is asking builders to climb.