Which companies support x402? The x402 ecosystem in 2026, mapped by role

This is our map of the x402 ecosystem in 2026: who governs the standard, who verifies and settles payments, which networks it runs on, which clouds and platforms ship it, which wallets let agents buy, and who sells. Every fact carries a date and a source. We wrote it from the seller's side, because that's where we sit. Payzum is a non-custodial, stablecoin-first crypto payment processor: payments settle directly to wallets the merchant controls. For x402, Payzum is the middleware in front of a seller's existing API. It isn't a facilitator, and nothing below claims it is.

The x402 ecosystem in 2026 at a glance

x402 revives HTTP's 402 Payment Required status code. A client asks for a paid resource, the server answers with a price, the client signs a stablecoin payment and retries, and the server returns the resource. That simple loop needs six kinds of company around it. Here they are, as of 19 October 2026:

If you're new to the protocol itself, start with what x402 is and how pay-per-call works. This page is the map. The rest of our x402 coverage is linked from the layer it belongs to.

Why "which companies support x402?" is harder than a logo wall

Ask an AI assistant or a search engine who supports x402 and you'll usually get a list of famous names. The list is accurate. It's also hard to use, because it mixes four very different things:

• Governance. A company pays to sit at the table where the standard is written. Premier membership costs $200,000 and comes with an appointed seat on the Governing Board, according to the Foundation's member page. That's a commitment to the standard, not a product you can buy.
• Live products. A facilitator that settles payments today, a wallet an agent can spend from, a cloud service with a general-availability date.
• Previews and waitlists. A product that exists for some customers, in some countries, behind an access request.
• Announcements. A contribution to the spec or a roadmap line, with no date for a product.

Block is a good example. On 24 September 2026 it joined the Foundation and contributed Bitcoin Lightning support to the spec. Its announcement gave no date for Square, Cash App or Bitkey to use it (our analysis). Both of those statements are true at once: Block supports x402, and a Square seller can't take x402 payments through Block today.

The usage numbers need the same care. The x402.org homepage shows a "last 30 days" counter of 75.41 million transactions, $24.24 million in volume, about 94,060 buyers and 22,000 sellers. When we checked it on 19 October 2026, it showed exactly the figures it had at the July launch, so treat it as a snapshot, not a live feed. Independent audits found that a big share of the 2026 headline volume was bridges and loops, not agents buying things (the first x402 audit).

What a wrong read of the x402 ecosystem costs a seller

If you sell an API, a dataset or an MCP tool, the map matters because each wrong turn has a concrete cost:

• Building on a network nobody settles. The x402 docs separate "protocol support" from "production support." Any EVM chain can be described in the protocol, but you still need a facilitator that settles on it in production. Pick a chain without one and you've built an endpoint that can't be paid.
• Waiting for a logo to ship. Teams hold off "until Visa or Stripe does it." Card networks govern x402 but don't sell x402 endpoints. Stripe's x402 support is real but in preview: US businesses in all states except New York, other countries by request. Meanwhile, buyer wallets already work on the open protocol.
• Missing where the money lands. In x402 the facilitator doesn't decide who gets paid. The seller's payTo address does. Some platforms set that address to a deposit account they control, which puts your revenue in a platform balance. That can be fine, but you should choose it on purpose.
• Over-building. Some teams spend weeks implementing batch settlement or payment channels for an endpoint that hasn't had its first paid call. The audit we covered found a median Base seller earned about $2.50 in August 2026. Start by being reachable and add complexity when the demand shows up.

How x402 splits the work: client, server, facilitator, wallet

The ecosystem looks crowded because the protocol deliberately splits one payment into separate jobs, each of which a different company can do:

1. The client (an agent, an app or a script) makes the request. When it gets a 402, it signs a payment from its wallet and retries. On EVM chains with USDC, it signs a transfer authorization (EIP-3009). It doesn't broadcast a transaction itself, which is why a one-cent call is practical.
2. The resource server (the seller) states the price, the asset, the network and the payTo address, then serves the request once the payment checks out.
3. The facilitator verifies the signed payment and submits it on-chain. The x402 docs are explicit: "Anyone can run a facilitator. You can run your own or self-facilitate."

Cards bundle all of that into one network with one rulebook and one acquirer holding the merchant relationship. x402 unbundles it, which is why so many companies can say "we support x402" while doing completely different things. For a seller, two questions sort the whole ecosystem: who can pay me (wallets and the buyers behind them), and where does the money land (your payTo address and whoever controls it).

1. Governance: the x402 Foundation

