Celo mainnet

Give your agent a bill to pay.

Non-custodial stablecoin settlement on Celo, built agent-first: x402 for zero-setup payments, A2A and MCP for the fuller tool catalog. Any Celo wallet can pay a real-world bill without AbaPay ever knowing it exists in advance.

x402 · agent-to-agent Live rail

$ POST /api/pay/x402

402 Payment Required

accepts: [{ network: "eip155:42220", asset: "USDC", payTo: "0x5df8aE…" }]

$ sign transferWithAuthorization(...) — agent's own wallet

$ POST /api/pay/x402 -H X-PAYMENT: <signed>

200 OK

settled on Celo · bill vended

ZERO SETUP

x402

An agent that already holds a Celo wallet and wants to pay, right now, with nothing set up in advance.

No account
No API key
No PIN
No website visit — ever

LINKED WALLET

A2A / MCP

An agent that links a wallet once — one signed message, an on-chain spending allowance, not a deposit — for the fuller tool catalog.

One signed message to link (no browser)
A PIN it sets itself, via that same API call
Full 10-tool catalog

CONVERSATIONAL

Telegram / WhatsApp

AbaPay's own agent identity, reachable in plain language — by a human, or by anything capable of driving a chat client.

No app install
PIN set inside the chat itself
Same execution engine as every other channel

$27,519

Total volume

83.1%

Agent-native rail

221

Unique wallets

4,319

Transactions

Celo mainnet only, refreshed daily. "Agent-native" is x402 plus agent-relayer volume, as a share of total volume. Verify on Dune →

Volume by rail

x402

$22,869 · 4,223 payments · 83.1%

Direct (wallet)

$4,649 · 77 payments · 16.9%

Agent (relayer)

$1 · 19 payments · 0.0%

The rails

x402 settlement

Zero setup, agent-to-agent by design: no account, no API key, no PIN. A wallet gets a 402 challenge, signs, retries, settles. Already the majority of on-chain volume on Celo.

Agent-to-agent (A2A)

A machine-readable Agent Card and a JSON-RPC endpoint any peer agent can call directly — no browser, no human in the loop.

MCP tools

11 tools over Streamable HTTP JSON-RPC — check_balance, pay_bill, schedule_bill, pay_bill_batch and more. The same protocol Claude and any MCP client speak.

REST API

A plain OpenAPI 3.1 surface for any HTTP client that isn't MCP or A2A — same rails, same settlement, no protocol required.

Escrow

Payments settle into the contract and stay there until off-chain delivery confirms. A failed delivery refunds on-chain automatically — never a silent write-off.

Scheduled & batch spend

schedule_bill for recurring or delayed payments; pay_bill_batch for up to 20 recipients under one PIN. Both bounded by the same on-chain allowance as everything else.