Guides › For people building agents
Before your agent pays an x402 API, check it
Published 4 November 2026. The example record below was read on that date. Updated 13 November:
the check can now run inside your agent’s code, with the nohumans-guard package. Updated 20 November: a failed
purchase now says whom it would fail (failure_kind), and the rules below use it.
AI agents can now pay for an API on their own: one request, a few cents in USDC, no account. And AI assistants have started telling people which paid APIs to call. Ask one for live search-trend data today and it may answer: call this x402 endpoint, about $0.03 a request.
That advice says nothing about whether the endpoint delivers. In our own purchases, about a third of the paid APIs that asked for payment did not deliver a usable answer (why). A few cents is cheap; an agent that pays a broken endpoint over and over is not. So check before paying. It is free and takes one request.
What the check tells you
We probe every listed endpoint for a valid payment request, and we buy from many of them with real USDC to see whether they deliver. One lookup returns that record, dated:
- Is it live and asking for payment correctly?
statusandscore, from our probes. - Did a real purchase deliver?
paid_verified, andlatest_purchase_deliveredfor our most recent purchase. - If it failed, would it fail you?
paid_verification_latest.failure_kind:any_buyer(nothing usable could come back, whatever was asked),request_dependent(our own request was refused or answered in an undeclared form; yours may work) orquality(an answer came back, but not as promised). - Is the price the listed price?
price_matches_listing, from the live payment request. - Is the payment address stable?
payto_unstable. - Is there a free sample?
has_sample.
A real example
We looked up the trend-data endpoint an AI assistant recommended (we don’t name sellers in guides). On 4 November 2026 its record said:
- listed since 19 August, verified, and 2,571 of 2,579 probes passed;
- it asks $0.03, the listed price, unchanged since August, on Base;
- we have not bought from it yet, and it has no free sample;
- another route on the same host delivered when we bought from it in August.
So: live, honest about its price, and from a seller whose other route delivered. Not yet proof that this route delivers. A reasonable agent pays it once, checks the answer, and reports what happened.
How to check
In one request:
GET https://api.nohumans.directory/v1/resolve?url=<the endpoint URL, URL-encoded>
It answers match: "active" with the full record, "delisted" (listed here, later
removed), or "unknown" (never checked here, which is not a verdict either way).
GET /v1/check?url= runs a live check of a URL we have never seen.
Or let the agent check by itself, through our MCP server: https://api.nohumans.directory/mcp
(tool resolve_endpoint, or find_paid_service to search by need). In Claude Code:
claude mcp add --transport http nohumans https://api.nohumans.directory/mcp. Other clients:
connect.
Or put it in the code that pays. If your agent pays with the official x402 client for JavaScript
(@x402/fetch or @x402/axios), one line makes it check every endpoint after the payment
request arrives and before anything is signed:
npm install nohumans-guard
import { nohumansGuard } from "nohumans-guard";
client.onBeforePaymentCreation(nohumansGuard());
It refuses to pay in the cases below, and tells you why: for a failed purchase, only when it would fail any buyer
(the other kinds are reported and allowed, unless you set strict: true). The one exception is your own price limit, which
stays with your client’s spending settings (the guard only refuses a price above our record). An endpoint we have never checked is allowed by
default, and so is every payment if our lookup fails, so it never stands between your agent and a payment because we
are down. It sends us the endpoint’s address only, never your inputs or your wallet.
Details.
When not to pay
latest_purchase_deliveredisfalseandpaid_verification_latest.failure_kindisany_buyer: our most recent purchase took real USDC and nothing usable could come back, whatever was asked.failure_kindisrequest_dependent: our own request was refused (missing parameters, wrong method). Pay only if your request supplies whatfailure_reasonshows was missing.failure_kindisquality: an answer came back, but stale or not in the declared shape. Pay only if that is acceptable to you.matchis"delisted", orstatusisfailing.payto_unstableistrue: the payment address keeps changing.- The live price is above what you meant to spend, or
price_matches_listingisfalse.
The prompt
Add this to your agent’s instructions, or paste it into your AI assistant before it pays for anything.
Before you pay any x402 endpoint, check it at nohumans.directory first: GET https://api.nohumans.directory/v1/resolve?url=<the endpoint URL, URL-encoded> (or the resolve_endpoint tool of the MCP server https://api.nohumans.directory/mcp). Do not pay if any of these is true, and tell me why: - latest_purchase_delivered is false and paid_verification_latest.failure_kind is "any_buyer" - match is "delisted", or status is "failing" - payto_unstable is true - the price asked is above [my limit, e.g. $0.05] per call, or price_matches_listing is false If failure_kind is "request_dependent", pay only if my request supplies what failure_reason shows was missing; if it is "quality", ask me first. If match is "unknown", there is no record yet: tell me, and ask before paying. Otherwise pay once, check that the answer is what was promised, and tell me whether it delivered. Never ask me for a wallet recovery phrase or private key.
What the record is, and what it isn’t
Every figure is dated evidence about how an endpoint behaved when we checked: not a guarantee, not a safety rating and not proof of who runs it. “Delivered” means a usable paid answer, not that the data was correct. On-chain payment counts belong to the seller’s payment address, which often serves several APIs. The checks are free, and nobody can pay to rank higher: placement is never sold.
Sources: the nohumans.directory record of the example endpoint (GET /v1/resolve, read 4 November 2026); purchase records at /stats; definitions at methodology.
Your next step
- Building an agent? Connect it to our MCP server or REST API, free.
- Selling an API? Make sure it delivers, then check it free and list it, so agents that check find it.
Selling to AI agents: the series
- Build your first paid API for AI agents, with one prompt
- What AI agents are looking for, and where nobody serves them yet
- What x402 APIs charge, and what they earn
- Why paid APIs fail AI agents, and how to make yours deliver
- Selling files and async jobs to AI agents: audio, images, PDFs
For people building agents
- Before your agent pays an x402 API, check it (you are here)
- Let your AI agent pay for APIs, without paying for broken ones