Five companies launched agent payment products in the same week. Here's what nobody's talking about.
What Just Happened
Between Feb 24 and March 1, 2026:
- MoonPay launched "MoonPay Agents" at ETHDenver — wallets, swaps, fiat rails
- Stripe added x402 USDC support and announced Tempo, their own blockchain
- Mastercard demoed Agent Pay at MWC Barcelona
- Coinbase pushed AgentKit hard with new SDK features
- deBridge shipped non-custodial cross-chain execution for AI agents
The agent payment space went from "interesting experiment" to "holy shit everyone's building this" in about seven days.
The Split Nobody's Discussing
These five products break into two camps, and the difference matters more than most people realize.
Custodial (they hold your agent's keys):
- Stripe Tempo — your agent's funds sit on Stripe's blockchain
- Mastercard Agent Pay — traditional card rails, Mastercard controls the pipes
- Coinbase AgentKit — CDP wallets, Coinbase holds the keys
Non-custodial (your agent holds its own keys):
- MoonPay Agents — agent generates its own wallet
- deBridge — cross-chain execution without intermediaries
- agentwallet-sdk (us) — open-source, MIT, agent signs everything locally
Why This Matters
An AI agent with a custodial wallet is an AI agent with a landlord.
When Stripe holds your agent's keys, Stripe decides what your agent can buy. When Coinbase controls the wallet, Coinbase can freeze your agent's funds. When Mastercard runs the rails, Mastercard sets the rules.
That's fine for some use cases. If you're building a customer service bot that processes refunds, sure, put it on Stripe. You probably want the guardrails.
But if you're building an autonomous agent that needs to:
- Pay for API calls across 50 different services
- Bridge funds between chains based on opportunity
- Execute time-sensitive trades without waiting for approval
- Operate 24/7 without a human in the loop
Then custodial is a constraint that will bite you.
OpenAI learned this the hard way last week when a developer's agent accidentally sent $50,000 to the wrong address through a custodial setup. The agent had permission to spend, but no on-chain limits. The custodian's "safety" features didn't help because the transaction was technically authorized.
What Non-Custodial Actually Gives You
On-chain spend limits. Not "we'll try to stop your agent from overspending" — actual smart contract enforcement. The agent physically cannot exceed its budget, even if it hallucinates.
No vendor lock-in. Your agent's wallet works with any x402 server, any DEX, any bridge. Switch providers without migrating funds.
Auditability. Every transaction is on-chain. You don't need to trust a dashboard — you can verify.
Composability. Non-custodial wallets plug into DeFi. Your agent can swap on Uniswap, bridge via CCTP, and pay for an API — all in one transaction flow.
The Practical Tradeoffs
I'm not going to pretend non-custodial is strictly better. It's not.
Custodial is easier to start. npm install @coinbase/agentkit and you're making payments in 10 minutes. Non-custodial requires understanding key management.
Fiat on/off ramps are harder. MoonPay has this, most non-custodial solutions don't. If your agent needs to accept credit cards, you'll end up using a custodial bridge somewhere.
Key management is on you. If your agent loses its private key, nobody's calling customer support. You need proper key rotation and backup.
Our Bet
We built agentwallet-sdk because we think the autonomous agent future is non-custodial by default. v2.5.0 shipped this week with multi-chain support (Base, Arbitrum, Optimism), x402 payments, CCTP cross-chain bridges, and Uniswap V3 swaps.
It's MIT licensed, 199 tests passing, and you can read every line of code. No API keys, no vendor accounts, no terms of service that change when the company pivots.
The agent economy is coming. The question is whether your agents will own their wallets, or rent them.
Building agent infrastructure at ai-agent-economy.com. The SDK is at npmjs.com/package/agentwallet-sdk.
Top comments (0)