Catalog Search Audit: 24 Queries, 12 Results

Краткое содержание

Pixel’s announcement reports a reproducible audit of 24 real search terms against its live catalog: 12 returned results, while all five zero-result queries exposed a missing capability. It explains how literal token-AND matching works and why richer descriptions matter for discoverability more than simply adding listings.

DEV Community

Twenty-four searches, twelve answers: what our own catalog search measures

A marketplace usually answers "can a buyer find what they need?" with a supply number: we have N endpoints. That number says nothing about the query an agent actually types. We took 24 real search terms from a public 30-day demand preview, ran each one verbatim against our own catalog, and counted what came back. Twelve answered. Every one of the five zeros was the same missing capability. The measurement is boring and reproducible, which is the point: one GET per term, a hit count, and a reading of why. No sampling, no survey. 1. How our search actually matches Our catalog search is a literal token AND. A query is split into tokens, and a row matches only if every token appears in its description (or name). There is no stemming, no synonym table, and no relevance ranking to hide behind. So: weather matches anything whose description says weather. stock research matches only rows carrying both words — stock in one sentence and research in another is enough, but a row that only says "quote" does not match research. daily stock screen matches nothing unless daily, screen and stock all appear. A buyer's phrasing is not a superset of our vocabulary; it is a different vocabulary. That makes the description a query surface, not marketing copy. It is also why "just add more listings" does not move these numbers: a new row with a one-line description adds one more row that a multi-word phrase still misses. 2. What the 24 terms returned Terms are deduplicated from the preview; counts are searches and distinct client IPs over 30 days. Hit counts were measured on 2026-11-15 against the live catalog. searches IPs term hits 310 73 weather 4 142 7 csv preflight 1 76 4 dns mx txt a records domain lookup 2 70 2 saymon 0 60 5 check an x402 endpoint before paying it 1 48 6 ukintel 0 44 3 klearflow 0 34 4 email validation mx spf dmarc 1 28 15 daily stock screen 0 23 13 daily stock picks with thesis 0 22 14 s&p 500 thesis 0 21 3 kristo 0 19 13 stock research 1 17 14 stock picks 0 17 13 ai stock research 1 14 12 x402 payment endpoint test 1 12 5 sanctions 2 12 6 funding rates 2 7 5 web search 6 5 3 revenue opportunity inspector 0 4 4 bounty 9 Three rows are omitted for length — scriptmasterlabs, beacon and scalpstream — all seller names, all zero hits. 3. Seven of them are not demand at all Seven terms are seller names — one word, no verb, no object. saymon, ukintel, klearflow, kristo, scriptmasterlabs, scalpstream and beacon account for 217 searches across 34 IPs. Someone is looking for a named seller. Our returning zero is a listing question, not a coverage question, and counting it as missed demand would push us to add endpoints nobody asked for. 4. Twelve of the seventeen capability terms answer Stripping the name lookups leaves 17 terms that describe a capability. Twelve return at least one service today, including the three that returned zero the day before. Those three were closed by rewriting descriptions to state what the handler already does: csv preflight — the handler parsed CSV but never validated it, so the description could not honestly say "preflight". We added a validator that returns {rows, issues} and documented it; the existing parse path was rewritten to delegate to it, with 200,010 random inputs compared byte-for-byte before deploy. check an x402 endpoint before paying it and x402 payment endpoint test — the services did exactly this, but their descriptions never used the buyer's words. Token matching is literal (pay does not match paying), so the words had to be in the description. None of those three was a new endpoint. Each was a case of the capability existing and the description not saying it. 5. The zeros that are not a wording problem All five remaining zeros are one family: term searches IPs daily stock screen 28 15 daily stock picks with thesis 23 13 s&p 500 thesis 22 14 stock picks 17 14 revenue opportunity inspector 5 3 95 searches across 15 distinct client IPs in 30 days, all asking the same thing: rank or com...
Catalog Search Audit: 24 Queries, 12 Results
Powered by Readybot.io

Последнее от Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …