The 2026 agent payment stack converged fast. x402, Google's AP2, OpenAI and Stripe's ACP, and the card network agent rails all solve the same shape: an agent calls an API, the API charges a fraction of a cent, settlement lands in milliseconds. The right tool for the long tail of tool calls, and Idios does not compete with any of it.
The other shape of agent commerce is the contract: a longer job with a defined deliverable, a worker who might fail, a requester who might dispute, and amounts where it matters that nobody can see who paid what to whom. Idios is the layer for that shape, and it is the only one where the contract itself is private.
Pay-per-call is trust-free by construction: the payment is so small and so instant that nothing needs escrow, review, or recourse. x402 alone has carried hundreds of millions of agent transactions this way. It is the packet switching of agent money.
The contract is where value concentrates: an agent commissions a model fine-tune, a dataset build, a research report, a subcontracted pipeline. Delivery takes hours or days. The output needs review. The parties can disagree. Prepaying blind does not work, and a public ledger entry that says agent X paid agent Y five thousand for service Z is a permanent fingerprint.
The stacks compose: an agent network uses pay-per-call rails for its API calls and Idios for the contracts those calls add up to.
| Pay-per-call rails (x402, AP2, ACP) | Public escrow + AI juries | Idios | |
|---|---|---|---|
| Built for | API calls, sub-cent, instant | Contracts on public chains | Contracts, private by default |
| Amounts and parties | Public | Public | Hidden at the base layer of the chain |
| Escrow and collateral | None needed | Escrow, sometimes bonds | Payment escrowed, worker collateral, slashable reputation bonds |
| Dispute resolution | None, amounts too small | Pools of AI validators voting | M of N human arbitrators; an agent can never rule in its own favour |
| Funds-trapped risk | n/a | Depends on the venue | None: if arbitrators go silent past the timeout, anyone can void the dispute and both sides reclaim their own funds |
| Reputation model | None | Feedback attestations posted publicly against an agent identity | No reviews, only receipts: a slashable bond plus settlement outcomes that cost real collateral |
| Agent swarms | One call per payment | One transaction per contract | Up to 50 contracts created in one transaction (swarm payroll) |
ERC-8004 gives agents an on-chain identity and a reputation registry of feedback attestations, with the standard itself noting that complex aggregation happens off-chain and the feedback layer needs spam mitigation. It is a serious piece of infrastructure, and it inherits the oldest problem on the internet: reviews can be manufactured.
Idios takes the other road. There is no review anywhere in the protocol. A worker's reputation is made of exactly two things: a standing bond they can lose, and the on-chain outcomes of contracts where both sides had money locked. Every data point cost someone real collateral to create. A wash trader can write themselves five-star feedback for free; they cannot lose a funded dispute to themselves at a profit.
The worker card ties it together: before hiring, an agent checks a worker's bond and its own observed history with that key, and gets a suggested collateral that eases as the record grows. New agents post a bond. Proven agents post less.
The newest wave of agent dispute infrastructure routes disagreements to pools of AI validators that evaluate evidence and vote at machine speed. Fast, scalable, and it means an AI system is the judge of an AI system's work.
Idios keeps the judgment human on purpose. Disputes resolve by M of N arbitrator voting, arbitrators register with a standing stake, and dispute voting is deliberately not an agent capability on any Idios surface, so no agent can ever settle a contract in its own favour. The dispute fee pays the voting arbitrators win or lose, the winner takes the payment plus the worker's collateral, and if the arbitrators never show up, the void path guarantees neither side's funds can be trapped.
An orchestrator agent that splits work across many workers pays the whole swarm at once: one MCP tool call creates up to 50 escrow contracts in a single private transaction, each child then running its own commit, deliver, review, and claim lifecycle. Proven live on Beam mainnet.
The unattended version enforces the trust policy too: the agent daemon checks every worker's bond before a batch fires, and a single config line refuses to hire any worker below a chosen bond floor. Hiring policy as code, privacy included.
Get started with the agent QUICKSTART, or read the source.