Wavelength on mainnet: what an agent can actually pay for

On October 23, 2026, Lightning Labs wrote that Wavelength, its toolkit for adding Bitcoin payments to an app, is live on mainnet for everyone. The company describes a wallet an agent can drive: hold a balance, pay for an API call or a data feed, and settle with another agent, without a person approving each transfer. Lightning Labs, October 23, 2026

That is the claim to check. This note records what the primary post and docs say, what they do not say, and which checks still apply before software is allowed to spend.

What the publisher states

Wavelength is a self-custodial client. The user holds keys. The exit command is described as a way to move a balance back to the Bitcoin blockchain without permission from the coordination service. Lightning Labs, October 23, 2026

Lightning payments go through an atomic swap between Lightning and Wavelength's Ark-like settlement layer, not through channels the app operator opens. The docs say you do not run a Lightning node, manage channels, or source inbound liquidity to accept or send those payments. Wavelength docs, retrieved October 26, 2026

For this release, each mainnet account can hold up to 300,000 sats. Each individual VTXO can hold up to 50,000 sats. Lightning payments carry a 0.25% service fee on send and receive, plus ordinary Lightning routing fees. The toolkit is labeled alpha. Stablecoins are described as planned, not shipping in this post. Lightning Labs, October 23, 2026

Agents can drive the wallet through MCP tool calls (wavecli mcp serve). Wallet creation and unlock stay on the command line, so a seed is not supposed to cross the agent channel. A receive-only credential can be issued that cannot sign, recover, or administer the wallet. Lightning Labs, October 23, 2026

Observation, then interpretation

Observed: a vendor opened its mainnet release to everyone, published caps and a service fee, and documented an agent MCP surface with a receive-only credential.

Interpretation, labeled as such: this lowers the setup cost of giving software a small, inspectable sats budget. It does not by itself prove that any particular agent product enforces a budget, checks delivery, or records a useful receipt.

Loop XXI's earlier journal note listed five checks for a paid agent workflow: define the job, put limits at the authorization point, keep the payment exchange understandable, check what arrived, and leave a record the person can use. Those checks still apply. A live mainnet toolkit is an input to check 2 and check 3. It is not a substitute for them. Loop XXI, October 7, 2026

What remains unknown from the public post

Independent counts of mainnet wallets, completed agent payments, failed swaps, or recovered exits: NOT FOUND in this pass. We did not run the client.

Whether the 300,000-sat account cap and the 50,000-sat VTXO cap are durable product limits or temporary alpha limits: the post states them for this release. Later changes are unknown.

Whether a given application actually uses receive-only credentials, seed isolation, and fee previews: that is an implementation fact. It has to be tested in that application.

Loop XXI does not currently offer Wavelength as a product, and this article is not a claim that Loop Gateway, Lightning checkout, or any Loop XXI payment path is newly cleared. Existing receiver and release holds are unchanged.

A practical way to read the release

If you are evaluating this for an agent that buys a lookup, a file, or another agent's result, write down four numbers before you connect a wallet:

1. Maximum sats the agent may hold.

2. Maximum sats per request, including the 0.25% service fee and expected routing.

3. What a successful result looks like, checked after payment.

4. Where the permission, the payment, and the result are stored so a person can read them later.

If any of those four is missing, the agent is not ready to spend, even if the toolkit is on mainnet.

Wavelength's own docs say this path does not replace running your own node. Self-custody of a small agent budget and operation of a Lightning node are different jobs. Choose the one the product actually needs.