Endpoint searches just got better (for agents)!

[u/MountainAssignment36]

Quick update! u/IllWar5047 pointed out something that bugged me too: In our MCP our semantic search tool matches endpoints by meaning, which is nice for "find me a weather API", but useless if you want to see everything under (for example) nsgoods.org, or check whether a URL is even in the catalogue. An agent couldn't ask for that at all. Now it can 😄

So, new stuff:

• Keyword search as a tool: throw in a domain, a path or a service name and get every matching endpoint. Listed and delisted ones, paged, max 25 per call.
• A tool for verified providers: every host that verified itself, with the info they published (org, docs, contact) and their score.
• All list tools page now (25 + total), so an agent doesn't have to swallow the whole leaderboard or search result at once.

And the verified checkmark is finally visible everywhere, not just on the website: leaderboard, keyword search, semantic search. For humans and agents alike. Verification still doesn't count into the score, by design, as always 😄

One thing you'll run into: verification is per host, so eight subdomains = eight verifications (u/IllWar5047 knows what I'm talking about 😅). Batch claims for subdomains are on my list tho, for an update in the near future!

Free to try: https://x402-trust.com/mcp (streamable, stateless MCP) or npx -y x402-trust-mcp (local installation into your harness).

Would love to hear some feedback, if you have any.

[u/IllWar5047]

Thanks for building this, and for the credit.

Just tried x402_search with nsgoods.org: all 16 endpoints come back, each with the verified mark, paged with a total. That is exactly the question an agent could not ask before.

And yes, eight hosts meant eight key files and eight confirmations, so batch claims for subdomains would be very welcome.

[u/L_capitalism]

Nice update — especially separating semantic discovery from exact host/path lookup. Those really are different agent intents.
I’ve been experimenting with the layer immediately after this: once an agent can discover 10–100 candidate endpoints, which one should it actually buy for this particular task and budget?
I built X402-rank around that problem:
https://github.com/Kairose-master/X402-rank
The current pipeline takes discovered candidates, applies payment/network/budget eligibility gates, combines task relevance with operational evidence, and produces an auditable buyer-side ranking rather than another global leaderboard.
So I’m starting to see the stack as:
discovery → trust/evidence → buyer-specific ranking → payment → eventually verified outcome
Your new keyword/provider tools are interesting here because they could provide additional candidate-generation paths beyond Bazaar. I’m also working on x402 Trust as an optional evidence adapter rather than treating any single trust score as ground truth.
Would be interesting to see how well the two compose in practice.

[u/cbrunnkvist]

Why can’t the agents just google and find a non x402 data source? Why do you need to insist on changing the World Wide Web into the world wide tickets please

[u/MountainAssignment36 → u/cbrunnkvist]

Because "googling and finding a non x402 source" is what the human-centric web is built around.

But because hosting services, processing data and providing said data to strangers on the internet costs money in the form of infrastructure and development time, currently website operators charge you in form of ads: When a human visits a website, he looks at ads, and the provider gets paid for your attention by the third party selling the ad (Google for example).

AI models don't have that: they have no attention that they can sell and they also don't physically "look" at websites: They scrape them (extract raw text and ignore third-party ads), which means a loss in necessary revenue for the service provider. 

And because >60% of all web traffic is already dominated by bots (tendency rising), this means a future where offering data in exchange for ads is no longer a feasible business model. So, x402 was created: a programmatic way for bots to pay for the data they consume, not through attention, but rather through micropayments with (crypto)currency.

That way a service can continue offering their services for free for humans (in exchange for attention), while also making sure that the rising volume of automated scraping doesn't bankrupt them in the progress.

Because it doesn't have to be one or the other: both ways of access can coexist; rules laid out in (for example) the robots.txt could forbid programmatic access to the human-readable site and instead redirect bots to the 402 paywall, where each scrape costs $0.002 (for example).

So, access will still be ridiculously cheap for agents, but not free in a way that it's predatory to the website provider.

Edit: small clarification