Two products keep getting put in the same sentence: AGIRAILS and Nevermined. Both let agents pay for things without a human clicking confirm, and both can speak x402, which is most of the reason the coverage keeps filing them under one heading.
They are not the same product, and they are not even the same layer.
The agent-payments space is young, the vocabulary is shared, and a lot of coverage blurs the line. But the two are answering different questions. AGIRAILS answers how do two autonomous agents settle a transaction with each other when neither can extend the other credit? Nevermined answers how does a human give an agent a budget to spend, and how do merchants meter, authorize, and settle machine traffic across card and crypto rails?
Answering them took the two teams to opposite architectures: a decentralized protocol on one side, a centralized orchestration layer on the other.
The definition
AGIRAILS runs ACTP (the Agent Commerce Transaction Protocol): an open, decentralized settlement and trust rail for agent-to-agent transactions on Base L2. Two software agents agree on work, funds lock in a non-custodial on-chain escrow before delivery, and the deliverable is attested on-chain. A programmatic dispute window opens at delivery (the requester can settle early, or anyone can auto-settle once it closes), and value settles in USDC under rules no party can override.
Nevermined is a hosted agentic-commerce orchestration platform for delegated agent spending and merchant-side monetization. A human or business can enroll a funding source (their own Visa card, or a crypto wallet) and delegate bounded spending authority to an agent. Merchants, publishers, API providers, and digital services meter machine usage and route payment. Settlement lands as a card payment through an existing processor such as Stripe, as on-chain stablecoin via x402, or through credits, depending on the rail chosen.
They can both speak x402, but for AGIRAILS that is a secondary detail. The substance of AGIRAILS is ACTP: the non-custodial escrow, the on-chain state machine, the dispute layer, and reputation. x402 is only an optional instant path for transactions that need no escrow.
Is AGIRAILS the same as Nevermined?
No. They are different products at different layers.
AGIRAILS ships a protocol, ACTP: a neutral on-chain rail where two agents settle directly with each other, with capital locked in escrow before work and released by smart-contract rules. Nevermined is an orchestration product: a hosted layer that enforces a human-set spending mandate, generates payment credentials, meters usage, and routes the actual money over existing card, stablecoin, or credit rails. One is the settlement primitive. The other is the policy-and-orchestration layer that decides when an agent is allowed to spend, how usage is metered, and which rail settles the payment.
This page compares layers and trust models; the question throughout is which transaction each architecture is built to handle.
What is the difference between AGIRAILS and Nevermined?
The deepest difference is the trust model.
On AGIRAILS, trust is anchored in the contracts. Funds sit in a non-custodial EscrowVault that only the ACTP kernel can move, and only along the kernel's validated 8-state machine. No company holds the capital and no admin function can redirect user escrow; settlement happens because the rules execute.
On Nevermined's card flavor, trust is anchored in the existing card ecosystem: the Visa network generates a one-time credential for each authorized transaction. A PCI-compliant vault (VGS) holds the real card data, so the agent operator never sees it. The human's mandate (budget cap, per-purchase limit, time window, merchant restrictions, instantly revocable) bounds what the agent can do. On Nevermined's crypto flavor, trust shifts to on-chain primitives: ERC-4337 smart accounts with session keys and delegated permissions, plus cryptographically signed usage records.
The second difference is who transacts with whom. AGIRAILS is built for agent-to-agent service settlement: a requester agent and a provider agent, with the contract as the neutral coordinator neither party controls. Nevermined's card flow is built for an agent buying from a merchant on behalf of a human or business. (Nevermined's crypto flavor also supports agent-to-agent settlement, covered below.)
The third difference is escrow, and it is the clearest place where the two approaches diverge. AGIRAILS holds the buyer's capital in escrow before work begins and releases it against verified delivery, so neither agent has to trust the other. Nevermined settles directly rather than escrowing: in the card flavor the money is a card authorization that settles to the merchant through a PSP. In the crypto flavor it is a direct on-chain stablecoin transfer or a prepaid credits redemption. Settling directly keeps the rail fast and light, while escrowing makes higher-trust transactions viable with an unknown counterparty. Two coherent bets, aimed at two different jobs.
The fourth difference is where the core transaction rules live. ACTP is an open, permissionless settlement protocol: the contracts are public, anyone can build on them or audit them, and no company sits in the middle of a transaction. Nevermined is a hosted orchestration layer that uses open standards and open-source SDKs, but the policy, metering, credential, and routing logic still run through Nevermined's service layer. Its card rail runs through the centralized card network; its crypto rail settles on public chains through Nevermined's facilitator.
Side by side
| Criterion | AGIRAILS | Nevermined |
|---|---|---|
| What it is | Open settlement protocol (ACTP) for agent-to-agent transactions | Agentic-commerce orchestration platform for delegated agent spending, metering, and payment routing |
| Primary customer | Developers building agents that pay or get paid for work | Publishers, data and API providers monetizing machine traffic, plus builders giving agents a budget |
| Who funds the transaction | A requester agent locks USDC into escrow | A human or business enrolls a Visa card or crypto wallet |
| Authorization model | Smart-contract state machine; no human point of consent in the loop | Human-set mandate: budget cap, per-purchase limit, time window, merchant rules, instantly revocable; agent spends within it |
| What the platform provides | A neutral on-chain rail, escrow, and settlement; no operator in the middle | Mandate enforcement, real-time metering, payment-credential generation, and multi-rail routing across card and crypto |
| Settlement rail | On-chain USDC on Base L2; cross-chain reach via Circle CCTP, bridge-free | Card flavor: fiat through an existing PSP (Stripe named). Crypto flavor: on-chain stablecoin (USDC) via x402, on Base and other chains |
| Trust anchor | The contracts: non-custodial escrow, publicly auditable on-chain, enforced protocol invariants | Card flavor: Visa network + VGS PCI vault + human mandate. Crypto flavor: ERC-4337 accounts + session keys |
| Fund custody | Non-custodial on-chain escrow; capital locks before work | Settles directly rather than escrowing (card auth or stablecoin transfer/credit); metering and mandate enforcement instead of holding funds |
| Dispute mechanism | Three-tier dispute court built into the protocol: an AI ensemble proposes a verdict, a bonded escalation game lets anyone challenge it, UMA's optimistic oracle is the last resort | Card flavor: the card network's chargeback system, mature but centrally adjudicated. Crypto flavor: settles directly, no dispute stage; built for low-value, low-risk payments |
| Agent-to-agent vs agent-to-merchant | Agent-to-agent service settlement | Card flavor: agent buys from merchant for a human. Crypto flavor: also supports agent-to-agent |
| x402 role | A side path, not the core: the optional instant no-escrow lane (buyer to seller). The primary AGIRAILS path is ACTP escrow | Card flavor: HTTP 402 trigger; money settles as a card auth. Crypto flavor: x402 moves on-chain USDC |
| Architecture (decentralized vs centralized) | Decentralized: an open, permissionless protocol; public on-chain contracts and Apache-2.0 code; no operator in the middle of a transaction | Centralized coordination: a hosted service runs policy, metering, and routing (built on open standards and open-source SDKs); the card rail is the centralized card network, the crypto rail settles on public chains through Nevermined's facilitator |
| Reputation | On-chain reputation increment for the provider on each settlement (ERC-8004 Reputation Registry), because trustless agent-to-agent settlement needs a portable counterparty-trust signal | Uses ERC-8004 for portable agent identity; because trust comes from the human's mandate, a per-settlement reputation score is not central to the model |
| Pricing | Published protocol fee: 1% of transaction value, $0.05 minimum fee. Gas is sponsored, so the agent pays no chain gas | Commercial/platform fees should be confirmed with Nevermined. Underlying card-network, PSP, stablecoin, and credit costs depend on the rail and merchant setup |
What people conflate about AGIRAILS and Nevermined
Three mix-ups come up again and again.
"They both use x402, so they must do the same thing." Both can speak x402, but it sits in a different place in each, and for AGIRAILS it is not the center. The core of AGIRAILS is ACTP: non-custodial escrow, an on-chain state machine, dispute resolution, and reputation. x402 is only the optional fast lane for low-risk transactions that need none of that. It is a thin wrapper over the official x402 packages doing real EIP-3009 / Permit2 settlement, buyer to seller, with no escrow on that path. In Nevermined's card flavor, x402 is the HTTP 402 trigger that starts the flow, but the money settles as a Visa card authorization through a PSP, not on-chain. In Nevermined's crypto flavor, x402 does move on-chain USDC. So "both use x402" is true and tells you almost nothing: for AGIRAILS it is a peripheral convenience, while ACTP escrow is the substance and the differentiator.
"Nevermined settles in fiat, AGIRAILS settles in crypto." Half right. AGIRAILS settles only in on-chain USDC; there is no card rail. But Nevermined is hybrid, not fiat-only. Its original model is crypto-native USDC on Base and other chains via x402, and the Visa card flavor (announced April 2026) is a separate rail layered on the same orchestration. Treating Nevermined as a fiat-only product is inaccurate.
"One has escrow, the other has chargebacks, same protection." The mechanisms differ, and so do the guarantees. AGIRAILS escrow locks the buyer's capital before work and releases it only on verified delivery or after a dispute resolves, enforced by contract, with no central arbiter. Disputes are designed to run through a three-tier court: an AI ensemble proposes a verdict, a bonded escalation game makes wrong challenges expensive and right ones profitable, and UMA's optimistic oracle is the court of last resort. The case law lives on-chain in machine-readable form. Nevermined's card flavor carries over the card network's chargeback rights, a mature dispute process, but one adjudicated by centralized intermediaries: the card network and the banks decide the outcome. Pre-work capital lock and post-hoc chargeback are both real protections. They suit different risk profiles, and neither is a substitute for the other.
Is AGIRAILS a Nevermined alternative for agent-to-agent payments?
AGIRAILS is an alternative to Nevermined for agent-to-agent payments. The difference is the trust model.
ACTP routes agent-to-agent work through a non-custodial escrow with on-chain delivery attestation and a programmatic dispute window. A provider agent can begin work knowing the capital is already locked; a requester agent pays knowing funds release only against verified delivery. Nevermined's agent-to-agent crypto flavor runs through ERC-4337 smart accounts with session keys and policies authorized once, settling stablecoin directly or via prepaid credits, optimized for fast, low-friction payments. If your agent-to-agent transaction is fire-and-forget and low-risk, either approach fits. If it is higher-value or dispute-prone and you want capital locked before work, the escrow approach is what sets AGIRAILS apart.
Do AGIRAILS and Nevermined do the same thing?
No, and you often do not have to choose between them. Nevermined decides whether an agent may spend and routes the payment across whatever rail the merchant accepts; AGIRAILS settles an agreed agent-to-agent transaction in escrow with no company holding the funds. Those are different jobs at different layers, so one stack can use Nevermined to authorize and meter an agent's spend and AGIRAILS to settle the agent-to-agent leg trustlessly. Both can speak x402, so they can interoperate at the payment layer rather than compete for the same slot.
When should I use AGIRAILS instead of Nevermined?
The rule of thumb: Nevermined when a human or business is delegating spend to an agent and needs control, metering, and routing across rails; AGIRAILS when two agents settle work directly and the capital has to be locked before the work starts.
Choose Nevermined if:
- a human or business needs to give an agent a budget to buy digital goods and services from merchants
- you want tight, auditable, human-set control over agent spend: revocable mandates with granular budget, per-purchase, time-window, and merchant-category limits are a genuine advantage when a person wants guardrails around what the agent can do
- you want settlement to land on existing card rails, so merchants get paid through Stripe with no new processor
- you are a publisher, data provider, or API vendor monetizing per-unit machine consumption (per article, per query, per call) and want a hosted, framework-agnostic layer that handles credentials, metering, and policy
- you want card-network controls wrapped around agent spend: one-time credentials, a PCI vault, instant revocation, the card ecosystem's fraud tooling
Choose AGIRAILS if:
- two autonomous agents need to settle a service or outcome directly with each other
- you want capital locked in non-custodial escrow before work, with on-chain delivery proof and a programmatic dispute window
- you need settlement where no company, including the protocol team, can move the funds outside contract rules
- you want portable on-chain reputation tied to agent identity (ERC-8004) that survives any single platform
- you want the transaction rule-set itself to be an open protocol you can inspect end to end and rebuild
Where this connects
The escrow primitive at the center of the AGIRAILS approach: What is agent escrow?.
The category that names AGIRAILS' core property, no party able to move funds outside contract rules: What is non-custodial settlement?.
Why neither AGIRAILS nor Nevermined is a traditional processor, and why the card rails needed something new: Why don't traditional payment processors work for AI agents?.
The architecture AGIRAILS is built to settle, payment tied to a verified outcome: What is Outcome-as-a-Service?.
The same comparison at the standards edge of the category, Google's mandate specification rather than a hosted platform: AGIRAILS vs Google AP2.
The whole series in one place: How does AGIRAILS compare to other agent payment systems?
The settlement primitive itself: agirails.io.
To the best of our knowledge, the first verifiable agent-to-agent escrow settlement on the open rail: BaseScan transaction (February 21, 2026, $3.69 USDC, full lifecycle, gasless, autonomous).
Sources and verification
Last verified: June 20, 2026.
Primary Nevermined sources used for this comparison:
- Nevermined homepage: delegate spending, meter usage, settle autonomously across card, crypto, credits, MCP, x402, and A2A.
- Nevermined product page: open standards and open-source SDKs, framework/PSP agnostic positioning, ERC-8004 identity, ERC-4337 smart accounts, session keys.
- Nevermined Visa/x402/VGS announcement: Visa Intelligent Commerce, x402, VGS, cardholder-defined guardrails, merchant PSP settlement.
- Nevermined x402 Facilitator overview: facilitator responsibilities: verify payment proofs, enforce policy, execute settlement, and return canonical receipts.
AGIRAILS and Nevermined serve different layers. Where they overlap, in agent-to-agent settlement, they offer different trust models: one orchestrates delegated agent spending over card and stablecoin rails, the other settles agent-to-agent work in non-custodial escrow on an open protocol. Pick the one that matches the layer your transaction lives in.