FinWikiPublic-source finance field guide
日EN

Nevermined · AI compute-payment protocol

ConfidenceLikelyUpdated2026-07-29Review by2026-10-27Sources5Machine-translatedOriginal (JA)

On this page

Wiki route

This entry sits under AI Agent payment protocols seven-protocol overview. Read it against x402 · HTTP-native micropayment for peer / contrast, skill market monetization for the marketplace framing, and payments index for the broader rail context.

Key facts

  • Nevermined is an AI compute / data marketplace + payment protocol — per-inference, per-dataset, per-agent-call micropayments
  • Architecture: smart-contract escrow + token-gated access; agents subscribe or pay-per-use for compute / model / data
  • Built originally on Polygon / EVM; integrates with x402 as one settlement option
  • Use case: AI compute provider exposes a model / GPU endpoint; agent consumer pays per inference call, settled in stablecoin
  • Targets the “compute-as-commodity” thesis where agents shop across many providers per workflow

Mechanism — how Nevermined routes compute payments

The protocol fits between compute / model providers and agent consumers:

AI agent ──── intent: "run inference on model X" ─────►
                                                      ▼
                                              Nevermined
                                              gateway / SC
                                                      │
                              ┌───────────────────────┼──────────────────┐
                              ▼                       ▼                  ▼
                     Compute provider A       Model provider B    Dataset provider C
                              │                       │                  │
                              └───── settlement ──────┴──── stablecoin ──┘
                                       (USDC, USDT, native token)

Core building blocks:

  1. Asset registration — provider registers a model / dataset / API endpoint with price, terms of use, and access policy
  2. Subscription / pay-per-use token — consumer agent buys a subscription NFT or per-call credit
  3. Smart-contract escrow — payments held until proof-of-delivery; provider claims on completion
  4. Access proof — gateway validates token before forwarding request to the compute provider
  5. Royalty / split logic — multi-party splits to model creators, data curators, compute providers

Compute-marketplace fit

The agent-economy thesis behind Nevermined: an agent workflow may touch dozens of compute providers in one task (e.g., a research agent that hits a vision model, a structured-extraction LLM, a vector DB, a domain-specific finetune, and a long-context model — each from a different vendor). Traditional SaaS API-key flow breaks at that fan-out; Nevermined’s per-call settlement + unified billing makes it linear.

Compare with the x402 architecture: x402 standardizes the HTTP handshake, Nevermined standardizes the marketplace + escrow contracts. The two can compose — Nevermined uses x402 for the transport-layer payment-required handshake while running its own escrow / royalty layer on top.

Integration with x402

Layer x402 public specification Nevermined public product / protocol docs
HTTP negotiation Defines 402 plus V2 PAYMENT-REQUIRED, PAYMENT-SIGNATURE and PAYMENT-RESPONSE payloads May use x402 as an interaction / payment transport where the selected Nevermined integration documents it
Payment abstraction Server advertises accepted schemes, networks, assets and destinations; settlement is scheme-specific Provider defines payment plans / credits and the deployment’s settlement configuration
Service discovery Discovery is outside the minimal payment handshake and can be supplied by ecosystem registries / applications Nevermined publishes marketplace / registry concepts for AI services, models or data
Access model Core flow gates an HTTP resource after payment verification; extensions / schemes may add other behavior Plans and credits can represent metered or recurring access according to current Nevermined docs
Revenue / split logic Core x402 does not define a universal marketplace royalty split Any split, escrow or provider payout claim must be tied to the exact Nevermined contract / plan version
Operator responsibility Client protects signing keys; server / facilitator validates and settles the selected scheme Provider and buyer must verify plan terms, service delivery, contract addresses, refund / dispute and key custody

Sources: ^[https://docs.x402.org/core-concepts/http-402] ^[https://docs.x402.org/core-concepts/network-and-token-support] ^[https://docs.nevermined.io/] ^[https://github.com/nevermined-io]

Practical pattern: a compute provider publishes via Nevermined for catalog + escrow, exposes the call endpoint with an x402 facilitator for transport-layer payment, and lets agents settle in USDC on Base / Arbitrum.

Where Nevermined sits

Function Open-stack peer Nevermined position
Discovery x402 Bazaar Nevermined registry
Settlement x402 + USDC Same rails, plus subscription
Identity Privy / Coinbase CDP / ERC-7715 Reuses external wallet identity
Royalty splits Stripe Connect, ERC-2981 Built-in via smart-contract escrow
Compliance / KYA Skyfire (see entry) Pluggable

Sources

  • nevermined.io product site and developer documentation.
  • github.com/nevermined-io for protocol contracts and gateway code.
  • Nevermined registry app and provider listings.
#agent-economy#payment#nevermined#compute-marketplace#per-inference#micropayment

Discovery

Keep reading

Related

Read next

Links here