How AI agents find x402 APIs: Agentic.Market, the Bazaar and Polygon Agentic Services

Updated 2026-11-10

Weekly companion: x402 real demand, the routes and categories with real repeat use once bot sweeps are filtered out, updated every Monday.

An x402 API answers an unpaid call with HTTP 402 and a price, and the agent pays per call in USDC, with no account and no API key. That removes signup, but agents still need a way to find services. In 2026 there are four places they look. This page explains each one, as read on 2026-10-08, and how Tanod shows up in them.

1. Coinbase Agentic.Market

Agentic.Market is a public catalog of x402 services that Coinbase launched in April 2026. Humans browse it on the web; agents read the same data through MCP and an HTTP API (GET https://agentic.market/v1/services and /v1/services/search?q=, listed in its markdown index). According to Coinbase's launch post, its search runs over the services indexed by the x402 Bazaar, and a smaller set is curated with richer descriptions.

2. The CDP x402 Bazaar

The Bazaar is the discovery index behind Coinbase's facilitator. There is no signup form: a seller describes each route (method, path, input example, output schema) inside its 402 response, and the route is indexed after a client pays it through the facilitator. See Get discovered in the CDP docs. Every paid Tanod route carries this metadata.

3. Polygon Agentic Services

Polygon Agentic Services is a directory of x402 APIs paid in USDC on Polygon (marketplace). Sellers wrap an existing endpoint and set a price. Agents can read the catalog as a SKILL.md file or as JSON from /api/discover/routes. Tanod accepts USDC on Polygon as well as on Base, Solana and BNB Chain, and Tempo with MPP.

4. x402scan and MCP directories

x402scan lists x402 resources and their payments. MCP directories (Glama, PulseMCP, Smithery, the official MCP Registry) list MCP servers, which many agents use instead of raw HTTP. Tanod is one remote MCP server at https://tanod.dev/mcp (registry name dev.tanod/tanod).

Calling Tanod after you find it

For sellers

To be found, put complete discovery metadata in your 402 response (input example, output schema, a plain description), keep the endpoint up, and make sure each route has been paid once. Agents tend to try cheap calls first, so a low entry price and a small free allowance help.

Expect your Agentic.Market service record to start mostly blank. On 13 October 2026 we read 46 service records through its search API (queries data, search, pdf, crypto and weather). 33 were marked enriched and carried a description, a category (most often Data or Search), a provider URL and an integration type; the ones we looked at were established brands such as CoinMarketCap, CoinGecko, Messari and FlightAware. The other 13 had an empty description and category even when the seller published those fields in its own /.well-known/x402. Coinbase fills them by hand, so what you control is the per-route metadata in your 402: the service name, the route description, the schemas and the tags. The search shows those either way.

Related guides: How to get your x402 API listed (seller checklist), How to check if a crypto address is on the OFAC sanctions list, Weather forecast API without an API key, Currency exchange rates API (ECB reference rates). Back to tanod.dev or the guide index. Results are automated and heuristic.