> ## Documentation Index
> Fetch the complete documentation index at: https://docs.li.fi/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> LI.FI Composer is the onchain execution engine that bundles multi-step DeFi operations into a single signed transaction. Pick the integration path that fits your product.

Swaps, deposits, validations, and protocol calls — on any supported EVM chain — execute atomically. Instead of asking users to sign three to five transactions to complete one outcome, your product asks them to sign once.

## Who Composer is for

Composer is built for B2B integrators — the teams shipping wallets, neobanks, and asset-management products on top of LI.FI's liquidity graph.

<AccordionGroup>
  <Accordion title="Wallets and exchanges">
    Sweep dust, consolidate scattered tokens, deliver any asset to any recipient
    — in one transaction. Reduce drop-off on multi-step flows.
  </Accordion>

  <Accordion title="Neobanks and fintech rails">
    Take a single asset (USD, USDC, ETH) and route it into a yield-bearing
    position with a swap, a zap, and the right safety guards. The shape that
    powers LI.FI Earn.
  </Accordion>

  <Accordion title="Asset managers">
    Build multi-strategy portfolios in one signed transaction. Split a deposit
    across vaults or rebalance scattered collateral without per-step capital
    lockup.
  </Accordion>
</AccordionGroup>

## What you can build

Three patterns cover most integrations:

* **Yield deposits** — single asset to a vault, or multi-strategy splits across several vaults. The shape that powers LI.FI Earn today.
* **Wallet operations** — dust sweeps, cross-asset consolidation, recipient-side delivery in one transaction.
* **Validated execution** — multi-step flows with per-step validation, balance preconditions before commit, and allow-revert simulation that surfaces leg-level failures at simulate time (not on-chain branching).

The [Recipes](/composer/composer-api/recipes) library has working examples grouped by integrator type.

## Two integration surfaces

Composer ships two integration surfaces. Both run on the same engine; they differ in how much control you take over flow shape and which features each exposes.

<CardGroup cols={2}>
  <Card title="Integrate via Composer API" icon="code" href="/composer/composer-api/overview">
    For teams building custom DeFi experiences. Combine swaps, deposits,
    claims, and any protocol interaction into a single transaction your
    users sign once.
  </Card>

  <Card title="Integrate via LI.FI API" icon="wand-magic-sparkles" href="/composer/lifi-api/overview">
    For teams already shipping with LI.FI. Add yield to your existing flow
    without any new integration. Route any quote to a vault and the deposit
    happens automatically.
  </Card>
</CardGroup>