Skip to main content
The Nevermined Catalog is a curated directory of external AI services your agents can pay for — browsable by a human at nevermined.app/catalog, and readable by an agent over a public API. Every listed service prices each request on the wire, so your agent can find a capability it needs and pay for it in the same motion, without a signup, an API key, or a subscription at the provider. The Catalog is the front door; the Router is how you walk through it. You discover a service in the Catalog, then pay it through the Router from a budget you control. The two are one product read in one direction: spending at services that were never onboarded to Nevermined.
The Catalog lists services you buy from. If instead you want your own API to get paid by callers, that’s the seller side — see the x402 Facilitator. You can be on both sides at once, and you can even add your own AI service to the Catalog so other buyers discover it.

What’s in it

Every listing is an external service that charges per request, on one of two payment rails the Router can settle: Services that authenticate with a long-lived API key and bill you monthly aren’t in the listed set — there’s no per-call price on the wire for the Router to pay. The Catalog only surfaces what an autonomous agent can actually buy. Listings are organized into a curated set of categories — Data & Enrichment, Search & Research, Crypto & Blockchain, Finance & Markets, AI & Media, Web Scraping & Automation, and more — each with granular sub-categories. See AI Services for the full offering and how to add your own, or Discovering services for browsing and filtering.

How the Catalog and Router fit together

One agent, one budget, one API key — reaching many independent services it never had to sign up for: The services on the right are unrelated to each other and to Nevermined — different providers, different payment rails, no shared account. Your agent treats them uniformly because the Router, not the agent, speaks each rail.

The Catalog: discover

Browse or query the directory to find a service that does what your agent needs, and read its price, protocol, and endpoints.

The Router: pay

Hand the Router the call you want made. It reads the merchant’s payment challenge, pays from your custodial wallet, enforces your budget cap, and relays the answer.
Your agent authenticates with its Nevermined API key and spends against a Delegation — a budget with a hard cap and an expiry. It never holds a private key, never learns a payment protocol, and never needs an account with the service it just paid.

What you need to buy through it

1

A Nevermined API key

Created from the Nevermined app. It authenticates you to Nevermined — never send it to a merchant. It must be a current-generation key; see the Router quickstart.
2

A Delegation

Your budget: a hard cap in cents and an expiry. Created once, reused for every payment until it’s exhausted or expires.
3

A funded wallet

Both rails pull from your own custodial wallet, so it must already hold the payment asset on the network you’re paying on.
Discovery itself needs none of this — the Catalog read API is public and unauthenticated. You only need a key, a Delegation, and funds at the moment you pay.

Three ways to use it

Natural language

Install the AI coding skill and just ask your assistant — “find a weather API and get me tomorrow’s forecast for Berlin.” It discovers, funds, pays, and returns the answer.

MCP

Wire Nevermined into any MCP-capable client so the Catalog and Router become tools your agent can call directly.

Plain HTTP

Everything is public REST. Any agent, in any language, can query the Catalog and route a paid call with curl or fetch.

Environments

Both rails settle real value on public networks. A call made against the live environment moves real funds to a real merchant. Start in sandbox, and keep your first Delegation cap small.

Next

Discovering services

Browse the app, query the read API, and understand what “listed” means.

Router quickstart

From an API key to a paid call, in five steps.

How the Router works

The payment flow, the two call modes, and where custody sits.

Guardrails

What the Router enforces, what it refuses, and every error code it can return.