Coinbase released x402 in May 2025. In April 2026 it announced it would hand the protocol to a neutral body, and on 14 July 2026 the Linux Foundation announced the operational launch of the x402 Foundation and "the completed contribution of the x402 protocol by Coinbase," with 40 members. On 1 October 2026 it appointed Michael Hursta, a payments executive formerly at Amazon, PwC and First Data, as executive director, citing "more than 50 active members." We covered the launch in the x402 Foundation makes agent payments an open standard.

The Foundation's member page, checked on 19 October 2026, lists 57 organizations:

Two details matter more than the count. First, the Technical Steering Committee, which decides what goes into the spec, has three seats. The TSC.md file in the x402-foundation/x402 repository lists Coinbase (Erik Reppel, who created x402), Cloudflare (Rohin Lohe) and Stripe (Steve Kaliski). Second, the code is open. The repository is Apache-2.0 licensed, had about 6,700 stars and 2,200 forks on 19 October 2026, and ships official SDKs in TypeScript, Go and Python.

The Foundation isn't the only group writing rules for agent payments. Card networks and fintechs run parallel efforts, which we've covered separately: the Agentic Payments Alliance (26 founders, 18 August 2026), EMVCo's agentic payments framework (draft, 1 September 2026) and the Visa–Mastercard–Ant Know Your Agent framework (10 September 2026).

2. x402 facilitators: who verifies and settles payments

A facilitator checks the buyer's signature, makes sure the payment hasn't been used before, and submits it on-chain. The x402 docs keep a list of production facilitators, which they describe as "selected production options," not a complete catalog. On 19 October 2026 it had 15 entries:

Not every facilitator is on that list. Binance launched its own, B402, on BNB Chain in May 2026, and its Agentic Wallet settles through it (our coverage). The public x402.org facilitator is for testnets only. The docs say it is "not intended for mainnet routes."

The largest one by far is Coinbase's. Coinbase's developer docs, checked on 19 October 2026, say the CDP Facilitator "has processed more than 100 million transactions and $28 million in payment volume across Base and Solana alone." It supports Base, Polygon, Arbitrum, Monad, World and Solana, runs the exact, upto and batch-settlement schemes (Solana: exact and upto), and powers the x402 Bazaar discovery catalog. Coinbase's documented price is the first 1,000 on-chain transactions each month free, then $0.001 per on-chain transaction. Verification is free. Even Stripe's x402 integration settles mainnet payments through the CDP Facilitator, according to Stripe's own docs.

Payzum isn't on this list, because Payzum isn't a facilitator. It sits one step earlier, in front of the seller's API, and calls an external facilitator (currently Coinbase's) to verify and settle. More on that below.

3. Networks and assets: where x402 payments settle

The protocol is chain-neutral by design. The specs/schemes/exact folder of the x402 repository had a written scheme for 17 network families on 19 October 2026, and the docs' network and token support page spells out what each one can carry:

The docs also list four payment schemes. exact is a fixed price per call. upto lets a buyer authorize a ceiling and the seller charge actual usage. batch-settlement uses an escrow deposit with off-chain vouchers that are redeemed together. auth-capture holds funds in escrow and captures, voids or refunds them after the resource is served.

In practice, two networks carry most of the traffic. Token Terminal's data for the week of 17 August 2026, the busiest week of the year, counted 8.7 million x402 transfers: 48% on Base, 38% on Solana, then Algorand and Polygon (our breakdown). The asset is even more concentrated: TRM Labs found 99.6% of settled x402 value was USDC (MPP vs x402). Ripple brought the XRP Ledger and RLUSD in June 2026 (Ripple joins x402), and the Solana Foundation added payment channels for high-frequency calls in September (Solana Payment Channels).

4. Clouds and payment platforms

These are the companies that package x402 so their own customers don't touch the protocol. Dates are when each one shipped or announced:

• AWS. Amazon Bedrock AgentCore payments went generally available on 18 August 2026. It supports x402 and the Machine Payments Protocol, the metered upto scheme, and payment sessions with a spending cap and an expiry. AWS also added a "Monetize" rule to AWS WAF for CloudFront in June 2026. AWS is a premier member. (AgentCore payments GA)
• Cloudflare. It holds a Steering Committee seat. It launched the Monetization Gateway on 1 July 2026, on a waitlist and for assets behind Cloudflare (our coverage), then Cloudflare Wallets and cloudflare.pay identities on 4 August 2026, starting with handle reservations (our coverage).
• Google. Its Agent Payments Protocol (AP2) handles who authorized a purchase. Google built an x402 extension so AP2 agents can settle in stablecoins. Google is a premier member. (AP2 + x402)
• Stripe. It holds a Steering Committee seat and co-authored the rival Machine Payments Protocol. Its x402 support launched in preview in February 2026. Stripe's docs, checked on 19 October 2026, say the 402 response points the buyer to a Stripe deposit address, the payment is recorded as a PaymentIntent, and USDC is supported on Base, Solana and Tempo. Stablecoin payments are open to businesses in all US states except New York, and to other countries by request.
• Alibaba Cloud. It was the launch partner for Solana Payment Channels on 3 September 2026, with inference endpoints payable through channels from day one.
• Coinbase. Beyond the facilitator, on 23 July 2026 Coinbase let its roughly 5,000 Coinbase Business customers accept agent payments over x402 (our coverage).

