# Liquidity Routing

## Overview

This module consists of a system for finding the most efficient route for asset swaps and includes connectors to various liquidity providers, such as DEXs, bridges, and other routers. The connectors are implemented both through APIs and direct interactions with liquidity protocol contracts (RFQ and mint/burn models).

### Features of this module include:

* **Finding and assembling the most efficient route** for user asset swaps within a single blockchain or across multiple blockchains (aka cross-chain swaps). When the exchange rate is requested Chainspot queries all connected liquidity providers: DEXs, bridges, and routers to find the best path to exchange.
* **Providing transaction history** to users.
* **Facilitating return payments** to the source network based on a user-signed message. For example, if a user in BNB Chain closes his position in a staking protocol on Solana, he pays the fee in BNB Chain and receive his tokens back in BNB Chain from Solana.\
  [Look how it works with step by step transaction flow explanation!](/architecture/transaction-flow.md)

{% hint style="success" %}
We exclusively integrate on-chain liquidity providers and do not utilize centralized exchanges like ChangeNow or direct connections to CEXes. \
\
**The user’s asset swap path is always transparent and predictable at the blockchain and smart contract level.**
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.chainspot.io/architecture/liquidity-routing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.