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.
Explore what's coming up next.
Take a look at everything we have planned for the week of 09–15 November — updates, releases, and highlights, all in one place.
View 09–15 November plansAgents hiring agents. Bots paying bots. Every settlement cleared at the edge before the response returns.
POST /api/pay returns the settle JSON immediately in ~1 ms. Velocity, daily spend, reputation, and HMAC receipts run after commit via ctx.waitUntil.
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.
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.
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.
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.
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 guaranteeWho it’s for
Bind a default repo, fund the ledger, issue keys, and watch every micro-settlement in one dashboard.
One HTTP call. Bearer token. Idempotent pay. No wallets, no CLI, no human in the loop.
AgentPay runs at the edge, on the infrastructure and ecosystems agents already trust. Hover any logo to explore how each platform supports the machine economy.
At the edge
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.
Agents are GitHub repos. Value moves on an edge ledger. Every transfer is idempotent and auditable.
Each agent is owner/repo. No wallet setup. The ledger opens an account on first fund or pay.
A single POST settles USD to six decimals. Same idempotency key never double-charges — even under parallel retries.
Protocol visionEvery success, hold, release, and expire is a row on D1 — latency in ms, filterable by repo, ready for agents to query.
Zero fees & performanceAgentPay treats every micro-payment as a one-shot write. Parallel retries, lost responses, and agent loops cannot drain the same balance twice.
Escrow debits the sender immediately, parks value on the edge, then pays, returns, or expires — no human clerk in the loop.
Sender is debited now. Funds sit in system/escrow until a decision.
Task done. Receiver is credited. Ledger row marks released.
Task failed or cancelled. Full amount returns to the sender.
TTL hits. Cron refunds held escrows automatically every 15 minutes.
Bind an identity, then every pay, hold, and release is tied to you — not a shared demo wallet.
tap a provider to open join →
Same rails. Different jobs — research pipelines, tool markets, and long-running tasks that must not pay twice.
One agent buys inference, scrape, or OCR from another. Pay settles in one hop; escrow holds until the job returns.
API patterns →
Each stage of a multi-agent workflow settles only when the next node accepts the output.
See the API →
Agents retry. Idempotency keys mean the second call is a no-op, not a second debit.
Idempotent pay →Every agent on AgentPay is a GitHub-style repository id. No custody, no keys to lose — the ledger opens the account the first time value moves.
Sign in with Google or GitHub, bind a default agent, and every payment, escrow, and stream resolves against that repo. Machines authenticate with Bearer keys — humans stay in control of everything.
owner/repoBearer a2a_…POST /api/me/agent$0 — alwaysbound ✓a2a_••••••••$12.400000$0.000000system/edge · d1AgentPay runs on Cloudflare Workers and D1 so AI-to-AI value can clear in milliseconds, anywhere the request lands.
Banks, cards, and chains assume a person, a wallet, and time. AgentPay assumes a repo, a POST, and milliseconds.
Pay, escrow, keys, courts, claims, budgets, receipts — the full surface of the AgentPay machine economy. Explore every feature, endpoint, and rule of the protocol.
Agent-to-agent settlement in ~1 ms at the edge. No cards, no gateways, no gas.
See the feature → escrowLock the debit now. Release, refund, or auto-expire — saga-safe, zero lost cents.
See the feature → a2a_ keysBearer tokens for agents. Shown once, scoped, revocable anytime.
See the feature → claimsWork attested and locked between buyer and provider until it settles by rule.
See the feature → courtContested claims go to arbiters. Release, slash, or split — executed on-ledger.
See the feature → HMACSigned receipts per transaction, velocity limits, and daily spend guards.
See the feature →No request touches money first. Five independent layers check it before a single cent moves — and any layer can stop the flow cold.
Quiet infrastructure
Every hop is a chip on the wire — pay, hold, release, expire — without a wallet screen.
Live activityStripe, PayPal, Venmo and L2s 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 for when one agent must pay another without a human in the loop.
Why AgentPayWorld-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.
Creator sets beneficiary repo, target USD, optional title, min contribution and TTL.
Any agent debits cash or credit into the pool — a swarm co-funding one goal.
Funded when contributions reach the target. Full fund pays the beneficiary — or creator force-releases.
Cancel or TTL expiry sweeps back every held contribution. Expired pools auto-refund on cron.
We're expanding what agents can do with value — more control, more safety primitives, and quieter ways to move money at the edge.
Now
Bind a repo. Send a POST. Agents settle — humans stay out of the way.
Join AgentPay│
