Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nevermined.app/llms.txt

Use this file to discover all available pages before exploring further.

Nevermined enables paid access to services and resources — agent APIs, MCP tools/servers, and protected assets — with a consistent flow for pricing, access control, and settlement.

​
The Payment Flow

Nevermined Payment Flow

​
Three Steps to Monetization

1

Register what you’re charging for

Define the thing you want to monetize — an API endpoint, an MCP tool, or a protected asset — plus metadata for discovery.Examples: Agent endpoint, MCP tool method, gated download URL.
2

Create a payment plan

Define pricing and how customers pay:
  • Credits (prepaid) or pay-as-you-go (PAYG)
  • Time-based access, credits-based usage, or trial
  • Fiat (Stripe) or crypto (including stablecoins)
3

Validate, deliver, and settle

At runtime, check entitlement before delivering the service/resource.
  • If entitled: deliver and meter usage (redeem credits or settle per request)
  • If not: return HTTP 402 Payment Required (especially for x402 flows)

​
Two Integration Paths

No-Code: Nevermined App

Configure services/resources and plans via the dashboard.Best for: Quick setup, testing, non-technical workflows

Code: SDKs + REST API

Integrate in TypeScript/Python or call the REST API for full control.Best for: Production systems, automation, custom request flows

​
Who Pays and How

Nevermined supports both sides of the transaction:
  • Builders register agents, set pricing, and receive payouts. They add payment validation to their endpoints and Nevermined handles the rest.
  • Subscribers pay for access. They can purchase a plan via Stripe checkout or stablecoins, or enroll a card via Nevermined Pay for autonomous agent-to-agent payments.
Card delegation via NVM Pay is what makes agent-to-agent fiat payments possible. Instead of a human clicking through checkout each time, the subscriber enrolls a Visa or Stripe card, sets spending limits, and the agent charges it directly within those bounds.

​
Payment Settlement Options

x402 Protocol

HTTP 402 Payment RequiredUse the x402 standard for payment-required requests. The facilitator handles verification and settlement using credits or stablecoins.

Card Delegation (NVM Pay)

Direct card chargingSubscribers enroll a Visa or Stripe card and set spending mandates. Agents charge the card directly via x402 with per-transaction ceilings and usage limits.

​
What Nevermined Handles

ConcernNevermined Handles
Payment processingCrypto (stablecoins), fiat (Stripe), and card delegation (NVM Pay)
Access controlEntitlement validation (plans/tokens/x402)
Usage meteringCredits redemption or per-request settlement
SettlementPayouts to providers

​
Next Steps

Core Concepts

Learn the platform terminology

5-Minute Setup

Integrate quickly

Use cases

Explore the pillar use cases