Skip to main content
Enso turns product intent into executable transaction data. Most integrations combine a small set of primitives: discover what can be shown, read what the user owns, request a route or bundle, submit the returned transaction, and refresh balances after execution.

The Enso Mental Model

Standard Build Flow

  1. Discover supported chains, tokens, protocols, actions, and yield destinations.
  2. Read the user’s balances and current DeFi positions.
  3. Build a Route request when Enso should find the path, or a Bundle request when your product controls the action sequence.
  4. Ask for approval only when the route or bundle spends an ERC-20 through the router and allowance is insufficient.
  5. Submit the returned transaction as-is.
  6. Track bridge status only for async cross-chain routes.
  7. Refresh balances and position metadata after confirmation.

Route API, Bundle API, and enso:route

Use the canonical Route API vs Bundle API comparison to choose an endpoint. Route API lets Enso choose the path. Bundle API lets your product submit an ordered action array. The enso:route action is one action available inside that array. Actions executed in one same-chain transaction are atomic. Cross-chain delivery and destination callbacks are asynchronous; monitor them through Bridge Status.

Product Entry Points

UI Fields To Plan For

Updated