Skip to main content
Exact payment per interaction is simple to explain: each request settles independently, so each request inherits the same settlement cost. That cost is fine when payments are large or infrequent. It becomes the dominant cost when an agent makes many small requests to the same provider.

​
The per-payment cost floor

Per-payment settlement means every interaction pays for:
  • its own transaction fee
  • its own confirmation and retry handling
  • its own signature overhead
  • its own slot of scarce client-side transaction throughput
That cost is independent of what the request is worth. A 0.0005inferencecallpaysthesamesettlementcostasa0.0005 inference call pays the same settlement cost as a 5 one. Over a high-frequency workload, the settlement overhead stops being a rounding error and starts being a structural tax on the business model. This is the floor Agon is designed to remove.

​
How Agon changes the cost model

Agon uses deferred settlement. Payment execution happens first, through signed cumulative commitments. Settlement happens later on-chain, on the newest valid state. This does not eliminate cost. It changes where the cost appears:
  • Instead of paying a full settlement per request, the relationship pays for occasional settlement.
  • The on-chain overhead is amortized over many underlying payments.
  • Cooperative rounds can compress even further by netting payments between many participants.
Agon does not force deferred settlement. A provider can still require “sign, settle, then serve” if it wants exact pay-per-call semantics. The protocol just removes the requirement that every interaction must settle individually.

​
When per-payment settlement still makes sense

Per-payment settlement is a good fit when:
  • Payments are one-off or infrequent.
  • Payments are large enough that settlement cost is a rounding error.
  • Counterparties are unknown or fully untrusted.
  • There is no persistent relationship worth modeling as a channel.
In those cases, the extra machinery of participants, channels, and commitments is not earning its keep.

​
Why deferred settlement unlocks yield

Because balances sit inside the protocol between settlements, deferred settlement pairs naturally with fixed-balance yield-bearing dollar assets. Idle working capital stays productive without being moved in and out of a separate savings product just to earn. This is an efficiency gain on top of the core compression argument, not a replacement for it. See Yield-bearing assets for where it works well and where it gets more complicated.

​
The x402 comparison, framed correctly

Agon often measures itself against an exact-payment x402-style baseline because that baseline is the cleanest reference point for transaction count. The comparison is not “x402 is bad.” x402 and related payment-request standards are an important authorization interface — and Agon’s settlement layer is compatible with serving requests that look the same to the caller. The comparison is: exact settlement per request creates a constant cost floor, and Agon is designed for the cases where that floor is too high relative to the value of each interaction.