> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enso.build/llms.txt
> Use this file to discover all available pages before exploring further.
# Get Started
> Choose the right Enso API path for swaps, zaps, Earn products, cross-chain execution, custom workflows, and third-party transaction validation.
export const date_0 = "2026-05-14"
Enso helps you build DeFi flows by returning transaction data your user can sign. First [create and verify an API key](/pages/build/get-started/authentication), then choose the product path that matches what you are building.
## What Are You Building?
| Product goal | Start here | Use these APIs |
| -------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Add swaps, zaps, or direct deposits to a wallet | [Route](/pages/build/get-started/route) | `POST /v1/shortcuts/route`, token data, balances |
| Build an Earn tab or yield marketplace | [Enso Earn](/pages/earn/overview) | `GET /v1/tokens`, `GET /v1/wallet/balances`, `POST /v1/shortcuts/route`, conditional `GET /v1/wallet/approve` |
| Move a user into a tokenized position from any supported asset | [Route](/pages/build/get-started/route) | Route plus token metadata and refreshed balances |
| Build a cross-chain deposit or bridge flow | [Crosschain Routing](/pages/build/get-started/crosschain-routing) | Route, `destinationChainId`, bridge callback parameters, bridge status |
| Create a custom multi-action workflow | [Bundle API](/pages/build/get-started/bundling-actions) | `POST /v1/shortcuts/bundle`, actions, dynamic outputs, checks |
| Show current assets and DeFi positions | [Balances](/pages/build/get-started/balances) | `GET /v1/wallet/balances` plus token metadata |
| Discover supported protocols and yield destinations | [Protocol Data](/pages/build/get-started/protocol-data) | `GET /v1/tokens`, protocols, standards |
| Validate a transaction generated outside Enso | [Quoter](/pages/quoter/overview) | Quoter simulate and validate endpoints |
## Standard Integration Flow
1. Discover available chains, tokens, protocols, and destination positions.
2. Read the user's balances to decide what they can spend or migrate.
3. Request a Route when Enso should find the path, or request a Bundle when your product controls the ordered actions.
4. Request approval only when spending an ERC-20 through the router and allowance is insufficient.
5. Submit the returned transaction as-is.
6. Poll bridge status only for async cross-chain routes.
7. Refresh balances and token metadata for the final UI state.
## Route API vs Bundle API
| Use case | Use Route | Use Bundle |
| ------------------------------------------------------ | --------- | -------------------------------------------- |
| Token swap | Yes | Rarely |
| Zap into one vault, LP, or tokenized position | Yes | Only when custom actions are required |
| Withdraw or redeem one position | Yes | Only when follow-up actions are required |
| Position migration | Yes | Use Bundle if fixed action order matters |
| Harvest, borrow, repay, leverage, or claim | No | Yes |
| Cross-chain route into a destination token or position | Yes | Use Bundle only for custom post-bridge logic |
| Multiple checks, dynamic outputs, or custom callbacks | No | Yes |
The **Route API** is the standalone `/shortcuts/route` endpoint: Enso selects the path and returns one signer-ready transaction. The **Bundle API** accepts an ordered array of actions selected by your product. Inside a Bundle request, `protocol: "enso", action: "route"` is the **`enso:route` bundle action**, not the standalone Route API.
## Core Guides
Learn the Enso primitives: token data, balances, route, bundle, approval, bridge status, and Quoter.
Find optimal paths for swaps, zaps, deposits, withdrawals, migrations, and simple cross-chain flows.
Build product-controlled multi-action workflows with dynamic outputs and checks.
Discover supported tokens, protocols, yield metadata, APY, TVL, underlying assets, and logos.
Show current wallet assets, DeFi positions, and post-execution balances.
Route from a source chain into a destination chain token or position.
## What To Show Users
| Moment | Show this | Source |
| ------------------ | ------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| Before action | Available source assets, current positions, APY, TVL, protocol, chain, token metadata | Balances and tokens |
| Quote review | Expected output, minimum output, gas, price impact, route path, approval requirement | Route or Bundle response |
| Signing | The returned transaction exactly as provided by Enso | `tx` |
| After confirmation | New source balance, new destination position, current APY, remaining dust, bridge status if cross-chain | Balances, token metadata, bridge status |