Skip to main content
The Catalog is discoverable two ways: a human browses it in the app, and an agent reads it over a public, unauthenticated API. Both surface the same curated set of Router-payable services.

​
Browse in the app

Open nevermined.app/catalog to explore listings visually:
  • Categories — filter by top-level category and sub-category (Search & Research, Crypto & Blockchain, AI & Media, and more).
  • Search — free-text over a service’s title and description.
  • Service detail — each listing has a page with its description, protocol, indicative price, callable endpoints, tags, and links to the provider’s homepage and docs.
The app is a browsing surface. To actually buy, an agent drives the Router — the same directory, read programmatically.

​
Query the read API

The Catalog read API is public, unauthenticated, read-only, and cached for five minutes. Send no Authorization header — none is required. Base URL is the environment API host: https://api.sandbox.nevermined.app or https://api.live.nevermined.app.

​
List services

The response is a page of services plus the total matching your filters:
offset is the page size, not a SQL offset. To walk the whole catalog, hold offset fixed and increment page. And the default ordering is intentionally not stable — services rotate within their curation tier — so never assume services[0] is the same service across two calls.
The fields you’ll actually use on each service:

​
List categories

Returns each category with a count of listed services in it. It enumerates what is populated, not the full legal set — prefer it over hard-coding category names.

​
Get one service

Returns the full service by its slug, or 404 BCK.CATALOG.0001 if no listed service matches (the lookup is case-sensitive).

​
The agent-readable feed

A single Agentic Resource Discovery document listing every service with its Router pay-through target and discovery pointers — the machine-readable twin of the browse experience.
The full machine-facing discovery contract — every filter’s validation edge, the discovery pointer shapes, and the catalog error codes — ships in the Router AI coding skill (nevermined-router), so your assistant already knows how to walk the Catalog.

​
What “listed” means

The Catalog only lists services the Router can actually pay — those that price each request on the wire (x402 and MPP). Services that bill out of band aren’t listed, so a browsing agent is never handed one it can’t buy. More on the Catalog’s contents in AI Services.

​
From discovery to a paid call

Once you’ve picked a service, buying it is the Router flow:
1

Read its targetUrl and protocol

Straight off the catalog listing. You don’t need to know x402 from MPP — the Router probes the service and detects the protocol from its 402.
2

Get an API key, a Delegation, and funds

A one-time setup — see the Router quickstart.
3

Route the call

Hand the Router the request. It pays the 402 from your wallet, enforces your cap, and relays the answer.

Router quickstart

From an API key to a paid call against a service you found here, in five steps.

​
Publish your own service

Listing a service you own — and the health validation it passes before it goes live — is covered in AI Services → Add your AI Service.

Related topics

Nevermined CatalogAI Coding SkillAPI VersioningPayments & BalanceA2A Integration