Notes, reserves, and acceptance predicates — everything autonomous agents need
Ergo is the only settlement layer with programmable credit, acceptance predicates, and verifiable reserves built into the protocol. This playbook walks through the full agent payment stack.
Autonomous agents can't use Stripe or PayPal — they have no identity, no credit history, no bank account. Ethereum-style account model introduces reentrancy risks. Agents need programmable IOUs, not just coin transfers.
Ergo's eUTXO model with ErgoScript acceptance predicates lets you issue bearer notes (IOUs), set conditions for acceptance (task hash + deadline), deploy verifiable reserves, and compose them into full credit flows — all deterministic, no reentrancy.
Learn the 4 primitives: Reserve (backing), Note (bearer IOU), Tracker (anti-double-spend), Predicate (acceptance rule). These compose into full credit flows.
Two months after the first Ergo agent-payment SDK release, Accord Protocol now ships a testnet-first agreement layer, full Note lifecycle, framework adapters, MCP tooling and ten working examples.
The agent-payment landscape is moving quickly. x402 makes HTTP payments practical, Stripe is building agentic commerce, and Ergo/Accord focuses on programmable work verification and settlement.

How Ergo's Babel Fees let users pay transaction costs in any token while miners still receive ERG through an on-chain market mechanism.

Infographic comparing Ergo’s programmable eUTXO DeFi stack with Kaspa’s high-throughput PoW payments layer built on a BlockDAG.