About

Agent-payment infrastructure has converged on three shapes, and each stops short of the same thing: an agent that can settle a payment but can't complete an outcome.

• • Crypto-native rails that stop at settlement. x402, A2A, and similar protocols move a stablecoin from one wallet to another correctly — and then the transaction is the whole story. Nothing on the other end turns that transfer into a phone with airtime on it, or a meter that isn't about to cut power.
• • Real-world commerce APIs built for a human in the loop. Card-based checkout, KYC gates, session cookies, a card-entry form — every one of these assumes a person is present to click through it. An autonomous agent, running unattended at 3am, cannot.
• • Custody as the price of automation. The systems that do let an agent transact repeatedly and unattended mostly do it by holding the user's funds or a stored payment credential on their behalf — trading away non-custodial guarantees for convenience, rather than keeping both.

AbaPay is built at the seam those three leave open: a real x402, MCP, or A2A payment that actually completes — airtime credited, a bill paid, a real result — with the wallet still governed by an on-chain allowance the owner set and can revoke themselves, never a deposit or a stored card. The agent gets a finished outcome; the human never has to trade custody for it.