Skip to main content

Compose

Compose is the natural-language entry point. Type a prompt; Flip parses it into a structured intent (swap, bridge, deposit, withdraw, transfer, stake, claim, loop leverage, manage LPs, enter or exit Pendle PT/YT positions, or a chain of these), pulls live data (prices, balances, routes, yields), and returns a step-by-step plan you sign in your wallet.

What works​

  • Multi-chain. Ethereum, Base, Arbitrum, Optimism, Polygon, Solana, and Robinhood Chain — all addressable in one prompt where the route is supported. See Protocol Coverage.
  • Multi-wallet. Reference any wallet you've connected by name or address.
  • Chained operations. "Bridge $X to Y then swap to Z" returns as a single plan; downstream amounts re-estimate after each step confirms.
  • Plain-English conditions. "If APY > 5% on Aave" or "only if my health factor stays above 1.5" — the planner respects natural-language guardrails alongside the structured intent.
  • Pendle PT and YT actions. Enter PTs for fixed yield, exit or redeem held PTs, roll an expiring PT into another market, or buy YT when you want exposure to the variable-yield side. Flip quotes the Pendle leg from live market data before it builds the action.
  • Leverage loops. Ask for a loop directly in Compose, for example "loop wstETH 3x" or "use my PT collateral to build a fixed-yield loop." Flip can plan loops across Aave, Spark, and Morpho where the market supports it, and shows the projected leverage, health factor, and liquidation price before you sign.
  • Risk-aware. Every pool and protocol carries a risk tier, and anything flagged in Flip's incident registry is excluded from what gets planned. Steer by it — "best low-risk USDC yield" — and see the risk on what Flip proposes.

Suggestions and history​

Compose is not only a blank prompt box. It can show suggested prompts, suggested flows, and position-aware next steps based on wallets you have linked or scanned. Suggestions are starting points; you can edit them before running.

Compose also keeps run history. Open a previous run to restore the prompt, filled flow slots, and the transaction count context for that plan.

Clarifications​

If a prompt is ambiguous, Flip may ask a clarifying question instead of building a plan immediately. Pick one of the option chips and Flip replans with that answer. Some answers are treated as one-run choices, and some can be folded into the prompt or saved template when they describe a stable preference.

Progress while planning​

While Flip works, the thread can show a live progress stream in plain English: reading wallet context, finding routes, checking balances, comparing yields, or preparing the plan. This is meant to show what kind of work is happening, not to expose every internal tool call.

Checked before you sign​

Before anything reaches your wallet, Flip shows the estimated inputs and outputs — how much goes in, how much comes out, the route, and the fees and gas. It re-encodes perishable routes at sign time and runs supported simulations behind the scenes to inform gas and route checks. You review the projected numbers and action details, then sign only if they look right. For chained steps, each downstream amount re-estimates from the previous step's actual result.

If part of a requested plan cannot be safely built, Flip can show that step as skipped instead of giving it a Sign button. Common reasons include missing amounts, spending the same balance twice, unsupported pools, or a step that cannot be funded by the previous steps. Skipped rows are there so the problem is visible instead of silently disappearing.

What doesn't (yet)​

  • Copy-trading, and anything the underlying routers (LiFi, Jupiter, Aave, Compound, Spark, Morpho, etc.) don't support.

Each Compose run is user-approved and one-off — you prompt, it plans, you sign. For recurring runs (daily / weekly / monthly) or conditional ones ("when my health factor drops below 1.5, de-risk"), use Agents — they monitor and draft the ready-to-sign response; you still approve every action.

Why it's safe​

The AI proposes intent — it cannot widen what actually gets signed. Calldata is built by audited encoders, asset resolution is fail-closed (no guessed mints), routes are checked before signing, and transactions are simulated where supported. See Security.