Your agent pays anyone who asks.
Every paid endpoint answers 402, but they don't agree on where to put the bill. The Router reads whichever convention the merchant uses, pays it from your delegation, and hands your agent the response. One call. No SDK per protocol, no keys in your agent.
The Agent Catalog is a curated shelf you can buy from this way. The Router is not limited to it.
No merchant allowlist. Loopback, private and link-local hosts are refused, and DNS is pinned.
Two protocols. One integration.
x402 and MPP both answer 402, and put the payment terms in entirely different places. Here is what each actually sends. The Router picks the rail off the header, so your code never branches on it.
HTTP/1.1 402 Payment Requiredpayment-required: eyJ4NDAyVmVyc2lvbiI6Miwi…// v1 puts the same requirements in the body:{ "accepts": [ { "scheme": "exact", "asset": "0x…" } ] }
X-PAYMENT: <signed payload>HTTP/1.1 402 Payment Requiredwww-authenticate: Bearer realm="x",Payment id="…", method="tempo",intent="charge", request="<base64url>"// Payment need not come first; the parser handles it
Authorization: Payment <credential>In an accepts array, or a base64 PAYMENT-REQUIRED header · In an RFC 7235 challenge, alongside any other auth scheme.
Not just the shelf. The market.
There is no merchant allowlist. If a service speaks x402 or MPP on a public host, your agent can pay it, listed or not. The only thing the Router refuses is an address it should never reach: loopback, private and link-local hosts are blocked, and DNS is pinned so a public name cannot resolve inward.
Browse the curated catalog →The cap is the control
Every payment is checked against your delegation before anything moves. You govern one number, not a list of merchants.
One ledger, every rail
exampleProtocols and assets differ per merchant. Your spend does not fragment with them.
| Merchant | Protocol | Asset | Amount |
|---|---|---|---|
| api.merchant-a.dev | x402 | USDC · Base | $0.05 |
| search.vendor-b.io | MPP | USDC.e · Tempo | $0.20 |
| data.vendor-c.eu | MPP | EURC.e · Tempo | $0.14 |
| api.merchant-d.ai | x402 | USDC · Base | $1.00 |
Stablecoin rails
A native Tempo transaction in USDC.e or EURC.e, or an ERC-4337 smart account settling USDC on Base, signed from your own custodial wallet. The Router never holds the float.
Card rail
Paying an external merchant from an enrolled card, with Nevermined minting the credential as token requestor. Built on the rails, not yet open, and separate from accepting cards as a Nevermined merchant, which is live today.
Managed access costs a flat 2% on external services. The merchant receives its full quoted price. Buying from a Nevermined merchant instead carries no buyer fee at all. See pricing.
