x402's record week: Solana takes 38%, and Ramp hands agent wallets to 70,000 businesses

What Token Terminal's numbers actually show

Twelve days ago we published an analysis of the x402 volume decline — dollar volume down 93% from its Q4 2025 peaks — and argued the drop was composition, not collapse: the speculative traffic left, the metering traffic stayed. The data that landed this week is the other half of that argument, and it arrived faster than we expected.

Per Token Terminal figures reported by Crypto Briefing and Cryptonomist on August 24–25, the week starting August 17, 2026 recorded 8.7 million x402 stablecoin transfers — more than double the 4.1 million of the week before, and the busiest week of the year. For context on how flat the baseline was: weekly counts hovered near 2 million for most of 2026 and dipped below 1 million in March. The all-time record — 20.1 million transfers in the week of November 17, 2025 — still stands, but that week belonged to a different market, and the difference is exactly what makes the new number interesting.

In November 2025, the peak week moved about $10 million. The record week of August 2026 moved about $367,950 — an average of roughly four cents per transfer. Same protocol, opposite economy. The 2025 spike was speculation wearing a payments costume: meme-coin farming and airdrop fishing that happened to travel over a payment standard. The 2026 curve is what the standard was designed for — autonomous processes paying fractions of a cent to a few cents, millions of times, for API calls, data lookups and tool invocations. When the average ticket is four cents, nobody is farming anything. Something is being metered.

The Base monoculture is over

The second shift matters more than the record. At the November 2025 peak, USDC on Base accounted for 18.7 million of the 20.1 million weekly transfers — 93% of all activity. x402 was, in practice, a Base protocol with a multichain specification attached.

The record week of August 2026 looks nothing like that:

Solana went from 6% to 38% of x402 activity in nine months. That was always structurally possible — the protocol is an HTTP standard, deliberately chain-neutral: a 402 response advertises which networks and tokens the seller accepts, and settlement happens wherever both sides agree. What changed is that buyer platforms started choosing different chains. AWS AgentCore settles the OpenAI cookbook flow in USDC on Base; Ramp provisions agent wallets on Solana; Algorand's agent tooling drives its own traffic. Demand pools wherever the wallets are, and the wallets now exist on four networks.

One thing didn't fragment: the money itself. By protocol analytics cited in the same coverage, more than 99.99% of x402 agentic transfer volume is denominated in USDC. The chains compete; the unit of account is settled. Agents buy in digital dollars, full stop — which is worth remembering every time someone frames agentic payments as a bet on a token.

Ramp: the week the corporate buyer arrived

The chart is the context. The announcement is the news. On August 20, 2026, Ramp — the corporate spend-management platform used by more than 70,000 businesses — integrated x402 into its agent tooling. Per Ramp's own agent-skills documentation, a company can now provision an agentic USDC wallet, grant an agent a scoped x402:write permission, and let it pay an HTTP 402 payment challenge from a seller autonomously — with the spend attributed, governed and audit-trailed inside the same platform where the finance team already manages cards and reimbursements.

Read that against the calendar. On August 13, OpenAI and AWS published the cookbook that made the agent's wallet a managed cloud service. Seven days later, the buyer side reached corporate finance software. This is now a weekly cadence: each announcement takes the question "how would our agent safely pay for something?" away from another category of company — first developers on AWS, now any business whose finance stack is Ramp.

And the governance shape is identical everywhere, which tells you it's the right shape. A human funds the wallet and sets the boundary before the task runs; the agent operates inside it without asking again; every payment is logged for the audit trail. The approval happens once, up front. Which means — same conclusion as the AWS story, now with 70,000 more companies attached — an agent mid-task will never stop to create an account on your website. Inside its budget, it can pay you in two seconds. Outside the set of endpoints that answer with a price, you don't exist.

What a record week of 4-cent payments means if you sell an API

Every number in this story is a demand-side number. The transfers, the chains, the wallets, the platforms — all of it measures the growing population of funded machines looking for something to buy. None of it adds a single seller. That asymmetry has been the constant across every x402 story this year, and it is the entire commercial argument:

