What is the difference between AGIRAILS ACTP and Virtuals ACP?

Every other page in this series compares AGIRAILS with something adjacent: a checkout standard, an identity platform, an instant-payment rail. Virtuals ACP is the exception. It escrows USDC between agents on Base, four phases from request to evaluation, reputation flowing into ERC-8004, the agent reputation registry standard. On paper, that is our job description.

So the details have to be exact. Virtuals got to production early, published an Agent Commerce Protocol whitepaper in early 2025, and took the model to standards territory this year as ERC-8183, drafted with an Ethereum Foundation researcher. Two teams reached the same conclusions about agent commerce, down to the settlement currency. Where they parted is the question this page answers: what happens between funding and payout, and who gets a say.

Virtuals ACP answers it with a judge the client picks, or no judge at all. ACTP, the Agent Commerce Transaction Protocol, answers it with an open objection: courts exist, but only the parties can summon one.

The definition

Virtuals ACP (Agent Commerce Protocol) is the commerce layer of Virtuals Protocol, the AI-agent platform on Base. A client agent funds a job in USDC into the protocol's escrow contract, and a provider agent submits the work. The client-designated evaluator then completes or rejects the job; the contract pays 95/5 provider/protocol, with a further 5% to the evaluator when a third party fills that role. Four phases (Request, Negotiation, Transaction, Evaluation), a signed Proof of Agreement at negotiation, ERC-8004 hooks for reputation. Version 2.0 arrived in April 2026 as the reference implementation of ERC-8183, a draft Ethereum standard for agent commerce. Jobs settled in $VIRTUAL until August 2025 and in USDC since. Agents join through the Virtuals platform and its Agent Registry, and the Butler agent fronts the network inside Coinbase's Base App.

AGIRAILS maintains ACTP, which escrows the same kind of transaction with the opposite judicial posture. The buyer's USDC is committed on-chain, the provider anchors its deliverable with a hash, and a challenge clock starts; if it runs out with no objection, the payout executes with no one's approval. A verdict exists only when a party stakes a bond to contest the job. The contest is designed to escalate past AI arbiters to UMA, the optimistic-oracle dispute protocol, which neither agent appointed. The fee is 1%, never under five cents, the protocol covers gas through an ERC-4337 paymaster, and reputation lands on ERC-8004.

Is AGIRAILS the same as Virtuals ACP?

No, though these are the only two protocols in the category built on the same primitive. Both hold a buyer agent's USDC in escrow on Base while a provider agent works. The differences start one sentence later: who judges delivery, whether the network is open or joined, who can change the contract's code, and what the protocol is for. Virtuals ACP is the commerce layer of one agent ecosystem, wired into its launchpad, its registry, and its distribution. ACTP is a standalone settlement rail with no ecosystem membership attached.

And no, neither of them is the OpenAI/Stripe checkout standard that shares the acronym; that untangling has its own page.

What is the difference between AGIRAILS ACTP and Virtuals ACP?

The difference is each protocol's default posture toward judgment.

On Virtuals ACP, the judge is chosen up front or not at all. A client that names an evaluator gets a quality gate on the job: the evaluator reviews the submission, its decision routes the money, and it earns 5% of the job for the service. There is no appeal and no arbitration layer behind that decision; the v2 docs describe none. A client that names no evaluator gets speed instead: per the deployed contract, the job completes on its own once work is submitted. Either way, the question of judgment closes at job creation. The design reads like a marketplace: the buyer decides in advance how much scrutiny a purchase deserves.

ACTP never closes that question until settlement. No one reviews an uncontested job, which keeps honest transactions at the protocol's 1% with nothing added, and the provider's delivery hash plus an expiring window do the settling. What every job keeps, from commitment to payout, is the standing right to object. A bonded challenge is designed to bring AI arbiters in for a first pass. That ruling binds no one, because either side can escalate to UMA's oracle, external to both agents and to AGIRAILS. The bond economics make a wrong first ruling expensive to defend. One protocol builds the courtroom into the checkout; the other keeps a courthouse down the street.

Past judgment, the next divide is what the contract answers to. Virtuals ACP concentrates all jobs in one escrow contract deployed behind an upgradeable proxy, with Virtuals holding the upgrade keys; the contracts are MIT-licensed and public, and no on-chain governance over those upgrades is documented. ACTP's EscrowVault gives its operator no handle on money in flight: what the contract says at commitment is what executes at settlement, and there is no upgrade path over user escrow.

The final divide is the front door. Joining Virtuals ACP has meant joining Virtuals: registration through its platform, wallet onboarding, sandbox graduation in v1, OAuth against the platform and a centrally run Agent Registry in v2. That buys real things: a curated network, the Butler storefront in Base App, a revenue program for service agents. ACTP has no membership: any agent with a wallet talks straight to the contracts, and registering is a wallet transaction that writes an ERC-8004 record, not an application.

On settlement currency, the changelog is the receipt: Virtuals ACP launched in its ecosystem token and switched to USDC on August 12, 2025.

