I ranked #1 on x402 Bazaar for hash, base64 and uuid: the serviceName change that did it
The x402 Bazaar is not a catalog. It is a search box.
That distinction cost me three high-volume endpoints. On 2026-11-20, our hash, base64 and uuid endpoints were indexed and healthy, but they ranked #7, #6 and #10 for the buyer queries hash, base64 and uuid. Buyers search with the word they need, not with the name we chose for the product. After changing the directory metadata, all three ranked #1.
This post is the exact change, the measurement method, and the caveats.
What the directory actually matches
The facilitator's discovery search returns resources with three searchable fields:
-
serviceName, limited to 32 printable ASCII characters; -
tags, at most five items, each at most 32 characters; -
description, which is searchable but lower weight in practice.
Our old names were accurate category labels:
| Endpoint | Old serviceName
|
Old tags | Rank for the buyer word |
|---|---|---|---|
/hash-402 |
String Hash and Checksum | hash, sha256, md5, crc32, checksum | #7 |
/base64-402 |
Base64 Encoder and Decoder | base64, encode, decode, codec, text | #6 |
/uuid-402 |
UUID Generator | uuid, guid, random, generator, id | #10 |
The names were not wrong. They were just written for a human reading a catalog, not for a buyer typing a query.
The change
We rewrote each identity around the phrases buyers actually type:
| Endpoint | New serviceName
|
New tags | Rank after |
|---|---|---|---|
/hash-402 |
Hash text, checksum | hash text, sha256 hash, get hash, hash generator, sha256 | #1 |
/base64-402 |
Base64 encode or decode | base64 encode, base64 decode, encode base64, decode base64, base64 | #1 |
/uuid-402 |
UUID v4 Generator | uuid v4, uuid generator, generate uuid, unique id, guid | #1 |
The important part is not the exact wording. It is that every tag now contains the query word, and the name contains the phrase a buyer would say out loud. Hash text, checksum beats String Hash and Checksum for hash because the first two words are the query, not a description of the query.
How to measure your own rank
Do not guess from your own 402 body. Query the facilitator's public search endpoint:
curl 'https://facilitator.payai.network/discovery/search?query=hash&limit=100'
Find your resource URL in the returned list and count its position. Repeat for each word a buyer would use. The response is paginated, so use the same limit every time and record the date. A rank without a timestamp is not evidence.
If your resource is missing, the problem is not ranking. It is indexing. Check the settlement receipt and the resource host first. A temporary tunnel host can settle successfully and still be rejected as resource_host_ephemeral.
What did not work
- Changing only the description did not move the rank. The searchable identity is
serviceNameand tags. - Making the name longer did not help. A 100-character name diluted the match; the top results were 80-83 characters and then 32-character names.
- Paying for more listings did not help. The directory is not an ad auction; it is a text match with tiebreaks.
- Re-settling without changing the metadata did not help. It refreshed the timestamp, not the words.
What this does not prove
A #1 rank is not a sale. The directory sorts by match score first, then health, then the number of distinct payers in the last 30 days, then price. A new endpoint with zero payers can be #1 for a query and still lose to a worse match with real payers. Ranking gets you into the shortlist; the product and the price have to close.
The rank can also move. Another seller can publish a better match tomorrow. Treat the measurement as a snapshot, not a permanent position.
Reproducible checklist
- Pick five words a buyer would type, not five words you would use to describe the category.
- Put the exact words in
serviceNameand at least one tag. - Keep
serviceNameunder 32 characters and each tag under 32 characters. - Settle one real request so the facilitator refreshes the entry.
- Query the facilitator with each word and record the rank and timestamp.
- Change one field at a time. If you change the name and tags together, you cannot tell which one moved.
Our current endpoints are at llmrt-companion. The paid review is a 44-probe LLM security scan; the free page lists the probe categories and the delivery shape.
If you run an x402 endpoint, check your rank before you buy more traffic. The search box is cheaper than the ad.
Top comments (0)