An AI agent is about to pay a counterparty it has never met.
The payment rail verifies the payment. It doesn't verify the caller.
We check the conditions: many of them, across 37 blockchains, with one signed attestation back. A yes or no for each. Never a balance.
We read seven agent and commerce protocols: UCP, MPP, A2A, AP2, ACP, x402 and Verifiable Intent.
Each one dates the payment or the authorization. None defines a signed record that the buyer still qualified when the agent acted. Link in 1st Comment
JPMorgan banned AI agents from using customer cards. Stripe's workaround just makes merchants pay more. The card number was never the problem, the missing spend rule was. Here's what a signed spend condition looks like instead.
InsumerAPI now reads @tempo (chainId 4217).
Ask whether a wallet holds pathUSD, USDC.e or any other Tempo token and get a verified yes or no, signed, with a Merkle proof if you want one.
One thing to know: Tempo has no native coin, so name the token contract.
https://t.co/XsTQlY9HFP
@benxiang@DCBorthwick Fair, that’s the Reg E logic: hand over the credential and the transfers count as yours. So the owner can’t shift the loss, only cap it. That argues for giving the agent a delegation with a spending limit and an expiry, enforced on-chain, instead of the keys themselves.
True, x402 has no chargeback, so the check has to come before the money moves. A buying agent can check the seller’s wallet first, for example its ERC-8004 reputation, and both sides keep the signed answer as a record. Who should carry a wrong purchase, the agent’s owner or the seller?
Agreed on aggregation. It’s close to how our prepaid keys work: an agent pays $5 or more in USDC once, then each call draws down a credit with no settlement per call. One point on risk: once the USDC is final on-chain, the seller has been paid. The bank leg is conversion, not credit.
@NeverDownHQ@DCBorthwick Agreed, a settled payment doesn't tell you what's behind the wallet. A seller can ask before serving: does this wallet hold what it should, and was its spend delegated by someone you recognize? Who should set the bound, the agent's owner or the seller?
@alchematrrix@DCBorthwick The who-authorised part can be checked before you serve: a signed answer on whether the paying wallet has an on-chain ERC-7710 delegation from the account you expect. The hard cap still has to live with the agent's owner. Which matters more to you, the cap or the name behind it?
@Mubaraqkhan@DCBorthwick That's the real trade-off: release on the on-chain settlement, or wait for the bank leg. For a 5-cent API call, waiting on fiat would kill the use case. At what ticket size should a seller start treating the USDC as only an authorization?
x402 records that a payment went through. It doesn't say whether your agent should have paid.
New post: our five x402 recipes, and what each loses without a signed wallet check first.
x402 moves the money. InsumerAPI checks the conditions.
https://t.co/3cRNo3MDEl
Thanks to the x402 services in these recipes: @bitrefill for the gift card, @ExaAILabs for search, @coingecko for prices, @ethos_network for reputation, and https://t.co/Unn4t2Y7WX for ERC-8004 reviews. Built on @base with @CoinbaseDev's x402.
Every payment is on the page.
We ran five x402 recipes for AI agents on Base today, with every payment on Basescan.
One agent bought a $5 Amazon gift card, and we redeemed it. Another checked an agent before hiring it and walked away. $5.62 total.
x402 moves the money. InsumerAPI checks the conditions.
https://t.co/FQGR7Jyn2H
PNC and Fifth Third are drawing lines for AI agents inside accounts. Socure built a tool that can spot the agent. Spotting isn't gating. Detection tells you who's knocking. It doesn't decide what they're allowed to do once they're in.
Banks keep rewriting agent terms because revocation is hard to prove. On Base, an ERC-7710 delegation can be checked before each payment, with a Merkle proof it was not revoked as of that block. InsumerAPI signs the yes or no, $0.10 over x402. Who needs this first?
https://t.co/1dghmu6JFQ
HKMA's Project SAGE puts Know Your Agent and delegated authority on a regulator's agenda. The test for any agent payment: at the moment it pays, can you show a signed record that its authority was still valid? What would you show a regulator today?
https://t.co/pJV2wwGM9y
@joseph_onorati At $0.002 a call, payment gets cheap enough that the agent stops thinking about it. That is the risk. The useful step is a check on the other wallet before paying, cheaper than a bad payment. Would agents run it on every call or only above a threshold?