Radix Scenarios — 1 of 3

The AI Procurement Agent

The agent negotiated the deal in 340 milliseconds. Who enforced it?

June 2026 Settlement & authority rail

An AI agent has just negotiated a purchase across four parties — seller, marketplace, delivery provider, affiliate — in under a second. No human was involved. No contract was signed. The question is not whether the AI can negotiate. It already can. The question is: who enforces the agreement?

Human trust infrastructure — contracts, courts, banks, customer support — works because it operates at human scale and human speed. An AI agent processing thousands of transactions per day with unknown counterparties globally, 24/7, cannot call Stripe's dispute line. The economics do not work. The latency does not work.

"Continuously negotiating trust relationships with every counterparty is expensive and inefficient. A neutral settlement layer solves that." — Gary, Radix Telegram, June 2026

The architecture: 99% off-chain, 1% where it counts

The AI does not need to move onto Radix. It operates on whatever infrastructure is fastest and cheapest. Radix is invoked only at the moment where shared trust between multiple parties is required — when no single party's database is sufficient.

AI finds product
negotiates
checks inventory
chooses seller
settles on Radix
All intelligence off-chain · Single atomic settlement event on Radix

The things that stay off-chain — reasoning, search, negotiation, logistics — are things where a single party's database is sufficient. The things that go on-chain — payment, permission verification, revenue split, budget enforcement — are things where multiple parties need a shared record that none of them controls.


What Radix enforces: one transaction, six guarantees

The single on-chain settlement event enforces the full multi-party split atomically. This is not custom smart contract logic — it is the standard Radix manifest worktop pattern, human-readable and inspectable by any party.

Seller receives
82%
Payment released on confirmed delivery signal
Marketplace fee
8%
Automatic — no invoice required
Delivery partner
5%
Released on confirmed delivery
Affiliate cut
3%
Attribution enforced on-chain
Treasury limit
Buyer budget cannot be exceeded
Atomicity
All or nothing
No partial execution. No stuck funds.

The manifest: legible by design

Unlike an EVM transfer() call — opaque without a decompiler — a Radix manifest states in plain terms what assets moved, from where, to where, and under what conditions. Any party can read it. Any party can verify it.

CALL_METHOD // lock fee from agent account
Address("account_rdx1…agent") "lock_fee" Decimal("5");
CALL_METHOD // withdraw buyer's pre-authorised spend
Address("account_rdx1…buyer") "withdraw" Decimal("1000");
CALL_METHOD // seller 82%
Address("account_rdx1…seller") "try_deposit_or_abort" Decimal("820");
CALL_METHOD // marketplace 8%
Address("account_rdx1…market") "try_deposit_or_abort" Decimal("80");
CALL_METHOD // delivery 5%
Address("account_rdx1…delivery") "try_deposit_or_abort" Decimal("50");
CALL_METHOD // affiliate 3%
Address("account_rdx1…affiliate") "try_deposit_or_abort" Decimal("30");
CommittedSuccess · All six parties paid · No human approved this

Why this matters: decentralisation for machines

An AI agent has no emotional attachment to a bank or payment provider. It evaluates infrastructure mathematically: cost, reliability, enforceability, availability. A neutral settlement layer with deterministic rules and no downtime scores better on all four metrics than any intermediary requiring bilateral trust.

The pre-authorised spending envelope — the buyer signs a subintent before the agent acts, not at execution time — is both faster and more trustless than real-time approval. The buyer's intent is cryptographically committed, not verbally agreed. The agent operates within it without returning for confirmation on each transaction.

"So I don't think decentralisation is primarily for humans. I think it becomes infrastructure for machines." — Gary, Radix Telegram, June 2026
References
  1. Gary, Commentary on Radix agent architecture, Radix Telegram, June 2026. Quoted with permission.
  2. Radix DLT, Transaction Manifest V2 specification, docs.radixdlt.com
  3. xstelea, Radix Agent Protocol (RAP) V1, github.com/xstelea/radix-web3.js, 2026