List your API
nohumans.directory is where AI agents look for paid services before they spend money. If you run an API that charges per call with x402, this page lists it in three steps: check it (free), describe it, and list it. Everything here uses the same public API an agent would use, with the same rules.
What listing does for you
- Agents can find you. Your listing appears in our search (
/v1/discover), in our MCP server'sfind_paid_servicetool, and in the record an agent fetches before paying. - We check it, so agents trust it. We probe your endpoint with unpaid requests from the first couple of minutes onwards and keep probing it. A short run of clean answers makes it verified; the status follows every probe after that. Nothing on this site can buy a status or a place in the results.
- A real purchase is included. The $0.25 fee includes one real purchase of the endpoint by our buyer, with real USDC, within 48 hours of the listing first verifying, if it verifies within 7 days and quotes $0.05 or less per call over HTTP 402. The result is published on your listing with its transaction. A delivered purchase is the strongest evidence an agent can see, and the pay rules we publish for agents check it first.
- You stay in control. You get a private claim token to edit or remove the listing at any time.
- You see what agents ask for. What agents search for here is public and free: /state/demand. It is the best list we know of what to build next.
Endpoints whose URL path is /mcp or under /mcp/ list free (no purchase is
included: our buyer cannot pay over MCP yet). An endpoint listed before can be listed again for free.
A submission that fails a check is never charged. Full rule.
1. Check your endpoint (free)
We make one live check, now, with the same unpaid requests our prober starts with, and tell you what we see: whether it asks for payment correctly, the price and network we read from it, and anything that would stop it from verifying. Nothing is created or charged.
The exact address an agent would call, including any example parameters it needs. It must be
https. Calling it without paying should answer 402 Payment Required.
2. Describe it
This is what agents read when they decide whether your API fits their task. Plain and specific beats clever.
Up to 120 characters.
Up to 2,000 characters. Say what goes in, what comes out, and any limits.
Pick an existing category where one fits (the list fills as you type).
What your endpoint charges. Step 1 fills it from your live price; agents always pay what your endpoint asks, so keep the two the same.
A free route that returns an example answer without payment. Agents use it to see what they will get before paying. It must answer 200 with JSON, and must not be the paid URL itself.
Used only for status notifications about this listing, as our privacy page says. Never published.
3. List it
Run step 1 first: it tells you whether a fee is due.
How paying from a browser wallet works
- You need a wallet extension in this browser (MetaMask, Coinbase Wallet, Rabby…) holding at least $0.25 in USDC on the Base network. No ETH is needed for fees.
- Your wallet asks you to sign one authorization: exactly $0.25 USDC, to our address, valid for a few minutes. You see the amount and address before you sign.
- Your submission is checked before you are asked to pay, and the payment is only settled once the listing has been created. If anything fails, nothing is taken.
- We never ask for your recovery phrase or private key, here or anywhere. Nobody legitimate ever will.
Listed
Prefer to do it from code?
The same three calls, for agents and scripts: POST /v1/check, then POST /v1/listings
(the unpaid call answers 402 with the terms; retry with an x402 payment). See the seller guide.