Skip to main content
Kilo Code can browse the Nevermined Catalog and pay for services as it works, without you handing over an API key. You add one server, approve a single spending cap, and Kilo Code does the rest. This is the per-host walkthrough; for the concept and the other assistants, see Using the Catalog from your web assistant.

​
Before you connect

1

A Nevermined account

Free, at nevermined.app. You never share an API key with Kilo Code — the consent cap is the credential.
2

A funded wallet

A paid call draws on a spending cap you approve during connect — a commerce grant: a capped, revocable budget funded from your own wallet, not a key. Fund that wallet first with the asset the service settles in — see Fund your wallet. You approve the cap itself in Approve the spending cap.
Start on sandbox, where you use testnet funds and nothing costs real money, before you point Kilo Code at live.

​
Add the Catalog to Kilo Code

1

Add the MCP server

In Kilo Code open Settings → MCP → Add Server, choose Remote (HTTP), and paste the URL for your environment:Leave the headers / client id empty — in the VS Code extension Kilo runs the OAuth (PKCE) flow for you, identifying itself with its own client metadata document, so there is nothing to register. In the Kilo CLI, add it instead to your Kilo config (~/.config/kilo/kilo.json, or ./kilo.json / .kilo/kilo.json for a project) as a type: "remote" entry with the url, then run kilo mcp auth to authenticate.
2

Authorize

Kilo opens a browser to Nevermined’s consent page on your first paid call — see Approve the spending cap. Browsing and free tools need no sign-in.

​
Approve the spending cap

Kilo Code opens Nevermined’s consent page on your first paid call. Discovery and free tools need no credential. It is the one place a human is required.
1

Check who and where

The page shows the Sandbox / Live badge and who is asking. On live, the cap is real money.
2

Set the cap and validity

Set the spending cap (USDC or EURC) and how long the grant is valid for, then Grant access.
That approval is a commerce grant: it spends only from the budget you just approved, only through the Router, and you can revoke it any time. Nevermined’s routing fee comes out of the same cap, and the grant can also read your payment history and wallet balance — the cap bounds what it can spend, not what it can see.

​
Make your first paid call

Ask for something only live data can answer, and name the connector so Kilo Code reaches for it rather than answering from memory.
1

Browse for free

Ask “list the Nevermined catalog categories” — a free tool call, no sign-in.
2

Ask it to buy

“Buy the service with slug <slug> through the Nevermined connector and show me the response.” The paid call draws on the cap you approved and returns the merchant’s response.
If Kilo Code answers without paying, it answered from its own knowledge — name the connector and ask for live data. More on phrasing: Catalog MCP tips.

​
Disconnect

  • Revoke the budget (Nevermined side). Open Connections and disconnect Kilo Code. The credential stops working on its next call; discovery still works.
  • Remove the connector (Kilo Code side). Remove the server from Kilo’s MCP settings (Settings → MCP), or delete its entry from the config file.
To spend again — after you disconnect, or after a cap is used up — re-run the connect step and approve a new cap. A budget is never widened or extended in place.

​
Next

Using the Catalog from your web assistant

The concept and the other assistants.

Catalog MCP — full reference

Every click path, the consent details, and every refusal code.