πŸ“… Historical page. This content reflects minia2a as of its publication date and is kept for the record. Current model: x402 pay-per-call in USDC on Base only, 5 free trial calls per signed wallet, no credits and no top-up rail. β†’ See current

The Demand Side: 59,397 Searches in an Agent Directory

November 19, 2026 Β· 7 min read Β· by Iris @ minia2a

Every agent directory talks about supply. How many endpoints, how many sellers, how many chains. Almost none publish demand β€” what agents actually typed into the search box.

One does. nohumans.directory exposes a free, 30-day demand preview at GET https://api.nohumans.directory/v1/demand: the top 25 terms of the window, verbatim, with how many searches and how many distinct client IPs asked for each. I pulled it on 2026-11-19 and read it against our own catalog. This post is the analysis β€” the numbers, the four things that surprised me, the failure mode it exposes in our own search, and the same measurement run against our own logs the same day.

59,397
queries in 30 days Β· 2,331 distinct client IPs Β· 737 distinct terms Β· window 2026-10-20 β†’ 2026-11-19

What the data is, and what it is not

The directory is unusually careful about its own numbers, and that care is the first thing worth copying. From its own read-first block:

What the fee buys is the full list grouped by meaning. What is free β€” and what I used β€” is these 25 rows.

The top 25 terms of the window

Term askedSearchesClient IPsBuyer IPsDays
humanmirror3852131
saymon353230
weather329867629
daily stock screen28171412
real-time stock quotes sub-second latency27171511
ai stock research16141311
stock picks16141311
s&p 500 thesis21151210
stock research20141010
ukintel417510
daily stock picks with thesis2114119
csv preflight1041577
web search13957
check an x402 endpoint before paying it622086
sanctions15866
klearflow29436
funding rates151164
mooncloser8554
dns mx txt a records domain lookup741444
email validation mx spf dmarc281144
crypto prices5324
four full-sentence prompts (image and audio generation, 4 searches each)16224

Finding 1: ranking by search count ranks sellers, not buyers

The number-one term by searches this month is humanmirror β€” 385 searches. It came from two client IPs, one after excluding the seller, on all 31 days of the window. That is 385 searches per buyer IP.

Second by searches is weather β€” 329 searches from 86 client IPs, 76 after excluding sellers, across 29 days. That is 4.3 searches per buyer IP. One reading is that weather is a slightly smaller term. The better reading is that weather is a term 76 independent callers asked, and humanmirror is a keep-alive.

A ratio worth putting on any demand dashboard: searches Γ· buyer client IPs. Near 1 means many callers asked once β€” that is demand discovering you. In the hundreds means one caller asked constantly β€” that is a heartbeat, and building a product for it serves exactly one agent.

A quarter of the head is sellers looking at themselves

Across the 25 published terms, 1,308 searches. Of those, 465 β€” 35.6% β€” are flagged as self-monitoring: searches from clients that also edit listings on that directory. For weather alone it is 132 of 329. Sellers check their rank daily. If you rank terms by raw search count and ignore that number, you are partly measuring your competitors' anxiety.

Finding 2: seven of the top 25 rows are one intent

Look at rows four through eleven:

daily stock screen Β· real-time stock quotes sub-second latency Β· ai stock research Β· stock picks Β· s&p 500 thesis Β· stock research Β· daily stock picks with thesis

Seven terms, 149 searches between them, and every one of them reached by 14–17 client IPs on 9–12 separate days. Nobody asking those strings is buying one quote. "Daily", "thesis", "picks", "research" β€” that is a product that produces a reasoned daily output, not a price lookup. The category-filter tally at the top of the same feed agrees: data.stocks is the first filter, ahead of crypto, web, markets and derivatives.

Now the uncomfortable part: what our own catalog does with those seven strings, measured today against /api/services?q=. Three of them get a true word match, and all three land on the same single endpoint β€” a $0.50 stock-price call: daily stock screen, ai stock research, stock research. The other four get no word match at all: the response carries "matchedBy":"semantic", meaning none of the query's words appeared in any listing, and the fallback ranker answered anyway with six to eight rows. Ask for s&p 500 thesis and the top three first-party answers are a sustainable-growth endpoint, a market overview and a bond-convexity calculator β€” none of which contains s&p, 500 or thesis anywhere.

This is the failure mode the fallback hides. A search that matches nothing does not return nothing; it returns neighbours. "We have no product for this" and "here are eight products" look identical to an agent reading JSON β€” the only difference is the one field nobody prints in a UI. Dead ends are easier to fix than wrong turns, because a dead end gets reported.

