
For most of the past decade, the conversation around artificial intelligence and crypto stayed largely theoretical. Two industries, both moving fast, both attracting enormous capital, but mostly running on parallel tracks. That started to change in late 2024, and by early 2026 the overlap had become hard to ignore. MoonPay, the crypto payments firm that built its name on fiat-to-crypto on-ramps, is now positioning itself as the financial infrastructure layer for a future where AI agents don't just analyze markets but actively participate in them.
On February 24, the company officially launched MoonPay Agents, a non-custodial software layer built on top of MoonPay CLI, its developer-focused command-line interface. The product gives autonomous AI systems the ability to generate wallets, fund them through fiat on-ramps or crypto transfers, execute on-chain trades, and convert holdings back to fiat, all without requiring a human to approve each individual step. Less than three weeks later, on March 13, MoonPay followed up with a second announcement: a deep integration with Ledger, the hardware wallet maker, designed to let users sign off on AI-initiated transactions directly from a physical device.
MoonPay CEO Ivan Soto-Wright put it bluntly in the launch statement: "AI agents can reason, but they cannot act economically without capital infrastructure." The line is a bit pithy, but it captures the actual gap. Building a bot that can identify an arbitrage opportunity across three chains is a solved problem in 2026. Building one that can act on that opportunity, fund itself, execute the trade, and off-ramp the proceeds into a bank account without exposing private keys or requiring a human babysitter is not.
MoonPay Agents is designed to close that gap. The setup is relatively straightforward: a developer installs MoonPay CLI, a user completes a one-time KYC verification, funds a wallet, and grants the agent permission to transact within defined parameters. After that initial handshake, the agent can operate independently. Wallets are non-custodial and stored locally on the user's device using OS keychain encryption. Private keys never leave the machine. Spending limits and pre-execution transaction simulations serve as guardrails against runaway agents doing something unintended.
The product ships with 54 tools across 17 categories, covering most of what a developer building a financially active agent would actually need. That includes real-time cross-chain swaps, recurring buy schedules, portfolio tracking, token discovery and analysis, multi-chain deposit links with automatic stablecoin conversion, fiat funding via virtual accounts that accept bank transfers, Apple Pay, Venmo, and PayPal, and the ability to off-ramp back to traditional currencies from the terminal.
Multi-chain coverage at launch spans Ethereum, Solana, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, TRON, and Bitcoin. Over 100 tokens are supported. Developers can also extend the platform with custom skills. The system is compatible with Claude, ChatGPT, Gemini, and Grok, and can be accessed via the CLI, a local Model Context Protocol server, or a web chat interface.
One detail that has caught the attention of developers in the agentic AI space is native x402 support. The x402 protocol, introduced by Coinbase in May 2025, revives the long-dormant HTTP 402 status code to enable machine-to-machine payments using stablecoins, with no API keys or subscriptions required. An agent simply pays for a resource or service at the time of access. MoonPay's inclusion of x402 compatibility positions MoonPay Agents within the emerging standard that Stripe, QuickNode (which extended x402 support across more than 80 chains), and a growing number of infrastructure providers have rallied around.
MoonPay Agents is not architected for one or two bots. The infrastructure is built to support thousands, eventually millions, of agents running concurrently across use cases that range from trading and portfolio management to gaming economies, commerce automation, and corporate treasury operations.
The Ledger Integration
MoonPay's solution was to bring Ledger into the loop. By integrating Ledger's Device Management Kit into the CLI wallet for MoonPay Agents, the company now allows every AI-generated transaction to be routed through a physical hardware device for approval. The agent constructs and proposes the transaction. The user confirms it on the Ledger. Private keys never touch the software layer at any point.
MoonPay says this makes the CLI wallet the first agent-focused wallet to support Ledger's secure signing through the Device Management Kit. Soto-Wright put the strategic framing plainly: "Autonomous agents will manage trillions in digital assets. But autonomy without security is reckless. We built MoonPay Agents with Ledger so intelligence can scale without surrendering control. The agent executes. The human stays in the loop."
Ledger's chief experience officer, Ian Rogers, acknowledged that the partnership reflects a real shift in what wallet infrastructure needs to support. "There is a new wave of CLI and agent-centric wallets emerging," he said, "and these will need Ledger security as a feature, too." It is a meaningful endorsement from a company whose entire value proposition is built on the premise that hardware is the only storage you can actually trust.
The model that results from the integration is structurally similar to two-factor authentication in traditional finance: the AI handles the analytical and execution work, but physical confirmation is required to release funds. Even a fully compromised software environment cannot move money without the physical Ledger device and its PIN.
For developers building agents that need to touch money, the practical implications of MoonPay Agents are fairly direct. The product abstracts away most of the hard parts: custody, key management, fiat connectivity, cross-chain routing, compliance. A single CLI install and a one-time user verification is genuinely all that stands between a developer and an agent that can fund itself, trade across chains, and off-ramp back to a bank account.
The ability to add custom skills also matters. MoonPay Agents ships with 54 tools across 17 categories, but the open extension model means developers can build on top of the existing toolkit rather than working around its edges. That kind of extensibility is usually what determines whether a platform becomes a default or a footnote.
What remains to be seen is how the ecosystem grows around it. MoonPay has the infrastructure and the user base. The question now is whether developers building the next generation of agentic applications pick MoonPay Agents as their default financial layer, or whether a competitor, or a collection of open standards, fills that space instead.
It is worth stepping back from the product details for a moment to consider what MoonPay is actually doing here. This is not a company adding AI features to an existing payments product. It is a payments company making a deliberate bet that the financial system is about to acquire a new class of participant, one that is not human, that will require infrastructure designed specifically for machine-speed, machine-scale capital movement, and that will need to be anchored to compliant fiat rails if it is ever going to interact with the broader economy.
That bet is not obviously wrong. Stablecoin volumes are growing at rates that would have seemed implausible even two years ago. Agent tokens and AI-driven trading systems are proliferating faster than most infrastructure providers anticipated. The convergence of AI and crypto, long discussed in the abstract, is becoming a concrete engineering problem that real companies are being paid to solve.
MoonPay's move is a claim that it has already built most of what that future requires, and that the work of this moment is connecting those existing rails to the autonomous systems that will run on them. It is an ambitious claim. The next 18 months will do a lot to determine whether it holds up.


