Coinbase Bazaar · x402: Autonomous Agent Commerce on Base

Autonomous agents don't browse marketplaces the way humans do. They don't click ads, they don't read landing pages, and they certainly don't fill out contact forms. They speak protocols. That's why the intersection of Coinbase Bazaar and the x402 payment protocol is such a pivotal moment for agent commerce: it gives machines a native, cryptographically settled way to discover, negotiate, and pay for services—without a human in the loop.

Today we're breaking down how Bazaar-listed CDP facilitator routes work, how machine-indexed SKUs enable autonomous buyers, and how ignition-settled payments register catalog presence on-chain. If you're building agents that transact, this is the rails layer you've been waiting for.

What Is Coinbase Bazaar · x402?

The Coinbase Developer Platform (CDP) Bazaar is a discovery and routing layer for on-chain services—think of it as a programmable service catalog where sellers list capabilities and buyers (human or machine) can discover them via structured queries. The x402 protocol extends the familiar HTTP 402 Payment Required status code into a full machine-to-machine payment negotiation standard. Together, they create a closed loop: an agent queries Bazaar for a service, receives an x402 payment request, settles via Base USDC, and gains access to the resource—all in milliseconds.

This isn't theoretical. The plumbing is live. Sellers register SKUs through the Bazaar catalog, buyers discover them via the x402 marketplace API, and payments settle on Base through the Ignition payment router. The result is a commerce stack that agents can traverse autonomously, end to end.

Connect Agents via MCP + x402 in Under 5 Minutes

If you're already using the Model Context Protocol (MCP) to give your agents tool access, adding x402 payment capabilities is remarkably straightforward. MCP provides the semantic interface—your agent knows what a tool does. x402 provides the economic interface—your agent knows how much that tool costs and can pay for it. Together, they turn any MCP-compatible agent into a commercially capable actor.

Here's the minimal integration path:

• Step 1: Register your agent at the MCP agent connection endpoint. This provisions your agent identity and generates the x402 payment wallet linked to Base USDC.
• Step 2: Discover paid tools via the Bazaar catalog. Each SKU includes a structured manifest—input schema, output schema, pricing in USDC, and the x402 payment endpoint. Your agent parses this like any other MCP tool definition.
• Step 3: Execute and settle. When your agent invokes a paid tool, the x402 layer intercepts the request, presents the 402 challenge, your agent signs the payment authorization, and the Ignition router settles the transaction on Base. The tool response is released upon confirmation.

The entire flow—from discovery to settlement—happens without human intervention. Your agent sees a tool it needs, pays for it, and gets the result. That's the promise of agent-to-agent payments made real through open protocols.

Base USDC Contract Triage for Autonomous Buyers

Not all USDC is created equal when you're an autonomous buyer operating at machine speed. Base hosts multiple USDC contract implementations—the native Bridge-minted USDC and the Coinbase-facilitated USDC.e—and agents need to route payments through the correct contract or face settlement failures. This is where CDP facilitator discovery becomes critical.

The Bazaar catalog exposes facilitator metadata alongside each SKU. When an autonomous buyer queries a service, the response includes:

• Contract address for the USDC variant the seller accepts
• Facilitator endpoint for CDP-routed approvals (relevant for Coinbase-managed USDC flows)
• Settlement confirmation requirements—how many Base L2 confirmations before the resource is released

This metadata allows agents to perform smart contract triage automatically: inspect the required contract, verify the facilitator route, check wallet balances against the correct USDC variant, and submit the payment through the appropriate path. No hardcoded addresses. No manual contract lookups. The Bazaar catalog is the source of truth, and agents consume it programmatically.

For builders integrating XRPL T54 cross-chain settlement alongside Base USDC, the same catalog structure accommodates multi-chain payment metadata—meaning your agent can choose the cheapest or fastest settlement rail based on real-time conditions, all discovered through the same Bazaar query.

Machine-Indexed SKUs: The Catalog That Agents Read

Traditional SaaS marketplaces are designed for human eyes—feature lists, pricing tiers, comparison tables. Bazaar flips that model entirely. SKUs are machine-indexed, meaning every listing is a structured, queryable object optimized for programmatic discovery. Think of it as a product catalog where the primary reader is a JSON parser, not a person.

Each SKU object contains:

• Capability descriptor: What the service does, expressed in a machine-readable schema compatible with MCP tool definitions
• Pricing vector: Per-call, per-token, or subscription pricing denominated in USDC, with volume discount schedules encoded as conditional logic
• Payment endpoint: The x402 URL where payment challenges are issued and settled
• Reputation signals: On-chain settlement history, uptime metrics, and latency percentiles—all verifiable on Base

When an autonomous buyer searches the catalog, it's not keyword matching—it's capability matching. An agent that needs a smart contract triage API can query for services matching a specific input/output schema, filter by price range, sort by settlement latency, and select the optimal provider. This is agentic commerce at its most efficient: machines negotiating with machines using shared protocols and verifiable data.

And because ignition-settled pays register catalog presence, every successful transaction reinforces the seller's visibility. More settlements mean stronger reputation signals, which mean more autonomous buyers discover and select that SKU. It's a virtuous cycle powered by on-chain proof of delivery.

FAQ

What is the x402 protocol?

The x402 protocol extends the HTTP 402 Payment Required status code into a machine-to-machine payment negotiation standard. It allows autonomous agents to discover a service's price, submit payment authorization, and receive access—all through standard HTTP interactions without human intervention.

How do agents pay for services on Coinbase Bazaar?

Agents pay using Base USDC through the Ignition settlement router. When an agent invokes a Bazaar-listed service, it receives an x402 payment challenge, signs a payment authorization from its linked wallet, and the transaction settles on Base. The service response is released upon on-chain confirmation.

Can I use MCP tools alongside x402 paid services?

Yes. MCP provides the semantic interface for tool discovery and invocation, while x402 adds the economic layer for paid services. Any MCP-compatible agent can be extended with x402 payment capabilities by connecting through the agent connection endpoint and provisioning a Base USDC wallet.

What is CDP facilitator discovery?

CDP facilitator discovery is the process by which autonomous buyers identify the correct USDC contract and facilitator endpoint for a given Bazaar-listed service. The Bazaar catalog includes facilitator metadata—contract addresses, approval endpoints, and settlement requirements—so agents can programmatically route payments to the right contract without manual configuration.

Start Building on the Agent Commerce Rails

The infrastructure for autonomous agent commerce is live and composable. Coinbase Bazaar provides the discovery layer. x402 provides the payment protocol. Base USDC provides the settlement rail. MCP provides the tool interface. Together, they form a complete stack for agents that discover, pay, and transact without human intermediation.

Whether you're listing services as a Coinbase Bazaar seller or building autonomous buyers that consume them, the on-ramp is straightforward. Connect your agents, provision your wallets, and start transacting on the only marketplace built for machines.

Ready to list your first SKU or connect your first paying agent? Get your Bazaar-listed pulse now and join the agent commerce ecosystem.