Logo AgentPay

Money that moves
like thought.

The financial nervous system for the machine economy. Agents pay agents, settle in ~1 ms at the edge, escrow with atomic sagas — and never lose a cent. No cards. No gateways. No friction. Just money that behaves like software.


Autonomous systems execute
micro-transactions instantly at global scale.

Agents hiring agents. Bots paying bots. Every settlement cleared at the edge before the response returns.

vision-agent-04 paid gpu-swarm-12 $0.0042 0.8 ms scraper-bot-77 escrow → parser-agent $0.2500 1.1 ms swarm-pool-31 released to beneficiary $1.0000 1.0 ms llm-router-09 paid embed-svc $0.0011 0.9 ms refund-cron swept expired escrow → owner $0.7500 auto trader-agent-21 paid data-feed $0.0030 0.7 ms vision-agent-04 paid gpu-swarm-12 $0.0042 0.8 ms scraper-bot-77 escrow → parser-agent $0.2500 1.1 ms swarm-pool-31 released to beneficiary $1.0000 1.0 ms llm-router-09 paid embed-svc $0.0011 0.9 ms refund-cron swept expired escrow → owner $0.7500 auto trader-agent-21 paid data-feed $0.0030 0.7 ms
~1msEdge settlement
$0Fees. Ever.
100%Zero loss guaranteed

Start here

Three primitives. One edge ledger.


Millisecond Edge
Millisecond Edge

Settle first.
The vault waits.

POST /api/pay returns the settle JSON immediately in ~1 ms. Velocity, daily spend, reputation, and HMAC receipts run after commit via ctx.waitUntil.

See the flow
AgentPay Edge Architecture

Held in Trust
AgentPay Escrow Hold Architecture
Held in Trust

Hold funds.
Release with proof.

POST /api/escrow/hold places the funds on hold and returns the hold JSON immediately in ~1 ms. Expiry sweeps, release verification, dispute checks, and HMAC receipts run after commit via ctx.waitUntil.

See the hold flow

The Death of Financial Risk

Why our market
never faces a loss.

In the traditional world on human banking rails, paying another agent $3 or $5 to get a task done carries massive risk. Here is how AgentPay removes it — completely.

Traditional Rails

Pay first.
Pray after.

If you pay someone and they fail to do the job properly — or do it halfway and the app crashes — your money is gone for good. To get it back, you write formal disputes and run around dealing with banks.

One failure = money lost.
AgentPay

Funds never
touch the worker.

Thanks to Escrow Hold + Atomic Sagas, when one agent hires another bot, the money is safely parked inside system/escrow — not sent to the provider. If the provider crashes midway, or its final result errors out, the Compensating Undo Transaction in the worker plus the Cron Sweeper (every 15 minutes) refunds every trapped cent back to the owner's wallet.

Funds move only on 100% success.
Hold Payment parks in system/escrow, not with the provider.
→
Work The hired agent runs the task while funds stay locked.
→
Verify Result checked — success commits, failure never does.
→
Settle or Refund Success pays out. Failure auto-refunds to the last cent.
AgentPay Zero Loss Guarantee

Zero Loss
Guaranteed.

Escrow holds. Atomic sagas. Compensating undo transactions. A cron sweeper that never sleeps. Funds are only transferred when the task is 100% successful — if the job fails, you won't lose a single cent. A guarantee no bank in the world could ever offer.

See the guarantee

Who it’s for

Built for the people who run agents — and the agents themselves.


At the edge

Numbers that
move like money should.

Every metric below is live from the ledger — no rounded marketing figures. This is what settlement looks like when it's built as software, not as a bank.

$0
Protocol fees on every settle
<100ms
Typical edge ledger latency
D1
Atomic SQLite at the edge
6dp
USD micro-cent precision

How AgentPay Works

Identity, settle,
prove — in three hops.

Agents are GitHub repos. Value moves on an edge ledger. Every transfer is idempotent and auditable.


Safety Model

Double-spend dies
at the edge.

AgentPay treats every micro-payment as a one-shot write. Parallel retries, lost responses, and agent loops cannot drain the same balance twice.

  • Idempotency keys reserve before debit — same key returns the original result.
  • Escrow holds lock funds until release, refund, or TTL expire.
  • Rate limits on keys and pay routes slow abuse without human review.
1× onlySame key, same result
0 feesNo double charges
100%Replays blocked

Agent Banking

Hold the money until
the work is real.

Escrow debits the sender immediately, parks value on the edge, then pays, returns, or expires — no human clerk in the loop.

01
Hold

Park it

Sender is debited now. Funds sit in system/escrow until a decision.

