Skip to main content
Search the Catalog for paid services, ranked by ARD hybrid relevance — semantic (meaning) matches merged with lexical (keyword) matches, most relevant first — falling back to pure lexical when the embedding provider is unavailable. Discovery only — free, no credential, nothing charged. To have the platform pick (and optionally pay) the single best service for a need instead of choosing yourself, use route_by_intent. Auth: free · Charges: nothing

Arguments

Only the first page is returned. The pageToken in the result cannot be passed back to this tool. To see other matches, narrow the query or filters, or raise pageSize (up to 100).

Returns

results and an opaque pageToken (informational only). Each result is a concise listing: the fields you pick a service by, flattened to one level (endpoints trimmed to two here). A hit with an nvm:catalog block comes from an older server, which returns the full ARD record instead (and has no detail): its catalog fields sit inside that block, and it has no slug (the slug is the last segment of identifier).
What a listing carries:
  • slug is what get_service, quote_service and pay_service take. Only a hit from this Catalog has one. A rankingSource: "federated" hit comes from another registry: it has no slug, carries its url and source instead, and can’t be quoted or paid here.
  • identifier, displayName, description and tags describe the service; matchReason, rankingSource and one score rank it.
  • protocol, network and the prices: priceLabel (the listing’s advertised price), headlinePriceLabel (derived from endpoint prices; “from” means they vary) and displayPriceLabel (the whole listing: what calls to it settled at when displayPriceSource is settled, the merchant’s latest quote when quoted).
  • Health and payability: routerPayable, healthStatus, uptime30d, successRate, verificationStatus, plus freeAfterPurchasePaths: path prefixes free to poll after your own paid call, within the follow-up window. A call under one that answers 402 is still paid; see get_service.
  • endpoints, each with its method, path, invokePath, priceLabel and description, plus access or auth when set. For an untemplated path, invokePath is the subpath to send, and "" means the service base already is the endpoint. A templated path (a :name, {name} or * segment) carries no invokePath: call get_service and send its payServiceArgs.path with each pathParams segment, whether a placeholder or the example’s value, replaced by your own.
  • An omitted field is unknown or withheld, never defaulted: a missing healthStatus doesn’t mean healthy.
  • Request shapes, examples and quotes are not in a concise listing. Read them with get_service before paying, or pass detail: true.
Reading the ranking:
  • Read the order, not the numbers. Results come back in pick order.
  • rankingSource is per-item: semantic, lexical or federated. matchReason is a closed value explaining the match.
  • The score field is scale-specific (semanticScore, lexicalScore or federatedScore). The scales are not comparable, so don’t re-sort across them.
  • displayPriceSource: "settled" means the displayPriceLabel reflects real multi-payer settlement — the service is genuinely used, not just advertised.
Then read one service in full with get_service.

Try it

Ask your assistant:
Search the Nevermined catalog for weather services.
Call it directly (discovery is free — no credential needed):