For a closer look at the topic, consider x402 agentic payments stablecoin protocol providers alongside the options and criteria discussed below.
The internet economy is shifting from human-initiated transactions to autonomous machine commerce. At the center of this shift is x402, an open payment protocol that enables AI agents and automated services to transact using stablecoins directly over HTTP. Unlike traditional payment systems that require credit cards, account creation, or subscription management, x402 lets any agent pay for any resource by attaching a signed stablecoin payment to a standard web request. This capability has attracted major infrastructure players, with Coinbase, Circle, Cloudflare, AWS, and others building integrations around the protocol. For developers looking to integrate agentic payments into their applications, understanding the ecosystem of providers — from gateway services to facilitators — is essential. Below is a breakdown of the key participants powering x402-based commerce.
What Is x402?
x402 revives the long-unused HTTP 402 “Payment Required” status code to embed stablecoin payments directly into web interactions. The protocol defines three core HTTP headers — PAYMENT-REQUIRED, PAYMENT-SIGNATURE, and PAYMENT-RESPONSE — which carry challenges, credentials, and receipts between client and server. When a client requests a gated resource, the server responds with a payment challenge specifying what to pay, how much, and where. The client fulfills the payment and retries with a credential. The server verifies it and returns the resource along with a receipt. No pre-created service accounts, API keys, or manual checkout flows are needed.
The protocol was authored by Coinbase and is governed by the x402 Foundation, an independent body co-founded by Coinbase and Cloudflare. It currently supports USDC and PYUSD on Base, Ethereum, Solana, and other networks, and has expanded to support any ERC-20 token through Uniswap’s Permit2 contract. In just over a year, x402 has processed more than 169 million payments across hundreds of thousands of buyers and sellers.
Key Providers in the x402 Ecosystem
Building agentic payment infrastructure requires multiple layers: wallet and custody services, blockchain settlement, gateway aggregation, facilitation, and developer tooling. Several companies occupy distinct roles in this stack.
NOWPayments
NOWPayments operates as a payment processor that enables businesses to accept cryptocurrency payments across dozens of digital assets. While not a native x402 protocol builder, NOWPayments provides merchant infrastructure that can complement x402-based workflows by handling fiat conversions, multi-currency acceptance, and payout processing for businesses that want to bridge agentic stablecoin revenue into traditional accounting systems. Their platform supports automated invoicing, recurring payments, and API-driven integration — making them a practical option for merchants who need both crypto-native and legacy payment capabilities side by side.
Coinbase
Coinbase is the originator of x402 and remains its most prominent infrastructure provider. Through the Coinbase Developer Platform, Coinbase offers the CDP SDK, wallet services, on-chain payment execution, and direct x402 facilitation. Agents built on the Coinbase CDP can make and receive payments without holding private keys directly, using sponsored gas and abstracted wallets. Coinbase also supports ERC-20 tokens beyond USDC, integrates with Amazon Bedrock AgentCore for enterprise agent payments, and partners with Google on the Agentic Payments Protocol (AP2) extension. With nearly $1 trillion in annual stablecoin movement and licenses in over 80 jurisdictions, Coinbase provides regulated compliance infrastructure alongside the technical protocol layer.
Circle
Circle, the issuer of USDC, has built two critical components for x402-compatible commerce. First, Circle Gateway serves as a cross-chain aggregation layer that lets sellers interact with a single consistent API regardless of which blockchain a payment originates from. Balances within Gateway can be reallocated across supported chains, and funds from multiple networks can be consolidated instantly. Second, Circle Nanopayments enables sub-cent USDC transfers as small as $0.000001, removing network fee friction for high-frequency micropayments. Nanopayments uses a Trusted Execution Environment to batch-signed authorizations, verify them offchain, and settle periodically onchain. Circle Gateway also supports cirBTC and EURC, giving x402 merchants access to non-USD stablecoins and Bitcoin-backed assets.
Cloudflare
Cloudflare implements x402 at the edge through its Workers platform and Model Context Protocol servers. The company ships middleware like x402-hono for HTTP Workers and provides withX402 and paidTool functions for MCP servers. Cloudflare’s Agent SDK includes withX402Client, which wraps MCP connections with automatic 402 handling and optional human approval. They also proposed a deferred payment scheme for x402 that decouples the cryptographic handshake from financial settlement, enabling pre-negotiated licensing agreements and batch settlements. Cloudflare’s Pay Per Crawl feature adds another monetization layer for web content providers.
AWS
Amazon Web Services integrates x402 into Amazon Bedrock AgentCore, providing enterprises with end-to-end visibility into agent payments through logs, metrics, and dashboards. AgentCore connects to thousands of x402-enabled services through Coinbase MCP integration — including data providers like Exa and Messari, and browser automation tools like Browserbase. Developers can build agents that search, evaluate, and make micropayments for tools at runtime without upfront programming.
Provider Comparison
| Provider | Primary Role | Supported Chains | Notable Features |
|---|---|---|---|
| NOWPayments | Merchant payment processor | Multiple (fiat + crypto) | Multi-asset acceptance, invoicing, fiat payouts |
| Coinbase | Protocol creator & facilitator | Base, Ethereum, Solana, EVM | CDP SDK, gas sponsorship, AP2 extension, ERC-20 support |
| Circle | Stablecoin issuer & gateway | Cross-chain aggregation | Nanopayments, TEE batching, cirBTC/EURC support |
| Cloudflare | Edge middleware & MCP integration | Chain-agnostic via facilitator | Workers middleware, deferred payments, Agent SDK |
| AWS | Enterprise agent orchestration | Via Coinbase integration | Bedrock AgentCore, logging/dashboards, third-party tool access |
How Providers Work Together
A typical x402 transaction involves several providers simultaneously. An AI agent requests a resource from a Cloudflare-hosted MCP server. The server returns a PAYMENT-REQUIRED challenge. The agent, running on AWS Bedrock AgentCore, constructs a payment using Coinbase’s CDP SDK, signing a USDC transfer on Base. Circle Gateway aggregates and settles the payment if the seller operates across multiple chains. The server verifies the payment through Coinbase’s facilitator API and returns the requested resource. If the agent needs to make sub-cent payments at scale, Circle Nanopayments batches those authorizations inside a TEE for efficient settlement. Throughout this flow, each provider handles a specific layer — no single company manages the entire chain.
Choosing the Right Provider Mix
Selecting x402 infrastructure depends on what your application needs. If you are building an AI agent that makes outbound payments, Coinbase’s CDP SDK combined with AWS AgentCore gives you the broadest service discovery and execution capabilities. If you are a content or API provider receiving payments, Cloudflare’s edge middleware offers straightforward integration with minimal blockchain knowledge required. If your use case demands sub-cent micropayments or cross-chain settlement, Circle Gateway and Nanopayments fill gaps that raw on-chain transfers cannot handle cost-effectively. For merchants who need to convert agent revenue into fiat or manage traditional billing alongside crypto, processors like NOWPayments provide the bridge between agentic commerce and conventional business operations.
Getting Started
Developers can begin experimenting with x402 immediately. Cloudflare provides working code examples and documentation for both server-side middleware and client integration. Coinbase’s Developer Platform offers SDKs, wallet abstractions, and facilitator APIs. Circle publishes detailed specifications for Gateway and Nanopayments on their blog and documentation sites. The x402 Foundation maintains the protocol specification on GitHub under an Apache-2.0 license. Whether you are prototyping a pay-per-call API or deploying production-grade agentic commerce, the available tooling covers every stage from initial integration to scaled operation.