Nevermined: Connecting Agent Service Purchases, Metering and Settlement

Agent payment and service-billing platform · Sources checked October 28, 2026. We did not register or make a real payment.

One agent pays $0.01 per search API call; another service charges by generated token. The developer needs more than a way to receive money: how much should each call deduct, is the buyer authorized, and are failed calls billable? Nevermined addresses a chain of purchase entitlement, usage metering, payment and settlement.

Background: commerce infrastructure for agents

Nevermined was founded by Aitor Argomaniz, Don Gossen, Robin Lehmann and others. It initially explored monetization of data and services and now focuses on payments for AI agent services. See company information. It is primarily payment and metering infrastructure; users may encounter a console, SDK, MCP service, payment plan or mandate. It should not simply be equated with a fully self-custodied consumer wallet.

How might a paid API call work?

Imagine a developer registers a search service and a plan that deducts credits per call. This diagram summarizes public descriptions; it is not a record of a test.

flowchart LR A[Provider registers service and payment plan] --> B[Buyer configures funds and mandate] B --> C[Agent discovers and requests service] C --> D{Check permissions and allowance} D -->|Allowed| E[Execute service and meter usage] E --> F[Deduct usage and settle under plan] D -->|Rejected| G[Stop or request permission]

A provider can design billing around requests, tokens, subscriptions or another unit, linking access, allowance and cost. On the buyer side, a spend mandate can specify amount, purchase count and expiration and can be revoked; Nevermined says the agent cannot raise its own established limit. Test timeouts, repeated requests and settlement in the actual integration. See the homepage and payment and metering explanation.

Question	Direction offered	What cannot be assumed
How much may the agent spend?	Mandates for amount, count, duration and revocation	Every third-party merchant is covered
How does a seller charge?	Plans, credits and usage metering	Every billing model suits every business automatically
How does a developer integrate?	SDK, API, MCP and paths including x402/MPP	Every protocol combination works in the target environment
Where are funds and credentials?	Restricted card credentials and crypto funding paths	Nevermined itself holds or custodies all funds

The provider says VGS holds enrolled card numbers and agents use network tokens; confirm regions, institutional relationships and contracts. Its terms distinguish software from crypto-asset wallets. The homepage describes payment at arbitrary web card merchants as a roadmap item, so it should not be called a universal purchasing card.

Pricing from buyer and seller perspectives

At review, the pricing page listed individual Free at $0, individual AI Services Catalog at $20 per month or a $10 top-up, and organization Starter at $50, Premium at $250 and Enterprise at $500 per month. For supported seller settlement, it listed 1% for stablecoin and 2% for cards, plus payment-processing costs; managed external service purchases carried a 2% buyer access fee. For purchases from Nevermined merchants, the page said there was no extra buyer fee.

For example, a seller receiving $100 by card would have an illustrative $2 platform fee before card-processing costs. That is not a net-income guarantee. The homepage also said merchant directory listing starts at $50 per month; ask how this relates to organization plans. A search snippet showed a different version without Starter, while the directly opened page showed the tiers above. Confirm current terms and whether prices and credits apply to the actual account. See pricing and the homepage.

How is it different?

Skyfire emphasizes KYA identity and service-specific credentials. Nevermined more visibly organizes its offer around authorization, metering and multiple service pricing models. Stripe can offer merchant checkout and payment processing; Nevermined seeks to address AI-service usage rights and autonomous buyer calls. They may be connected in an architecture rather than being mutually exclusive.

Verify whether target APIs are accessible in the directory, per-call costs and external-buyer markups, refund and retry semantics, the institution holding funds and regional availability. A claimed metering model does not establish output quality or make every payment reversible.

How do money and entitlement change in one request?

Suppose a research API seller creates a plan for 100 calls. After the buyer purchases it, the buyer receives usage rights. For each agent request, the service must verify permission and meter usage according to its rules. Official material lists requests, compute, tokens, subscriptions and custom outcomes as possible billing units; these are different products. For call-based billing, whether a duplicate request counts once or twice and how estimates are reconciled must be specified in the integration and contract. See metering information.

The buyer’s spend mandate controls a different question: whether the agent may spend within its amount, count and time limits. The seller’s plan defines how a service is sold; the mandate controls buyer authorization. They can work together, but a buyer cap does not prove seller metering is accurate, API output is good or the data is refundable.

A fee example: who pays what?

Using the listed seller price as an example, $100 settled by card less a 2% platform fee leaves $98 before processing. If processing were hypothetically $3.30, $94.70 would remain. Processing cost is illustrative, not a fixed fee for each card. A managed external-service purchase is a different case: the pricing page lists a 2% buyer markup, unlike a buyer purchase from a Nevermined merchant. Do not assume both 2% fees always apply to the same transaction. See pricing.

Distinguish actual service charges, Catalog subscription or credits, organizational plans and settlement platform fees. A $20 monthly individual Catalog plan does not mean every API has unlimited usage for $20. Check whether service charges are included, credit deductions and remaining-credit validity against current terms.

What evidence is needed after a failure?

A buyer should be able to link mandate, provider, plan or request, actual charge and delivery. Sellers should define whether failed service execution is metered, how duplicate requests are recognized and whether a timed-out response can be queried after payment. These are procurement requirements, not independently verified complete platform capabilities. Card refunds and on-chain stablecoin handling can differ; do not assume identical reversal or dispute mechanisms across paths. The provider describes arbitrary web card payments as still on its roadmap, so verify the target service is actually available. See the product site.

Sources

Product site: mandates, integrations and purchasing scope.
Public pricing: transaction paths and organization plans.
Company information and terms.