Coinbase presents x402 Bazaar, the AI agents’ “marketplace”: they pay APIs in 200 ms and configure themselves

x402 introduces a bazaar of services for AI agents with centralized discovery, machine-readable metadata, and automatic API payments in stablecoin. The model is pay‑per‑request, with no accounts or subscriptions, to enable autonomous workflows and reduce integration friction. According to the official documentation Coinbase Docs and the launch materials published on September 10, 2025 Coinbase Launch, transactions can be completed in approximately 200 ms, a value reported in the materials but still to be verified with independent tests on real loads and production networks.

We have examined the specifications and compared the stated metrics with third-party reports: industry articles published at launch highlight settlement paths on Base with very low gas costs (nominally less than 0.0001 USD in launch materials). Industry analysts also note that, while promising for micropayments and automated discovery, measuring the actual end-to-end latency will require independent benchmarks in enterprise environments and realistic load conditions.

What is x402 Bazaar and why it matters

x402 Bazaar is a machine-readable index where agents find compatible endpoints, read metadata (prices, limits, requirements), and initiate transactions in USDC integrated into the HTTP call. It is not a simple list: the system significantly reduces integration times and enables autonomous adaptation of agents to the most suitable tools. In this context, the impacts on scalability and time-to-value are significant; the project was officially presented on September 10, 2025, by Coinbase and accompanied by technical documentation and a demo.

How it works: discovery and payment in the same round

• Query the catalog: the agent queries the bazaar and receives structured responses that include information on compatibility, policy, and prices.
• Endpoint selection: the agent selects the endpoint based on cost, latency hint, reliability, and specific requirements.
• Request + payment: the agent sends the call with integrated payment (via the x402 protocol), which the endpoint verifies and confirms.

The result is consumption-based billing: credentials, subscription plans, and monthly invoices to manage disappear. That said, control remains within the agent’s perimeter and its policies.

Performance and Sources

The declared latency of about 200 ms is reported in the official documentation Coinbase Docs and in the release notes of September 10, 2025. Tests and technical journalism reports at launch also highlight that the settlement path on Base aims for extremely low transaction costs (the presentation material mentions nominal gas below 0.0001 USD), but these numbers will need to be verified through independent benchmarks in production contexts and with variable loads.

What changes for developers and providers

• Less static agents: agents can discover new APIs and adapt in real-time without the need for updated manual releases.
• Pay‑per‑request: the model lowers the commercial barrier and encourages the creation of granular services.
• Time‑to‑market: integrations are faster thanks to standardized and easily interpretable metadata.
• Observability: prices, limits, and requirements are transparent during runtime, facilitating monitoring and audit.

A use case, narrated in 30 seconds

Imagine an agent organizing a weekend: it checks the weather, compares local events, purchases two tickets, and updates the calendar. Each operation queries different services, selects the most convenient endpoint, and pays through micropayments included within each request. In fact, everything happens without managing complex accounts or billing issues, keeping the flow cohesive and very sensitive to latency.

Key Technical Components

• Machine-readable index: describes endpoint, methods, pricing, rate limits, and policy requirements, making the system easily integrable by automated software.
• Integrated wallet: allows instant micropayments in stablecoin (such as USDC), enabling pay-per-use transactions.
• Protocol x402: leverages the HTTP status code 402 “Payment Required” RFC 9110 to integrate payment directly into the HTTP call, innovating the traditional use of the code.
• Metering and reporting: the system generates signed logs that facilitate audit and transaction reconciliations.
• Registration policy: guidelines are established to ensure quality, security, and governance within the catalog.

Risks, Limits, and Concrete Countermeasures

Greater autonomy involves the expansion of risk surfaces. To mitigate these issues, x402 Bazaar offers various practical solutions.

• Undesired spending: agent budgets, endpoint spending limits, and service allowlist are implemented, along with time window-based restrictions.
• Abuse and fraud: client-side request signing, attestations provided by the endpoint, rate limiting, and dynamic blacklists help prevent fraudulent behavior.
• Catalog quality: identity verification of providers is conducted, periodic reviews are performed, and de-listing policies are applied, supported by reputation systems.
• Compliance: immutable logs, role separation according to the principle of least privilege, and the use of sandboxes and testnets ensure accurate controls.
• Interoperability: metadata consistent with HTTP standards are adopted, along with clear specifications on SLA and latency.

Immediate Adoption Scenarios

• Data marketplace and real-time feeds;
• Content generation (images, videos, text) for consumption;
• Scraping and information aggregation with granular payments;
• On-demand business automation and just-in-time integrations;
• Financial research with premium datasets and instant pricing;
• Autonomous services (fleet, IoT, API‑first) with integrated accounting.

The questions that matter (to decide whether to integrate now)

• Is the expected latency compatible with my SLAs?
• What spending limits and controls will I implement for each agent and service?
• How will I manage the reputation and revocation of non-compliant endpoints?
• Do I have signed logs and adequate audit procedures for reporting?

FAQ

Can agents pay for any listed API?

Yes, as long as the endpoint supports the x402 protocol and is registered in the bazaar, which clearly displays compatibility, prices, and limits.

Do you need a traditional account?

No: the pay‑per‑request model integrates payment directly into the HTTP request. Management tools such as budget and agent-side control policies remain necessary.

Official Resources

• Documentation x402 Bazaar: docs.cdp.coinbase.com/x402/bazaar
• Repository and specifications: github.com/coinbase/x402
• Project site: x402.org
• Standard HTTP (402 “Payment Required”): RFC 9110

Conclusion

With x402 Bazaar, the AI agents evolve from static systems to self-adaptive entities: they discover new services, make instant payments, and orchestrate autonomous workflows in on-demand mode. The potential impact on innovation, speed of adoption, and process automation is high; however, the final maturity will depend on security, governance, and validation through independent benchmarks conducted in real production scenarios.