300,000 satoshis initial limit for AI bitcoin payments via Lightning Labs Wavelength on mainnet

This availability allows AI agents to conduct payments and receive funds, as announced by Lightning Labs on Oct. 23. Developers can now install a client, establish a wallet, and begin utilizing actual bitcoin without needing to operate a Lightning node or manage payment channels.

Michael Levin detailed in the announcement that agents can utilize this system to pay for various services, such as data feeds, individual API calls, and other services provided by different agents. The company stated that transactions can occur without requiring personal approval for every single transfer. This mainnet deployment follows a July announcement where access to the testnet and signet was granted to all, although mainnet usage at that time required an invitation. Despite the opening of mainnet access, Levin confirmed that the product remains in its alpha phase.

In its July release, Lightning Labs introduced a wallet interface designed around structured commands and responses formatted as JSON. The materials released for its launch detail installation support for coding agents such as Claude Code, Codex, Gemini CLI, Cursor, and Copilot. The toolkit utilizes the Model Context Protocol, or MCP, for agents managing the wallet, which presents wallet functionalities as tools that an AI system is capable of invoking. The project's public repository contains documentation for a command that initiates the MCP server, alongside functions for wallet operations like checking balances, sending funds, receiving payments, and reviewing activity.

Lightning Labs' July statement also explained how L402 manages paid services. When a resource is requested by an agent, the server issues a Lightning invoice, and granting payment provides access without needing a pre-existing account or a separately provisioned API key. The company mentioned that developers have the capability to use the identical interface to sell access to their own services. Consequently, an agent can both spend bitcoin when contacting another party and receive payment for an endpoint. According to the launch materials, the processes for wallet creation and unlocking occur outside the agent channel, thereby keeping seed phrases and passwords separate from the model.

The October release specifically incorporates receive-only credentials which lack the ability to sign transactions, recover assets, or manage the wallet. The public repository illustrates a long-running wallet process featuring both gRPC and REST interfaces, offering host applications an alternative method to call its functions. Meanwhile, the developer documentation describes a client responsible for holding user keys, tracking balances, and signing payments, while a managed operator handles settlement and coordination via an Ark-like system. Loop provides the Lightning liquidity that this operator uses.

Its payment documentation clarifies that receiving a Lightning transfer involves an atomic swap into Ark. Conversely, when sending a payment, the operation reverses this, moving value from the wallet’s Ark balance to cover the payment of a Lightning invoice. According to the system guide, users interact with standard BOLT 11 invoices, which enables the wallet to send and receive payments from established Lightning applications. The swap guide points out that the availability of server liquidity and the operator directly influence how payment processing proceeds. Transfers might remain outstanding for several minutes or seconds, and the wallet incorporates refund recovery mechanisms if a payment expires or a swap times out.

Wavelength differentiates between unilateral exits and ordinary cooperative withdrawals in its withdrawal documentation. A cooperative withdrawal necessitates the operator’s co-signature, whereas an emergency exit broadcasts transactions that were signed previously without that necessary cooperation. The documentation cautions users that unilateral exits require more time and incur greater costs. Furthermore, Bitcoin timelocks must elapse, several on-chain transactions might be necessary, and users might need to fund a wallet to cover network fees.

For the public mainnet launch, Lightning Labs specified a ceiling of 300,000 satoshis for accounts and a limit of 50,000 satoshis for every virtual transaction output. Both sending and receiving Lightning payments are subject to a 0.25% service charge, in addition to standard routing fees. The announcement indicated that deposits and withdrawals carry distinct charges, with an estimated cost being displayed prior to payment. Users executing a unilateral exit are responsible for paying the Bitcoin network fees. Levin characterized the release as “still an alpha,” urging developers to report any issues or features that are missing.

Stablecoin payments are still slated for implementation; the July announcement identified Taproot Assets as the intended mechanism to support them through the same interface. Coinbase, a U.S. exchange, started offering Agentic Wallets in February, enabling software to manage funds, execute payments, and trade under controls defined by developers. As crypto.news had previously reported, these autonomous wallet tools include session spending caps and transaction limits. Coinbase’s own launch announcement details security measures that confine private keys within its own infrastructure, alongside checks designed to flag risky activity.

Stripe introduced x402 payments on Base in February, whereupon its product manager, Jeff Weinstein, presented a preview for charging agents using USDC. Stripe’s current machine-payments documentation lists USDC on Base for x402, with the payments ultimately settling into a merchant’s Stripe balance in fiat currency. This stablecoin option is accessible to businesses across the United States, excluding New York, contingent upon Stripe’s access review. Bitcoin is also supported within x402.

In September, Block added Lightning payment support after becoming a member of the x402 Foundation, according to its announcement and earlier reporting on its Lightning payment integration. Block describes x402 as being independent of specific networks and currencies, utilizing HTTP’s Payment Required response to solicit payment during a web interaction. Its stated future plans involve further contributions to Lightning and active participation in the foundation’s working groups.