• Buyers are being manufactured at platform scale. AWS ships agent wallets to its cloud customers; Ramp ships them to 70,000 finance teams; Coinbase and Cloudflare ship them to consumers and workers. The buyer side is a product race between very large companies.
• Sellers still have to opt in one by one. An endpoint becomes agent-payable only when its owner decides to answer a machine with a price instead of a login form. There are millions of commercial APIs, feeds, archives and tools that still respond with a signup page — invisible to every wallet in that record week.
• Four cents is a feature, not a failure. Per-call prices in cents are exactly what a budget-bounded agent can evaluate instantly, and exactly what card rails can't process economically. The record week is proof the metering model works at volume — 8.7 million times in seven days.

If you sell data, inference, search, enrichment, lookups or tools, the practical question stopped being "is agent demand real?" — the week of August 17 answered that with a number — and became "is my endpoint on the shelf those wallets can buy from?"

How Payzum fits: middleware in front of your API, not the facilitator

Worth being precise, because the roles in x402 get conflated constantly. Payzum is the middleware/proxy that sits in front of your existing API. Payzum is not the facilitator. On-chain settlement is handled by an external facilitator — Coinbase's today. What Payzum removes is the work that would otherwise sit on your sprint board: implementing the 402 handshake, verifying payment, guarding against replay, and forwarding the paid request to your real service.

You configure the endpoint you already run, the API key or bearer token it already expects, and a price. Payzum publishes an x402 URL, answers agents with the 402 and the terms, waits for settlement, then proxies the paid call to your real endpoint with your own key and returns the response. Funds are non-custodial: USDC on Base lands directly in a wallet you control, with roughly two-second confirmations. Payzum never holds, pools or routes your money — the settlement is the payment. Pricing is usage-shaped: around 1,000 transactions per month free, then roughly $0.001 per transaction plus gas. Your service keeps its current authentication, rate limits and deploy pipeline. Nothing about it changes.

On the multichain question, honesty first: Payzum's x402 settlement is USDC on Base — which the record week's own data shows is still the largest network on the rail at 48% of transfers, and the chain the AWS/OpenAI buyer stack settles on. The 402 handshake is the same HTTP standard on every chain, so being payable on the deepest lane today is how you're ready for the rest of them tomorrow. If you want the settlement mechanics, we've written up why USDC on Base fits per-request pricing in detail.

How it works, step by step

1. Connect the endpoint you already have. In the Payzum dashboard, paste your existing API URL and the key or bearer token it expects. No SDK, no protocol implementation, no redeploy of your service.
2. Set a price and a destination wallet. Choose what one call costs in USDC and the Base wallet where funds should land. Because settlement is non-custodial, that wallet is yours from the very first payment.
3. Payzum publishes the x402 URL. Agents that hit it receive an HTTP 402 with the price and payment details — the same challenge a Ramp-provisioned or AgentCore-managed agent is built to answer — and pay in USDC. Settlement is verified through an external facilitator.
4. The paid call is proxied to you. Payzum forwards the request to your real endpoint with your key and returns the response inside the same request cycle. Signed webhooks, a full audit log, 2FA and encrypted secrets cover every call, and you can watch the first one land with the integration playground and REST API.

Waiting vs. being x402-payable now — what actually changes

Two fair objections

"Counts doubled but the dollars are tiny. Why should $368k a week move me?"

Because you're not selling to the week — you're selling to the trajectory of the buyer side. The dollar total measures today's average ticket, and today's dominant use is sub-dime API metering; 8.7 million settlements in a week is the proof that the machinery works at exactly that ticket size. What compounds from here is the wallet population: AWS in May, OpenAI's cookbook on August 13, Ramp's 70,000 businesses on August 20. Readiness costs you a configuration form. Being absent when a funded agent looks for your category costs the sale, every time, silently.

"The fastest growth is on Solana, and Payzum settles on Base. Am I on the wrong chain?"

No — you're on the biggest one. Base carried 48% of the record week, the largest share of any network, and it's where the AWS/OpenAI buyer stack settles. More importantly, x402 is chain-neutral HTTP: the 402 challenge you publish today is the same handshake on every network, so nothing about your endpoint, your price or your integration is chain-locked. The multichain spread is good news for the standard you're adopting — it means the rail no longer depends on one network's roadmap.