AI Services

Every entry in the Catalog is an external AI service that prices each request on the wire, so your agent can pay per call — no signup, no API key at the provider, no subscription. This page covers what’s in the Catalog today and how to get your own service into it.

​

What’s available

Listings span a curated set of categories, each with granular sub-categories: The full set also includes Sales & Business Intelligence, Social & Creator, Identity & Compliance, Infrastructure & Compute, Weather, and Travel. Browse or query the live set — the current categories and their counts come from the public feed, never a hard-coded list. See Discovering AI Services. Each service settles on one of two payment rails the Router can pay:

​

What gets listed

The Catalog only lists services the Router can actually pay — those that price each request on the wire (x402 and MPP). Services that authenticate with a long-lived API key and bill you monthly aren’t listed: there’s no per-call price on the wire for the Router to settle. The Catalog surfaces only what an autonomous agent can buy, so it’s never handed a service it can’t pay for.

​

Add your AI Service

The Catalog is also where you list a service you own so other buyers’ agents discover and pay for it. From a paid organization (Starter or above) in the Nevermined app, publish one of your registered agents into the Catalog with a category, its callable endpoint, and presentation details (title, description, logo, tags, features). For the step-by-step — the two ways to submit and what each one needs — see Publish to the Catalog. You supply only presentation and the endpoint. Trust-sensitive facts are derived server-side rather than accepted from you — the payment protocol and price are detected from your endpoint, and ownership is taken from the agent — so a listing can’t misrepresent what it charges or who runs it.

​

Listed only once it’s validated healthy

Before your service goes live, a monitor probes the endpoint to confirm it actually responds — a listing is never published on your word alone. It also keeps checking after launch, so the Catalog stays a directory of services that currently work, not ones that used to. Each listing moves through a simple lifecycle:

​

Health is also judged on paid calls

The monitor’s probe does not pay, so it proves your endpoint answers, not that a paid call delivers. The Catalog also reads the outcome of real purchases made through the Router:

• Hidden while payments don’t go through. If none of a listing’s paid calls over the last 7 days settled and at least 3 of them went undelivered, from at least 2 different buyers, it is hidden from discovery. An undelivered call is one that failed, or one where your endpoint collected the payment and then answered with an error. One settled call brings the listing back. Without one, it is shown again 3 days after it was hidden — but while the undelivered calls that hid it are still inside the 7-day window, the next hourly check hides it again.
• No uptime claim without a settled call. If a listing has at least 3 paid calls from at least 2 buyers in the last 30 days and none of them settled, it stays listed but publishes no “operational” status, uptime or last-healthy time until a call settles — and a status=operational filter no longer matches it. You still see the monitor’s own readings on your listing. Card payments made over MPP (Stripe) are not counted here, because that rail never records a settlement.

​

Next