Nevermined
Card payments for agents — spend mandates, scoped credentials, metering
Nevermined Pay lets an operator enroll a real card once, tokenize it, and delegate a spending mandate to an agent. The agent receives a payment capability (scoped virtual-card credential / API key), not the raw PAN. Mandates can include a budget, time window, optional per-purchase cap, transaction count, and API-key restriction; Nevermined enforces them server-side before settlement. Mid-task purchases use x402-style payment headers so the agent can buy a paid API or tool without a checkout redirect. Integrates with OpenAI, Anthropic, LangChain, CrewAI, MCP, and custom agents. Pair with the Agent Payments & Spend-Policy Control Plane playbook.
Use Cases
- Delegate a capped card mandate so an agent can buy APIs mid-task
- Issue a payment capability instead of handing over the PAN
- x402-style settlement when a tool raises payment-required
- Revoke or expire a mandate without rotating the enrolled card
- Meter agent purchases against a server-enforced spend policy
Key Features
Card enrollment and tokenization
Enroll a credit or debit card once. The PAN is tokenized in a PCI-compliant vault (Stripe, Braintree, or Visa Intelligent Commerce per Nevermined docs). Nevermined states it does not store the raw PAN.
Spend mandates
Budget, duration (hours to custom windows), optional max transactions, optional API-key restriction. Server-side enforcement before money moves.
Scoped payment capability
The agent gets a credential that encodes identity, limits, and restrictions — purchasing power without the card number.
x402 mid-task payments
When a paid endpoint or LangChain tool requires payment, the agent presents an x402 access token and settles inside the mandate.
Metering and traces
LangChain’s Agents That Pay cookbook traces provider payments in LangSmith. Treat metering as vendor-documented, not as invented revenue stats.