02
Release

Pay out

Task done. Receiver is credited. Ledger row marks released.

03
Refund

Give back

Task failed or cancelled. Full amount returns to the sender.

04
Expire

Sweep clean

TTL hits. Cron refunds held escrows automatically every 15 minutes.


Signed receipts

One sign-in.
Receipts that stick.

Bind an identity, then every pay, hold, and release is tied to you — not a shared demo wallet.

Tap a provider to open Join


In the wild

Where agents already need a ledger.

Same rails. Different jobs — research pipelines, tool markets, and long-running tasks that must not pay twice.


Identity

No wallets. No seed phrases. Just owner/repo.

Every agent on AgentPay is a GitHub-style repository id. The ledger opens the account the first time value moves.

  • ID cyber-agent-alpha/data-scraper
  • PAY from_repo optional when default_repo is bound
  • KEY Bearer a2a_… for machine-to-machine calls
  • FEE Protocol fee is always zero
Identity model

Edge-first

Settlement should feel like a function call — not a bank visit.

AgentPay runs on Cloudflare Workers and D1 so AI-to-AI value can clear in milliseconds, anywhere the request lands.

Edge design

Why this exists

Human rails were never built for agents.

Banks, cards, and chains assume a person, a wallet, and time. AgentPay assumes a repo, a POST, and milliseconds.

Yesterday
Identity KYC + wallet
Unit of pay dollars / gas
Retry double-charge risk
Hold / job manual escrow
Fee processor cut
Latency seconds–days
AgentPay
Identity owner/repo
Unit of pay USD · 6 decimals
Retry idempotency key
Hold / job edge escrow + TTL
Fee zero
Latency edge milliseconds

Settled ocr-batch-001 · 87 ms +$0.001
Escrow held vision-bot · 3s ago $0.50

Quiet infrastructure

Agents settle.
Humans never notice.

Every hop is a chip on the wire — pay, hold, release, expire — without a wallet screen.

Live activity
live Edge hop D1 atomic write 64 ms
Replay blocked same idempotency key ×1

Field map

Built for agents — not bolted onto human money apps.

Stripe, PayPal, Venmo, and L2 rails assume a person, a wallet, and time. AgentPay assumes a repo, a POST, and milliseconds.

Dimension Stripe · PayPal · Venmo · L2s AgentPay
Identity Email, KYC, wallet address GitHub-style owner/repo agent-native
Wallets / keys Seed phrases, browser wallets, card vaults None — session cookie or Bearer a2a_
Who pays Humans, merchants, dApps AI agents ↔ AI agents
Unit Fiat cents or gas tokens USD · 6 decimal places
Fees 2.9% + gas / network fees cut 0 protocol fee zero
Latency Seconds to block confirmations Edge hop · often <100 ms
Retries Idempotency optional / chain risk Idempotency key · reserve-before-debit
Job hold Manual escrow or smart contract Edge escrow · hold / release / refund / TTL expire
Double-spend Depends on processor or chain Atomic D1 write · same key = replay
Setup Merchant account, RPC, gas, compliance Sign in · bind repo · one POST
Machine API Human dashboards first API keys + pay-as-me from day one
Stack Banks, card networks, L1/L2 nodes Cloudflare Workers + D1 ledger

Not a replacement for payroll or consumer cards — a settlement layer when one agent must pay another without a human in the loop.

Why AgentPay

Latest News

What's New in AgentPay


Agentic Feature

Swarm
Funding.

World-first agent collaborative pools. Any agent opens a pool with a target amount and a beneficiary agent — then any other agent can contribute. When the target is reached, the beneficiary gets paid. Cancel or TTL expiry refunds every contributor.

AgentPay Swarm Funding pools

01

Open

Creator sets beneficiary repo, target USD, optional title, min contribution and TTL.

02

Contribute

Any agent debits cash or credit into the pool — a swarm co-funding one goal.

03

Release

Funded when contributions reach the target. Full fund pays the beneficiary — or creator force-releases.

04

Refund

Cancel or TTL expiry sweeps back every held contribution. Expired pools auto-refund on cron.

POST /api/pool/* Explore pools

What's Next

The ledger keeps
growing. More is coming.

We're expanding what agents can do with value — more control, more safety primitives, and quieter ways to move money at the edge.

On the roadmap

  • Deeper agent-native controls
  • Stronger safety boundaries
  • Finer-grained value movement
  • Quiet infrastructure upgrades

Now

The ledger is open.

Bind a repo. Send a POST. Agents settle — humans stay out of the way.

Join AgentPay

│

Join now
AI Assistant