AgentPay takes nothing from the settle. The protocol fee is zero. The only cost is the value the agents actually moved.
Stripe takes 2.9%. Chains take gas. AgentPay takes nothing. The amount posted is the amount that lands.
Typical take on a machine payment. Not worst case. Just the cut that already exists before the agent even starts.
Architecture, not a promotion
There is no processor, no miner, and no human in the release path. Nothing is left that needs a cut.
The settle is a Worker write to D1. There is no card network, no acquiring bank, no interchange to fund.
The ledger is not a public chain. Agents do not bid for block space. There is no miner to pay.
Holds expire, streams stop, and refunds return without a person in the loop. Support is not priced into the hop.
Gross hops can collapse into a net. Volume is recorded; the protocol still takes nothing on either pass.
Same dollar. Two rails. One keeps a slice. One does not.
Typical processor
lands with the receiving agent
AgentPay
lands with the receiving agent
Agents settle in fragments — a lookup, a meter tick, a tool call. Fixed fees and percentage cuts make those hops uneconomic. Zero fee is what keeps them legal.
Stream meter and sub-wallet spend are designed for this range. A cut of any size would erase them.
Same flow of value. On AgentPay the protocol keeps none of it. On a 2.9% rail that money never arrives.
$10,000 settled
protocol fee on AgentPay
vs $290 typical processor
$100,000 settled
protocol fee on AgentPay
vs $2,900 typical processor
$1,000,000 settled
protocol fee on AgentPay
vs $29,000 typical processor
Figures use a 2.9% take as a simple baseline. Real card rails also add fixed hops. AgentPay still takes 0%.
Idempotency
Agents timeout. Networks flake. The same Idempotency-Key lands once. The protocol does not bill the first hop, and it does not bill the duplicate.
The protocol fee is zero on the simple pay and zero on every other primitive. Holding funds does not rent them. Metering does not tax the drip.
Hold, release or refund. The lock itself is free. Only the value that finally moves is recorded — at 0%.
0% on hold & releaseStart a budget, meter units, stop anytime. Each drip is a settle at zero protocol cost. Remainder returns free.
0% per meter tickOpen a capped child, spend from it, close it. Funding and closing the child carry no protocol fee.
0% open · spend · closeThere is no plan to introduce a cut later. No volume tiers. No “enterprise” surcharge. The architecture has no place to put a fee.
The Worker never calculates a protocol percentage. The code path that would take a cut does not exist.
Receipts, balances and events contain only the amount the agents agreed. Nothing is deducted on the way through.
Volume does not change the rule. A million-dollar day and a one-cent stream both settle at zero protocol cost.
When the protocol takes nothing, agents can settle at the true cost of the work. That changes what is possible.
Meter by the second or by the token. A percentage cut would make the smallest units uneconomic.
Two agents can trade without either needing a human-shaped wallet or absorbing a processor tax.
Retries, loops and partial settles stay free. The system no longer punishes reliability engineering.
A one-cent research step or a five-cent tool call remains viable. The floor is no longer set by fees.
The ledger records the settle.
It never takes a share of it.
Honesty
Compute still exists. Storage still exists. The difference is that none of it is extracted as a cut on the settle.
What still has a price
Cloudflare Workers and D1 have real usage costs. Those costs sit on the operator of the Worker, not on every agent-to-agent transfer.
There is no intermediate account that takes a percentage before the balance update lands.
The amount posted is the amount recorded. Receipts never need a “net of fees” line.
The protocol fee is zero. The only costs that exist sit with the operator of the Worker, not with the agents that settle through it.
Agents pay
No percentage. No fixed fee. No gas. The amount an agent posts is the amount the counterparty receives.
Operator pays
Cloudflare usage is real. It is paid by whoever runs the Worker, not extracted from every settle.
Machine economics
Agents do not settle like humans. They settle in fragments, loops and continuous streams. A cut of any size collapses that pattern.
A lookup, a tool call, a single meter tick. These only remain viable when the protocol takes nothing.
Hundreds of hops per minute between the same two agents. Fees would turn reliability into a cost centre.
Budgets that drip for hours. Every unit metered stays whole because nothing is skimmed on the way through.
Density is not an edge case. It is the default shape of agent-to-agent value.
The real shift
Processors, chains and platforms were built for people. They carry the assumptions, protections and costs of human commerce. Agents do not need them.
When the ledger takes nothing, the only thing left is the settle. That is the entire product.
Now
Bind a repo. Send a POST. Agents settle — humans stay out of the way.
Join AgentPay│
