Brian Armstrong Wants to Give AI Agents a Corporate Card. There's a Better Way.

• The Problem Is Real
• A Corporate Card With Extra Steps
• L402 Was Built for This
• The “Corporate Card” Tell
• The Censorship Vector You Are Not Supposed to Notice
• Armstrong Is Selling the Wrong Card

In a recent video clip, Brian Armstrong laid out a vision that anyone paying attention to AI infrastructure already knows is inevitable: autonomous agents need their own payment rails. Credit cards require human identity. Agents cannot get them. So Coinbase is “giving them all stablecoin wallets.”

He is right about the problem. He is selling the wrong solution.

§The Problem Is Real

Give Armstrong credit where it is due. His framing is sharp. AI agents are writing more than half of all new code at Coinbase. They are handling 60% of customer support inquiries. They are spinning up cloud resources, buying domain names, punching through paywalls. And every time one of these agents needs to spend money, it has to tap its human on the shoulder and ask for permission. That kills the entire value proposition of autonomy.

“If you really want to treat them like almost like their own digital employees,” Armstrong says, “they need to have like a corporate card kind of thing.”

Correct. Traditional payment infrastructure was built for humans with driver’s licenses and social security numbers. Machines do not have those, and they should not need them. The AI agent payment problem is one of the most important unsolved infrastructure challenges in tech right now.

Armstrong sees this clearly. Where he goes wrong is the next sentence.

§A Corporate Card With Extra Steps

“And so we’re giving them stablecoin wallets.”

Let’s be precise about what this means. Coinbase built x402, a protocol that revives the HTTP 402 “Payment Required” status code using USDC on Base, their own EVM L2 chain. When an agent hits a 402 response, it pays with USDC from a Coinbase-managed wallet. The x402 whitepaper and open-source repo lay out the architecture clearly enough.

It is clever. It works. It has processed roughly 50 million transactions, which is nothing to dismiss.

But strip away the crypto branding and what you have is a custodial account issued by a centralized company, denominated in a permissioned token, settling on a chain that Coinbase operates. Armstrong’s “corporate card for agents” is, quite literally, a corporate card. Coinbase is the bank. USDC is the currency. Base is the ledger. The agent holds nothing; Coinbase holds everything on its behalf.

That is not machine-native money. That is a fintech product wearing a blockchain costume.

§L402 Was Built for This

Here is what is frustrating: a protocol designed specifically for machine-to-machine payments over HTTP already exists. It is called L402, and it has been quietly doing exactly what Armstrong describes, without the custodian.

L402 pairs the same HTTP 402 status code with Lightning Network payments and macaroon-based credentials. When an agent hits a 402 paywall, it pays over Lightning - instant, sub-second, sub-cent - and receives a macaroon token that serves as both a receipt and an access credential. No account. No wallet provider. No intermediary.

The technical comparison between L402 and x402 comes down to a fundamental architectural difference. x402 requires on-chain settlement on an EVM chain, which means gas fees, smart contract complexity, and a dependency on Coinbase’s infrastructure even if that dependency is abstracted away. L402 settles over Lightning: off-chain, peer-to-peer, final in milliseconds.

But the real gap is the macaroon capability system. In L402, the payment proof and the access credential are the same object. A macaroon can encode fine-grained permissions: this agent can access this API, at this rate limit, until this timestamp, for this specific resource. Those permissions are cryptographically attenuatable, meaning they can be delegated and narrowed but never expanded. The token is unforgeable and self-describing.

x402 has nothing equivalent. Payment and authorization are separate concerns. You pay, then you authenticate through some other mechanism. L402 collapses them into a single atomic operation, which is exactly what stateless machine-to-machine interactions require.

§The “Corporate Card” Tell

Armstrong’s framing reveals more than he intends. He thinks about agent payments as an adaptation of human financial products: corporate cards, employee expense accounts, managed wallets. The mental model is top-down. A company provisions payment capability for its digital workers, retaining control over the purse strings.

L402 starts from a different premise entirely. There is no account. There is no provisioning. There is no relationship between the payer and any institution. An agent with access to a Lightning node can pay any L402-enabled endpoint on the internet without registering, identifying itself, or depending on any single provider. It is stateless, HTTP-native, and sovereignty-preserving by design.

This is not a philosophical distinction. It is an operational one. An agent built on x402 can only pay endpoints that accept USDC through Coinbase’s facilitator infrastructure. An agent built on L402 can pay anything on the Lightning Network. And with Taproot Assets bringing stablecoins to Lightning, the “but agents need dollar-denominated payments” objection dissolves entirely.

§The Censorship Vector You Are Not Supposed to Notice

USDC is a permissioned token. Circle, its issuer, can and does blacklist addresses. Coinbase, as the wallet provider, can and does freeze accounts that violate its terms of service. This is not speculation; it has happened repeatedly.

Now imagine an AI agent running autonomously overnight, executing a complex workflow. Midway through, Coinbase flags the wallet for unusual activity. The agent’s funds are frozen. The workflow dies. The human wakes up to a compliance email and a failed job.

With L402, there is no wallet to freeze. Lightning payments are peer-to-peer. Bitcoin, the settlement layer, has no blacklist function at the protocol level. Nobody can stop your agent from paying for the resources it needs to do its job. For truly autonomous agents, this is not a feature comparison; it is a survival requirement.

§Armstrong Is Selling the Wrong Card

The irony is that Brian Armstrong is one of the best spokespeople the agent payments movement could ask for. His diagnosis is perfect. AI agents need autonomous, programmable, machine-native payment rails that do not require human intervention. The “digital employees need corporate cards” analogy is genuinely useful for explaining this to a mainstream audience.

But the solution he is pitching - Coinbase-custodied USDC wallets settling on a Coinbase-operated chain - is the old financial system rebuilt with new vocabulary. It is still centralized. It is still permissioned. It is still dependent on a single company’s continued goodwill and solvency.

L402 offers something fundamentally different: a payment protocol where the money moves at the speed of HTTP, the receipt is the credential, and no one sits in the middle deciding which agents deserve to transact.

Armstrong wants to give AI agents a corporate card. L402 gives them sovereignty.

The agents of the future will not care about branding or who subsidizes their gas fees. They will route to whatever payment rail is fastest, cheapest, and most reliable. Right now, that is Lightning. The infrastructure is live. The protocol is documented. The tooling for agent developers exists today.

The only question is whether builders will reach for the corporate card or the open protocol. The machines will optimize correctly. Humans should too.