How to find an x402 API your agent can pay for

Is there a directory of x402 services?

Public directories include Coinbase’s x402 Bazaar. A listing helps you find a URL, but you still need to check whether it suits your task and what its current payment terms are.

x402scan is an ecosystem explorer where anyone can register a URL, and it lists the URL automatically if it serves a valid x402 payment challenge. Other facilitators and marketplaces keep their own lists too.

Agents Trust helps you find candidate endpoints. Browse by the kind of work on Browse endpoints, or ask it a question on Recommend.

Does a listed endpoint actually work?

A catalog entry does not guarantee that a URL answers today or delivers a useful response after payment. Read the returned liveness, freshness and delivery evidence, then check the endpoint yourself before signing a payment.

How does an AI agent discover paid APIs it can use without me signing up for anything?

x402 removes the account. A paid endpoint answers an unpaid request with HTTP 402 and its terms, the agent signs a stablecoin payment, and it sends the same request again with the payment attached. There is no key to provision and no checkout, so the only thing the agent still needs is the right URL.

Agents Trust answers that part with one GET. The agent sends need= with a short description of the work, and Recommend returns three candidate URLs by default (up to five with limit=5), each with the evidence behind it. It is itself an x402 endpoint, so the agent pays for it the same way it pays any other. A query costs 0.01 USDC, and a search that finds nothing is not charged. Agents can read llms.txt or install the Agents Trust skill to learn the call.

How does Agents Trust choose what to show?

Recommend returns candidates for the task you describe. Read each pick’s match strength, explanation, URL, price, networks, liveness, freshness, delivery status and risk flags before choosing one. A weak match needs particular care: it may not meet your requirements.

Use max_price_usd and chain to express your constraints. Evidence can be old or unknown, and not_tested means delivery is unknown. Fetch the endpoint’s own 402 before paying. The Recommend reference describes the request and response fields.

My agent needs a weather API it can pay for per call. How do I find one?

Ask Recommend. The website’s demo needs ("weather", "crypto prices", "web search") answer without payment, so this call works from any terminal as written.

curl "https://api.agents-trust.com/recommend?need=weather&limit=3"

On 12 October 2026 the first of three picks came back like this, trimmed to the fields that decide whether to call it.

"url": "https://api.strale.io/x402/weather-lookup",
"match_strength": "weak",
"price": { "min_usd": 0.054, "max_usd": 0.054 },
"networks": ["eip155:8453"],
"is_live": 1,
"probe_age_hours": 21,
"delivery_verification": { "status": "verified", "http_status": 200 },
"reason": "Nearest available match, not confirmed. It shares weather with your request. It recently answered an x402 liveness check. Both endpoint and seller evidence are available. Calls start at $0.054."

Read match_strength and the reason before you pay. A weak match is the nearest thing found, so check the endpoint’s description and input contract against your task. Then fetch the endpoint’s own 402 and compare its current price with your cap before signing.

Any other need answers 402 first, with the terms in the PAYMENT-REQUIRED header and payment on Base or Solana. The handshake is shown in three clients on the docs page.