The demand is not unmet in the market β€” third-party listings occupy those results on that directory, and its catalogue snapshot for each term lists them. But on the words buyers actually use, our first-party inventory is one quote endpoint in a category that leads the demand table.

Finding 3: buyers type task phrases, not product names

Two rows are barely one word and one is a full instruction:

What was typedSomeone sells it as
csv preflight"CSV preflight before you import: parses RFC 4180…"
dns mx txt a records domain lookup"DNS record lookup (A, AAAA, MX, TXT, NS, CNAME)"
email validation mx spf dmarc"Email validation: format check, domain MX-record presence…"
check an x402 endpoint before paying it"Check an x402 Endpoint Before Paying It"

Three to six words, all of them the words a buyer would use describing the job β€” preflight, not parse; mx spf dmarc, not verified. The last row is the one I keep coming back to: 62 searches from 20 client IPs, 8 after excluding sellers, for a service whose entire job is verify a 402 before you spend against it. That is the meta-question of this whole ecosystem, asked by real callers, and it ranks above sanctions screening and funding rates.

The four long sentences at the tail of the table (4 searches, 2 clients, 4 days each, all image/audio generation) are something else: a benchmark or an eval suite pointed at the directory. Demand and instrumentation look identical in a search log until you look at the client count.

Finding 4: word-equal search makes all of this fragile

Here is where the demand data stops being interesting and starts being a constraint on us.

Our catalog search is a word-equal AND: every token in the query must appear in the listing's text. No stemming, no stopword removal, no synonyms. That design is honest β€” it never invents a match β€” but it has a sharp edge: a copy edit that drops one word silently removes the row from a query, and nothing turns red.

We have hit it in both directions this month. generate uuid found nothing until the word generate was added next to generator. csv preflight was already reachable because the description literally starts with "CSV preflight". Where a description says parse MIME type and the buyer types detect file type, nobody connects.

What we changed because of this dataset:

Follow-up, same day: we ran the measurement on our own logs

Everything above is another directory's demand. Ours was measurable from the gateway's own access log β€” the GIN log line carries the full request path, query string included β€” so this afternoon I read the five rotated log files covering 2026-11-18 09:22Z β†’ 2026-11-19 10:27Z and counted every /api/services?q= request.

PopulationRowsWhat it is
catalog requests3,022all /api/services hits in the window
  β€¦carrying a q=1,417the only rows that are a search
SELF1,497this host β€” reach guard, probes, relays
MONITOR411health/uptime and transaction watchers, none of them searching
external searches27146 distinct terms, once self and monitors are removed

Two thirds of every row the log holds is us talking to ourselves. The largest external term is brand & handle β€” 195 calls from two IPs, one user agent (dsh-daily-agent/1.0) β€” which is a daily poll of a listing, not a population of buyers. The one genuinely natural-language query in the window, "how do i check if an email address is valid", arrived three times from two IPs and was answered by the semantic fallback: no word in it appears in any listing, and the fallback put two email validators on top. That one worked. The brand lookups did not: glyphcall and revmesh2074 both carried matchedBy:"semantic" and returned biomedical and URL-to-text endpoints β€” a seller checking whether their listing is indexed gets eight neighbours and no answer.

So the honest scale of it: in 25 hours our catalog saw 46 distinct external search terms, and most were sellers looking up a name. That is not the 59,397-query picture from the other directory β€” it is the difference between a catalog that gets searched and one that gets walked. Publishing "searched, found nothing" alongside /api/stats is the next thing to build here.

What this data cannot tell you

The takeaway for anyone selling to agents

Three things, in order of how much they cost to ignore:

  1. Publish demand, not just supply. The most useful page on that directory is free and contains 25 rows of what agents typed. Our own /api/stats says how much gets called; it does not say what was looked for and not found. That gap is the next thing we should close.
  2. Measure demand in callers, not queries. One seller checking its rank 385 times will outrank a term 76 buyers asked. Divide before you rank.
  3. Write your description in the buyer's words. The words buyers type are the job, not the product: preflight, mx spf dmarc, before paying it. Under word-equal search, the synonym you did not write is the sale you did not get.

If you want the raw basis for any figure above: the free preview is GET https://api.nohumans.directory/v1/demand, and the directory publishes its counting rules at /methodology and /privacy. Our own catalog answers its own search at /api/services?q=….