> ## 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.

# LI.FI SDK Overview

> Cross-chain and on-chain swap and bridging toolkit

<Info>
  **Building an AI agent?** For AI integrations, we recommend using the [REST API](/api-reference/introduction) directly instead of the SDK. See our [Agent Integration Guide](/agents/overview) for the minimal endpoint set.
</Info>

## Introduction

LI.FI SDK provides a powerful toolkit for developers to enable seamless cross-chain and on-chain swaps and bridging within their applications. Our JavaScript/TypeScript SDK can be implemented in front-end or back-end environments, allowing you to build robust UX/UI around our advanced bridge and swap functionalities. LI.FI SDK efficiently manages all communications between our smart routing API and smart contracts and ensures optimal performance, security, and scalability for your cross-chain and on-chain needs.

**LI.FI SDK features include:**

* All ecosystems, chains, bridges, exchanges, and solvers that LI.FI supports
* Complete functionality covering full-cycle from obtaining routes/quotes to executing transactions
* Easy tracking of the route and quote execution through the robust event and hooks handling
* Highly customizable settings to tailor the SDK to your specific needs including configuration of RPCs and options to allow or deny certain chains, tokens, bridges, exchanges, solvers
* Supports widely adopted industry standards, including [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702), [EIP-5792](https://eips.ethereum.org/EIPS/eip-5792), [ERC-2612](https://eips.ethereum.org/EIPS/eip-2612), [EIP-712](https://eips.ethereum.org/EIPS/eip-712), and [Permit2](https://github.com/Uniswap/permit2)
* SDK ecosystem providers are based on industry-standard libraries ([Viem](https://viem.sh/), [Wallet Standard](https://github.com/wallet-standard/wallet-standard), [Bigmi](https://github.com/lifinance/bigmi))
* Support for arbitrary contract calls on the destination chain
* Designed for optimal performance with tree-shaking and dead-code elimination, ensuring minimal bundle sizes and faster page load times in front-end environments
* Compatibility tested with Node.js and popular front-end tools like Vite

<Info>
  **Looking for one-click DeFi operations?** The SDK fully supports [Composer](/composer/overview) — deposit into vaults, stake, and lend across chains with a single transaction. See the [SDK Composer Integration Guide](/composer/guides/sdk-integration).
</Info>

## How to integrate the SDK

<Steps>
  <Step title="Install the SDK">
    <CodeGroup>
      ```typescript yarn theme={"system"}
      yarn add @lifi/sdk
      ```

      ```typescript pnpm theme={"system"}
      pnpm add @lifi/sdk
      ```

      ```typescript bun theme={"system"}
      bun add @lifi/sdk
      ```

      ```typescript npm theme={"system"}
      npm install @lifi/sdk
      ```
    </CodeGroup>

    Learn more in the [installation guide](/sdk/installing-the-sdk).
  </Step>

  <Step title="Create the SDK client">
    ```typescript theme={"system"}
    import { createClient } from "@lifi/sdk";

    const client = createClient({
      integrator: "YourCompanyName",
    });
    ```

    Find all [config parameters](/sdk/configure-sdk).
  </Step>

  <Step title="Install and configure SDK providers">
    Setup [EVM](/sdk/configure-sdk-providers#setup-evm-provider), [Solana](/sdk/configure-sdk-providers#setup-solana-provider), [Bitcoin](/sdk/configure-sdk-providers#setup-utxo-bitcoin-provider), [Sui](/sdk/configure-sdk-providers#setup-sui-provider), and [Tron](/sdk/configure-sdk-providers#setup-tron-provider) providers.
  </Step>

  <Step title="Request quotes or routes">
    Use the client to request [swap and bridge routes](/sdk/request-routes).
  </Step>

  <Step title="Chains and tools">
    Load lists of available [chains and tools](/sdk/chains-tools).
  </Step>

  <Step title="Token management">
    Find [supported tokens](/sdk/token-management) with all metadata you need.
  </Step>
</Steps>