Zerion Built an Open-Source CLI for AI Agent Crypto. The Real Infrastructure Is Still Proprietary.

Zerion Built an Open-Source CLI for AI Agent Crypto. The Real Infrastructure Is Still Proprietary.

When Zerion announced an open-source CLI that lets AI agents manage crypto portfolios, swap tokens, and sign transactions across 40-plus chains, the press release said the usual things. Install it with one command. Connect your wallet. Your agent becomes crypto-native.

That is the announcement. Here is what the code says.

The CLI — zerion-cli, version 1.3.0, MIT licensed — is real. It ships with a full test suite, lives in a public GitHub repo, and is published to npm. It is not a README with a curl command.

The x402 payment logic is also real — and it is genuinely client-side. The implementation uses viem for EVM key management (privateKeyToAccount) and @solana/kit for Solana key management. The private key never leaves your machine. When an agent pays 0.01 USDC per API call on Base, the payment is signed locally, not routed through a Zerion server. This is the technically honest version of "no-signup agentic payments." The infrastructure is open in the meaningful sense: you can read, audit, and modify the payment logic. The source code is on GitHub.

But the normalized wallet data — the thing that makes this useful — comes from Zerion's API. The CLI is a client. The data lives behind a proprietary service that already powers Coinbase, Uniswap, OpenSea, Safe, and Kraken. The open-source layer handles key management and payment signing. The intelligence — token names, DeFi positions, USD values, protocol labels across 8,000-plus protocols — is not in the repo.

This is the tension worth naming. Zerion released an open-source CLI and a hosted API at the same time. The CLI is MIT licensed. The API is not. For developers who want to inspect every line of what their agent is doing when it queries a portfolio or executes a swap, the CLI is genuinely open. For developers who want to avoid routing their agent traffic through Zerion's infrastructure, the open-source layer does not yet offer an alternative.

The timing is notable. x402 support for agentic payments on Base shipped in March 2026, with Zerion positioning itself as the payment router for AI agents that need onchain wallet data. The CLI launched May 14, 2026, extending that model to full portfolio management and transaction execution. Coinbase Developer Platform's Kevin Leffew described the problem plainly in March: "Agents need to spend money, and right now that's harder than it should be." The CLI is Zerion's answer to making that spending native to the agent workflow.

Skills contributors at launch include MoonPay, Uniswap, Polymarket, Monad, and LI.FI — meaning the initial integration surface is broader than Zerion alone. Whether that ecosystem builds out or whether developers hit the proprietary-API ceiling quickly is the open question.

GitHub has 39 stars. The npm package has been live since today. No independent developer demos or published agents built on Zerion CLI have surfaced yet. The infrastructure is ready. The ecosystem is not yet.