As the U.S. Senate pushes towards markup for the CLARITY Act, a new bipartisan push in the U.S. Senate is trying to answer another question that has come up again and again in crypto.
When does writing software turn into running a financial business?
At the center of the debate is a bill reintroduced by Senators Cynthia Lummis (R-WY) and Ron Wyden (D-OR) that aims to clarify when crypto developers, open-source maintainers, and infrastructure providers should, and should not, be treated as money transmitters under federal law. The proposal does not try to deregulate crypto wholesale. Instead, it tries to draw a hard line between publishing code and controlling user funds.
That distinction might sound obvious to engineers. To prosecutors, it has been anything but.
For years, the idea of “developer liability” lived mostly in white papers, legal panels, and late-night conference debates. That changed when U.S. authorities began testing aggressive theories that treat certain privacy tools and non-custodial software as unlicensed financial businesses.
Cases involving Tornado Cash and Samourai Wallet turned a theoretical concern into a real one. The message many developers heard was simple and chilling: if people use your software to move money, you might be responsible for how they use it, even if you never touched the funds yourself.
That fear has started to shape behavior. Some teams have shut down. Others have avoided building in the U.S. entirely. Many have quietly redesigned products to remove any feature that could be interpreted as “control.”
This Senate bill is a direct response to that climate.
The proposal, often referred to as the Blockchain Regulatory Certainty Act, rests on a single principle. Developers and infrastructure providers should not be treated as money transmitters if they do not have custody of user assets and do not have the unilateral ability to move or control those assets.
In other words, liability should follow control, not authorship.
If you run an exchange, a broker, or a custodial wallet, this bill does nothing for you. You are still squarely in regulated territory. But if you publish open-source software, operate a node, maintain a wallet interface, or provide routing infrastructure without custody, the bill aims to put you outside money transmitter rules.
That matters because money transmitter classification is not a small thing. It can trigger state-by-state licensing, federal registration, AML obligations, and in some cases criminal exposure if regulators decide you crossed the line without permission.
Even if a developer ultimately wins in court, the cost and risk of getting there can be enough to stop innovation cold.
The word that does all the work in this bill is “control,” and that is exactly where the fight will be.
In clean cases, the distinction is easy. Exchanges custody funds. Non-custodial wallets do not. But crypto is full of gray areas.
Upgradeable smart contracts with admin keys. Front ends that can block addresses. Protocols with pause buttons. Governance structures that look decentralized on paper but concentrated in practice.
Regulators may argue that these forms of influence amount to control. Developers will argue they do not.
The Senate bill tries to anchor the definition to something narrow and concrete: the legal right or unilateral technical ability to move someone else’s assets. Whether that language survives negotiations intact is an open question.
This developer liability push is happening alongside a much bigger legislative effort to overhaul U.S. crypto market structure more broadly. That larger framework aims to clarify which assets are securities, which are commodities, and which agencies oversee what.
What is becoming clear is that developer liability has become a quiet pressure point in those negotiations. Many lawmakers may be willing to compromise on market structure details, but fewer are comfortable backing a system that could criminalize software developers for publishing neutral tools.
In that sense, developer protections are no longer a niche issue. They are a prerequisite for passing broader crypto legislation at all.
If enacted, the bill would not end debates about crypto and compliance. But it would shift them.
First, it would give open-source developers and infrastructure providers a clearer legal lane, especially those building non-custodial systems.
Second, it would encourage business models that minimize custody by design. Expect more architectures that deliberately strip out admin powers, key control, and unilateral intervention.
Third, it would push regulators to focus enforcement elsewhere. Centralized onramps, custodians, stablecoin issuers, and brokers would remain the primary choke points for AML and sanctions policy.
That shift may frustrate some policymakers. It will reassure many builders.
Strip away the legal language and the crypto politics, and this debate boils down to something fundamental.
Is publishing financial software more like writing code, or more like running a bank?
The Lummis-Wyden approach says it depends on whether you control the money. That principle is simple, intuitive, and easy to explain. The hard part will be writing it into law tightly enough to protect neutral builders without giving cover to businesses that function as intermediaries in everything but name.
That fight is just getting started.
You can stay up to date on all News, Events, and Marketing of Rare Network, including Rare Evo: America’s Premier Blockchain Conference, happening July 28th-31st, 2026 at The ARIA Resort & Casino, by following our socials on X, LinkedIn, and YouTube.