5. Buyer wallets and agent platforms

This is the layer that grew fastest in 2026. Every launch below gives agents money they can spend on any endpoint that answers with a 402:

• Coinbase: the Agentic Wallet CLI and Coinbase for Agents. On 22 September 2026, Coinbase for Agents let trading agents pay per call from the user's USDC balance (selling market data to agents).
• Binance Agentic Wallet: added x402 on 13 July 2026, settling on BNB Chain, Base and Solana (our coverage).
• MoonPay PayBox: a self-custodial shopping wallet inside Claude and ChatGPT, announced 23 July and live 28 July 2026 (our coverage).
• Ramp: on 20 August 2026, gave its 70,000+ business customers agent wallets funded in USDC, with scoped permissions (our coverage).
• OpenAI Agents SDK + AWS AgentCore: a 13 August 2026 cookbook showed an agent paying 0.25 USDC on Base for an API call in about two seconds, within a budget set in advance (our coverage).
• MCP clients: by June 2026, the mcpc client paid x402-priced tools automatically (our coverage).

The demand is real, and growing fast. Chainalysis' North America report of 14 October 2026 counted more than 138 million x402 transactions on Base by the end of the third quarter. By then, the median wallet made its first x402 payment 18 minutes after being funded, down from 73 days in late 2025. Over 87% of payments were between a hundredth of a cent and ten cents. We read the report in detail in what AI agents buy.

6. Sellers and marketplaces

The seller side is where the ecosystem is thinnest, and it's the side we work on. Notable sellers so far:

• Apify made 20,000+ scraping and automation tools payable over x402 on 30 June 2026 (our coverage).
• Travala let agents search and book 2.2 million+ hotels, paying USDC on Base, from 5 June 2026 (our coverage).
• Massive launched US stock data with per-route x402 pricing on 1 September 2026 (our coverage).
• The x402 Bazaar, the discovery catalog powered by the CDP Facilitator, exposed 10,000+ pay-per-use endpoints to agents through AWS's Bazaar MCP server in August 2026 (our coverage).
• API providers using middleware. Most API businesses don't want to run x402 code. That's the gap Payzum fills (a practical guide, monetizing an MCP server).

There are also neighboring standards a seller will hear about. MPP, from Stripe and Tempo, is a second HTTP 402 standard that also supports cards (MPP vs x402). Proof's x401, launched 15 October 2026, handles agent identity and was designed to sit next to x402. Card networks run their own agent programs, such as Mastercard Agent Pay for Machines (our coverage) and virtual cards for agents (virtual cards vs x402).

x402 by the numbers: dated facts

Read together, these say three things. The infrastructure is mature and well funded. Real usage is growing but small in dollars. And most of the money is still waiting for sellers, which is good news if you have something agents want. For the long view, see what the 2026 volume decline really meant.

Where Payzum fits in the x402 ecosystem

Payzum works on the seller layer. It's the middleware, or proxy, in front of an API you already run. You set up three things in the Payzum dashboard: your existing endpoint, your own API key or bearer token for it, and a price per call. Payzum publishes an x402 URL. When an agent calls that URL, Payzum answers with the 402 and your price, has the payment verified and settled through an external facilitator (currently Coinbase's), then forwards the paid request to your real endpoint with your key attached. Your service doesn't change, and nobody on your team implements the protocol.

The money goes to you. Agents pay USDC on Base, and it settles directly to the address you set, a wallet you control. There's no Payzum balance in between, so there's nothing for us to hold back or freeze. Becoming a facilitator is a future goal for Payzum. Today we're not one, and we'd rather tell you that than blur it.

Outside x402, the same account handles the rest of your crypto payments: payment links, hosted checkout, invoices and subscriptions online, a POS at a counter, and stablecoin payouts. Security includes 2FA, signed webhooks, encrypted secrets and a full audit log.

How to join the x402 ecosystem as a seller, step by step

