Three ways to get paid

Catalog
Nevermined discovers and lists your AI service. Agents find it and pay per call in stablecoin. Nothing to enroll.
Embedded Web Flow
Charge your own end users any cart total by card, through a checkout embedded on your site. No plan, no buyer account.
Merchant Plans
Sell credits, time, or pay-as-you-go access to your AI service. Agents buy the plan and call your endpoints with an access token.
Not sure which one? If the buyer is an agent and you want zero setup, use the Catalog. If the buyer is an agent and you want to set the price and the access model yourself, use Merchant Plans. If the buyer is a person on your website, use the Embedded Web Flow.
Catalog
The Catalog is the zero-setup option. Nevermined auto-discovers services that already price each request on the wire (x402 or mpp) and lists them at nevermined.app/catalog. Buyers are agents with a Nevermined account. They pay each call in stablecoin from their NVM wallet through the Nevermined Router, at whatever price your service quotes on that request. You don’t register a plan, and the buyer doesn’t hold one — they hold a funded wallet. Read the Catalog overview for the buyer’s view, or add your AI service so buyers can find it.Embedded Web Flow
The Embedded Web Flow is for selling goods and services to your own end users. You control an organization, you set the price per checkout (any cart total, as a one-off Order), and your buyer pays by card through an embedded PSP checkout on your site. The buyer needs no Nevermined account, no plan, and no delegation, and you never touch card data. This is the newest of the three. The Orders guide documents the contract and tracks its availability insandbox and live.
Merchant Plans
Merchant Plans are the traditional Nevermined flow: you sell access to your AI service through a plan (credits, time, or pay-as-you-go) at a fixed price you set. Other agents order your plan, obtain access tokens, and call your endpoints programmatically, settling in stablecoin or fiat. Both sides integrate Nevermined, which makes this the most flexible of the three — and the one with the most setup.How It Works
- Register your Agent & Plan: Create a payment plan in the Nevermined App and link it to your AI agent (endpoints, metadata, pricing).
- Receive Subscriber Requests: Configure your agent to validate requests from subscribers via Nevermined Payment Libraries (Python/TypeScript). No additional servers or custom gateways needed.
- Agents Pay, Then Use: Other agents order your plan, obtain access tokens, and call your agent’s endpoints with bearer authentication.
- Secure Settlement: Payments are processed via stablecoins or fiat (Stripe), with pricing models supporting subscriptions and per-query credits.
Payment Methods
Merchant Plans support two payment methods:Fiat Payments
Accept credit cards via Stripe. Users can purchase plans directly, or delegate their card for autonomous agent-to-agent payments.
Stablecoin Payments
Accept USDC or other ERC-20 tokens on-chain. The native method for agent-to-agent commerce with the lowest fees (1%).
Benefits
- Simple setup: Create a plan, link your agent—done.
- Programmable access: Agents can buy and use services autonomously.
- Flexible pricing: Subscriptions, credits, and metered usage.
- Trusted payments: Stablecoin and fiat support with transparent settlement.
Implementation Steps
- Create a Payment Plan in the Nevermined App (price, duration, credits).
- Register your Agent: Provide endpoint URLs and capabilities.
- Link Plan → Agent: Ensure the plan grants access to your agent.
- Validate Requests in your agent using the Payment Libraries to check
payment-signaturetokens and credit balances. - Publish your agent so other agents can discover and subscribe.
Learn More
- Register Agents in the Nevermined App
- Manage Plans for pricing and access
- 5-Minute Setup to get your first paid request working
- Catalog Overview for how agents discover and pay listed services
- Orders: Goods & Services Checkout for the Embedded Web Flow contract
- Payments for card enrollment and delegations behind card-paid flows
- Blog: Making x402 Programmable
- Blog: Agentic Payments with x402, A2A & AP2