What Agents Buy.

Independent reviews of the x402 APIs behind agentic commerce. I give an AI agent a real wallet, buy things with it, and publish every receipt.

Written by Neil·nothing here is sponsored·new? start here·how we grade

Danswerpool.ioA+A-api.anchor-x402.comAenrichx402.comA+groundcheck.seiche.infoCaeml-x402.zeabur.appAgas.apitoll.cloudA2s.ioCkeyronne.comAquartermaster.surewhynot.appAx402.halowerk.comA+anywaypossible.comA-signals.edge.reportA+api.nansen.aiCx402datasource.comFapi.jarvisclaw.aiCapi.thetrustlayer.xyzDapi.x402lint.devCmcp.fortclaw.comAblockrun.aiAapi.bitrefill.comDmcp.x402.boatsA+B-pro-api.coinmarketcap.comAstablememes.devDanswerpool.ioA+A-api.anchor-x402.comAenrichx402.comA+groundcheck.seiche.infoCaeml-x402.zeabur.appAgas.apitoll.cloudA2s.ioCkeyronne.comAquartermaster.surewhynot.appAx402.halowerk.comA+anywaypossible.comA-signals.edge.reportA+api.nansen.aiCx402datasource.comFapi.jarvisclaw.aiCapi.thetrustlayer.xyzDapi.x402lint.devCmcp.fortclaw.comAblockrun.aiAapi.bitrefill.comDmcp.x402.boatsA+B-pro-api.coinmarketcap.comAstablememes.dev
25bought and graded
53agent calls this week

I pay for these APIs with my own wallet and publish what happened. The volume this market gets quoted by is mostly wallets paying themselves, so I read the payments off the chain myself. I check whether the answer that comes back is actually right, against a source that cannot be the seller. And the verdict an agent gates on is backed by money that moved. Every weight and threshold behind that is published at how we grade. The sweep covers every USDC payment agents make on Base and Solana, every day. Free MCP server for your agent →

Why this differs from the x402 dashboard total

This headline counts USDC received at the seller wallets we track, on Base and Solana, over the last complete UTC day. Of it, $23,713 settled on Base and $80,287 on Solana (Solana is mostly Bitrefill and Laso). The /x402 dashboard sweeps Base only, so it shows roughly the Base portion; a rolling-24h window there also differs from a calendar day by a few percent. Every figure on this site carries its scope for exactly this reason.

Before you let an agent pay an API

25 checks, in the order you hit them. Every one comes from getting it wrong with real money on this site, and every line links to the receipt. If you only read one page here, read this one.

Before you call

  1. 1There is no single catalog. Two public registries exist and neither is the whole market. why
  2. 2Ignore registry usage counters. One credited 4,201 calls where the chain showed 131,803 in a day. why
  3. 3Call it the way the schema says. A GET to a POST-only endpoint reads as a dead service, not a mistake. why
  4. 4Check the declared method twice. Some paywalls charge before they route, so a wrong verb costs money and returns HTML. why

Reading the price

  1. 5Read the live 402 for the price. Never the docs, never the registry listing. why
  2. 6Look in three places. 63% of sellers put the challenge only in a header, so a body-only parser sees nothing. why
  3. 7Check the asset's decimals. USDC is 6; BNB-chain tokens are 18. Assuming 6 turned one cent into ten billion dollars here. why
  4. 8One endpoint can quote several prices. Compare the options before picking one. why
  5. 9Price does not always scale with the request. Some sellers charge the same for a tenth of the work. why
  6. 10Quotes expire, sometimes in 30 seconds. Do not think for a minute and then pay. why

Before you pay

  1. 11Call the free endpoint first. Several sellers answer the same question for nothing on another path. why
  2. 12Check whether the cheap action needs state you can only buy. A three cent call can have a nine dollar entry fee. why
  3. 13A published quote is not a promise. Some sellers only accept their own client. why
  4. 14Ask for a route that cannot exist. Anything that quotes you a price for it is billing on nothing. why
  5. 15A changing payment address is usually fine. Some sellers mint a fresh one per request; probe twice before accusing. why

After you pay

  1. 16Reconcile against the chain. Your client reporting no payment is not proof that no payment was made. why
  2. 17Check the goods against the promise. Reputation scores cannot see a service that is reachable, well-formed and simply does not deliver. why
  3. 18Keep the block number, not the clock. A timestamp cannot be reproduced; a block height can. why
  4. 19Confirm you got what you paid for. Two differently named models returned the same weights on one router. why
  5. 20A ticker is not an asset. Asking for BTC returned 13 candidates; taking the first is how you get the wrong one. why
  6. 21Read payTo from the challenge every time. 89 counterfeit addresses now sit in one buyer's history, all rendering identically to the real one. why

Reading the market

  1. 22Money arriving is not a sale. Several top earners pay almost all of it straight back out. why
  2. 23Many storefronts, one operator. Wallet addresses collapse brands that look independent. why
  3. 24A catalog fetch that stops early looks exactly like a complete one. Floor-check every pull against the last. why
  4. 25Never read a registry call counter as demand. One service sells the number outright, $190 a year to pay your own endpoint twice a month. why

The long version of each is in the field notes. How the protocol itself works is in how to pay an x402 endpoint. What happened when I paid these services is in the ratings.