1. Pick one endpoint. Choose something an agent would buy one call at a time: a lookup, a quote, a scan, a search, a generated report. One route is enough to start.
2. Set a price per call. Most x402 payments are one to ten cents. Price the route by what a single answer is worth to the caller, and give expensive routes their own price.
3. Configure it in Payzum. Add your endpoint URL, your API key or bearer token (stored encrypted and never shown to the agent), the price in USDC, and the Base address that should receive the money. Payzum publishes the x402 URL.
4. Test the 402. Call the URL without paying and you get 402 Payment Required with your price. Pay from a test agent wallet and you get your API's normal response, with USDC settled at your address.
5. Tell buyers where to find you. Put the x402 URL in your docs, your MCP tool description and your llms.txt, so agents and the people who configure them can find it.

Here's what an agent sees:

# 1. The agent calls your x402 URL, unpaid
GET /v1/x402/<your-endpoint>
→ HTTP/1.1 402 Payment Required   (price: 0.01 USDC · network: Base)

# 2. The agent signs a USDC authorization and retries
GET /v1/x402/<your-endpoint>
X-PAYMENT: <signed EIP-3009 authorization>

# 3. Verified through the external facilitator, proxied to your API
→ HTTP/1.1 200 OK   (your API's response, unchanged)

Use cases: who should join the x402 ecosystem now

Here are six API businesses and the path that fits each one. Two of them aren't Payzum.

• A market-data API in Chicago. It sells quotes and options-flow data on monthly plans. Trading agents built on Coinbase for Agents want one data point per decision, not a subscription. It puts two routes behind Payzum, one cent per quote and five cents for options flow, and keeps its plans for human customers.
• A code-security scanner sold as an MCP tool. Chainalysis found security and code-analysis payments are a real category of agent spending. A two-person team in Berlin prices one scan per call, puts the x402 URL in its MCP tool description, and gets USDC in its own wallet without building a billing system.
• A company-enrichment API in Austin. Its buyers are corporate agents running on AWS AgentCore with a spending cap, or on Ramp wallets with scoped permissions. Those agents can't sign up for a plan, but they can pay a 402. The team prices each lookup and lists the endpoint in its docs.
• A weather and geodata API in Lisbon. It already runs behind its own gateway with API keys. It doesn't want a second codebase for agents. Payzum forwards paid calls with its existing key, so its backend sees normal traffic.
• A Bitcoin-only data shop: not Payzum. If it wants to be paid in sats over Lightning, it needs the Lightning x402 scheme, which requires running its own Lightning node. Payzum's x402 settles USDC on Base.
• A US SaaS that wants proceeds in its Stripe balance: maybe not Payzum. If it already runs on Stripe, is US-based outside New York and is happy with Stripe holding the funds, Stripe's x402 preview may fit better. If it wants USDC in its own wallet and no code, Payzum fits.

Ways to sell on x402, compared

There are several ways into the x402 ecosystem as a seller. We compared them on neutral criteria, using each provider's public documentation as of 19 October 2026. Cells say "not stated" where we couldn't verify a fact that day.

None of these locks you in. The buyer only sees the 402 and the payment it asks for, so you can change how you serve it later without changing anything for the agents that pay you.

Common objections about the x402 ecosystem

"x402 is just Coinbase's protocol."

It started at Coinbase. Since July 2026 it has been governed by the x402 Foundation under the Linux Foundation, with three companies on its Technical Steering Committee and 57 listed members, including direct competitors of Coinbase. The code is Apache-2.0 and anyone can run a facilitator. Coinbase still runs the biggest facilitator, and that concentration is fair to point out. It's also something you can change later without your buyers noticing.

"The volume is tiny, and part of it isn't real."

That's true. Audits found bridges and self-payments in the headline numbers, and most real payments are under ten cents. But the buyer side now has managed wallets from AWS, Cloudflare, Binance, MoonPay, Ramp and Coinbase, and new wallets start spending within minutes. Being payable is cheap. Waiting until the market is large means arriving after the sellers who were there first.

"We'll wait for Visa, Mastercard or Stripe."

Card networks help govern x402, but their agent products run on card rules. Stripe's x402 is in preview and settles into a Stripe balance. Waiting is a fine choice if you specifically need one of those. If not, the open protocol already works, and agents that pay one x402 endpoint can pay yours.

"Which chain should we bet on?"

You don't have to bet. Buyers pay from wherever their wallets are, and the market has settled on USDC, mostly on Base and Solana. Payzum's x402 uses USDC on Base, the network with the most x402 transactions to date. If your buyers are mostly on another network, tell us and we'll say honestly whether we're the right fit.