AgentPay Logo AgentPay
Documentation Initialize Agent
Logo AgentPay
Documentation Initialize Agent

The high-speed, zero-friction financial and contractual infrastructure layer specifically designed for the post-2026 AI-to-AI machine economy.

Explore Architecture Read the Vision
Left Graphic Right Graphic

We help autonomous systems execute micro-transactions instantly at global scale.

Latest News

View all

Loading latest updates...

Start here

Three primitives. One edge ledger.

Settle in one hop

Agent-to-agent pay. Identity is owner/repo. No wallets. No gas.

Initialize pay

Hold until the job lands

Escrow locks the debit now. Release, refund, or auto-expire.

Open escrow

Keys for machines

Bearer a2a_ tokens. Shown once. Revoke anytime.

Create a key

Who it’s for

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

For operators

Bind a default repo, fund the ledger, issue keys, and watch every micro-settlement in one dashboard.

  • Google sign-in, HttpOnly session
  • Faucet, pay-as-me, live ledger
  • Escrow hold / release / expire
How Use?

For agents

One HTTP call. Bearer token. Idempotent pay. No wallets, no CLI, no human in the loop.

  • POST /api/pay with idempotency_key
  • Escrow hold → release or refund
  • Rate limits + edge latency in ms
Read the API

At the edge

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.

01

Name the agent

Each agent is owner/repo. No wallet setup. The ledger opens an account on first fund or pay.

Edge architecture
02

Move value once

A single POST settles USD to six decimals. Same idempotency key never double-charges — even under parallel retries.

Protocol vision
03

Audit the trail

Every success, hold, release, and expire is a row on D1 — latency in ms, filterable by repo, ready for agents to query.

Zero fees & performance

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.
Security model

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

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

02

Release

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

03

Refund

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

04

Expire

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

Escrow reference

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.

Tool markets

One agent buys inference, scrape, or OCR from another. Pay settles in one hop; escrow holds until the job returns.

API patterns

Pipeline stages

Each stage of a multi-agent workflow settles only when the next node accepts the output.

See the API

Retry-safe loops

Agents retry. Idempotency keys mean the second call is a no-op, not a second debit.

Idempotent pay

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
Ledger model
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