Side by side

What people conflate about AGIRAILS and Virtuals ACP

"ACP is ACP." The category holds two unrelated protocols named ACP and one named ACTP, and the fastest sort is to count the machines holding money. Virtuals ACP (Agent Commerce Protocol) and AGIRAILS ACTP (Agent Commerce Transaction Protocol) each have two: a client agent and a provider agent, with escrow between them. The OpenAI/Stripe ACP (Agentic Commerce Protocol) has none: the agent fronts a human's card at a merchant, and the money rides retail rails. Two-agent escrow means this page; a shopper and a store means the other one.

"An evaluator is a dispute system." An evaluator rules on the work. A dispute system exists for when the two sides disagree about the ruling itself, and that is the layer Virtuals ACP does not carry. The evaluator's call is final, and the party it goes against has nowhere to take the disagreement. ACTP's bonded path and oracle backstop exist for that second-order case. Client-chosen review and neutral recourse can look alike on a diagram; they diverge the first time a ruling is wrong and one side wants it reviewed.

"Same escrow, so the trust is the same." An escrow contract's guarantees depend on who can change its code. Virtuals ACP's escrow lives behind an upgradeable proxy whose keys the operator holds, a normal engineering choice for a fast-moving platform, and a real trust assumption for the agents whose funds sit inside. ACTP is built on the absence of that assumption: there are no keys that could make the rules otherwise.

Can AGIRAILS and Virtuals ACP work together?

At the standards layer, they already overlap: both write agent reputation to ERC-8004, so a provider's record from one rail is legible to the other. ERC-8183 vs ERC-8004 is not a contest, either: 8183 standardizes the job-escrow-evaluator flow that Virtuals ACP implements, and 8004 standardizes agent identity and reputation. An agent could earn its reputation on either rail and spend the credibility on both.

At the transaction layer they are parallel roads, and the choice between them is the choice of the ecosystems around them. An agent living on the Virtuals launchpad, with a token, Butler distribution, and the revenue program, transacts where its network is. An agent that wants settlement without a platform attached takes the standalone rail. ACTP is infrastructure, not a marketplace: it brings the escrow, and you bring both sides of the trade.

Is AGIRAILS a Virtuals ACP alternative for agent-to-agent payments?

Yes, and the comparison runs both directions: Virtuals ACP vs AGIRAILS ACTP is the only pairing in the category where both candidates escrow the same dollar on the same chain. What decides it is everything around the escrow. Virtuals ACP comes with membership in the Virtuals economy, an evaluator gate the client sets per job, and the distribution that a platform brings. ACTP comes with permissionless entry, review only on challenge, a fifth of the fee, and escrow rules fixed from commitment to settlement.

When should I use AGIRAILS instead of Virtuals ACP?

Decide where the trust should sit: with a reviewer the client names, or with rules that hold still.

Use Virtuals ACP if:

• your agent lives in the Virtuals ecosystem and its counterparties are there too
• you want a designated reviewer on every deliverable, so acceptance is never your agent's problem
• the Butler storefront and Base App distribution matter to your agent's business
• the revenue program for service agents changes your unit economics
• you want the path that tracks ERC-8183 as the standard matures

Use AGIRAILS if:

• your agents transact across ecosystems, and joining a platform is a cost, not a feature
• honest jobs should settle at 1%, with no review fee on work neither side disputes
• the losing side of a ruling needs somewhere to go: bonded appeal, then an oracle no one appointed
• the rules holding escrowed funds must stay fixed for the life of the job
• you also need the instant lane, since the same SDK carries x402 for the requests escrow would only slow down

Where this connects

The primitive both protocols reached for: What is agent escrow?

What it means for escrow rules to be beyond the operator's reach: What is non-custodial settlement?

The other ACP, the retail one: AGIRAILS ACTP vs Stripe ACP

Every comparison in this series, mapped: AGIRAILS comparisons

ACTP itself, live on Base: agirails.io

Sources and verification

Last verified: July 2, 2026.

Primary Virtuals sources used for this comparison:

• The Virtuals whitepaper, commerce layer: the four-phase model, roles, and Proof of Agreement.
• The ACP whitepaper PDF (2025): the framework as first published.
• ACP changelogs: go-live July 3, 2025; the VIRTUAL-to-USDC switch on August 12, 2025; ACP v2.0 in April 2026.
• ACP v2 documentation: job lifecycle, evaluator designation, fee split, ERC-8183 positioning, and the absence of any arbitration or appeal path in the v2 docs.
• The ACP contracts repo (MIT) and the escrow proxy on Base: the upgradeable-proxy custody model.
• ERC-8183 on Ethereum Magicians (draft, 2026): job-based escrow with a single evaluator, ERC-8004 hooks.

Virtuals ACP and ACTP prove the same thesis twice: agents transacting with agents need escrow, a chain, and dollars. The remaining disagreement is old legal philosophy in new clothes, an appointed inspector or a standing right to object. AGIRAILS chose the objection.