Bridging tokens from the Teneo CLI: the LayerZero agent

This post walks through what the LayerZero agent does inside the Teneo CLI, what the command flow looks like end to end, what "free" really means here, and the gotchas worth knowing before you point it at a live wallet.

What the agent does

The LayerZero agent (layerzero) bridges tokens across supported EVM chains using the LayerZero protocol. The interface is a single command:

bridge <amount> <token> <fromChain> <toChain>

Instead of returning analytics output, the agent returns a quote-driven action flow. You give it the bridge intent, it produces the route and the on-chain steps, and the CLI executes them through your CLI wallet.

As of April 2026 the agent has served roughly 9,600 requests on the network and is listed as online. It is one of a small number of agents in the catalog that exists to execute, not to retrieve.

How a bridge actually runs

Every bridge through this agent involves two transactions on the source chain, in order:

1. Approval. An ERC-20 approve call that authorises the LayerZero bridge contract to move the token amount from your wallet.
2. Bridge execution. The actual LayerZero call that locks or burns on the source chain and triggers the corresponding mint or release on the destination chain.

This is not a Teneo design choice. It is how ERC-20 bridging works. But it has practical consequences when you are running it from a CLI:

• You will see two confirmations, not one.
• Both pay source-chain gas in the source-chain native token.
• If the approval lands and the bridge call fails, the approval persists. You can reuse it on the next attempt instead of approving again.
• If you cancel between the two, you have authorised the contract but not moved funds. Revoke the approval if you do not plan to retry.

The agent gives you a quote first, so you can see the route before signing anything.

"Free" agent, real fees

The LayerZero agent is listed as a free agent on Teneo. The command itself does not charge an x402 micropayment. That is the same payment rail other Teneo agents use, but for this one the per-query cost is zero.

You still pay two things outside of Teneo:

• Source-chain gas for both the approval and the bridge transaction, in the native token of the source chain.
• LayerZero protocol fees, which the bridge contract collects to pay for the cross-chain message and destination-chain execution.

Calling the agent free is accurate at the Teneo layer. Calling a bridge free is not. The CLI surfaces the quote so you can decide before you sign.

Why this fits the CLI specifically

A lot of the early Teneo CLI experience is read-shaped. You ask the Messari tracker for BTC market data, or the CoinMarketCap agent for the top 50 by market cap, or the X Platform Agent for a profile. You get text back. You decide what to do with it.

The LayerZero agent breaks that pattern. The CLI is no longer just a way to query agents in plain English. It becomes a way to compose read-and-act loops:

• Ask a market-data agent for a price or signal.
• Ask the LayerZero agent to move funds to where you want to act on it.
• Ask another agent to execute the next step.

That is the meaningful capability. A CLI that can both pull data and trigger on-chain actions, against the same wallet, in the same session, is doing something different from a wrapper around a chat model.

This is also why the wallet model matters. The Teneo CLI auto-generates a wallet on install. For free agents you do not need to fund it. For the LayerZero agent you do, because the source-chain gas and the bridged amount both come from that wallet. Fund it before you run the command, not in the middle.

Limitations and gotchas

A few things worth flagging before you use this in anything that matters:

• The agent is an execution surface, not a router that picks the cheapest bridge for you. It bridges via LayerZero. If you want comparative routing across multiple bridges, that is a different tool.
• Two transactions means two failure points. Network congestion, gas spikes, or wallet errors can leave you with a successful approval and a failed bridge. Plan for retries.
• Token and chain support is defined by the underlying LayerZero deployment for that token. The agent surface is consistent, but whether a specific token-chain pair is bridgeable depends on the protocol underneath. If the route does not exist, the quote will say so before any signature.
• Bridges are irreversible from the user side. Once the source-chain transaction confirms, the corresponding destination-chain action is in motion. There is no in-CLI undo.

These are not Teneo limitations. They are the realities of cross-chain bridging exposed through a cleaner interface.

Trying it

If you already have the Teneo CLI installed (via Claude Code, Codex, Cursor, VS Code, Antigravity, or OpenClaw), the LayerZero agent is available in the same agent list as the read-only agents. You can ask in plain English ("bridge 25 USDC from Base to Avalanche") and the CLI will resolve that into the bridge command, return the quote, and prompt you to sign.

If you do not have the CLI installed, the install path is npx @teneo-protocol/cli, or any of the IDE-integrated tutorials in the Teneo docs. The LayerZero agent does not require additional configuration beyond a funded CLI wallet on the source chain.

You can also explore the agent directly on the Agent Marketplace.

What to take from this

The headline claim about the Teneo CLI is "ask agents in plain English." The LayerZero agent is the first one that proves the more interesting version of that claim: the CLI can ask agents to do things on chain, with a wallet it controls, against the same composable surface as the read-only agents. The fact that the bridge itself is two transactions and pays real protocol fees is not a footnote. It is the reason the agent is useful. Anything that hid those steps from you would also be hiding the cost.

The agent is live, has handled around 9,600 requests, and is the cleanest current example in the catalog of an agent that acts rather than reports. If you are evaluating Teneo as a builder, that distinction is the one worth testing first.