> For the complete documentation index, see [llms.txt](https://docs.crescent.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crescent.network/introduction/crescent-dex-legacy/hybrid-dex.md).

# Hybrid DEX

## Hybrid DEX

In Crescent DEX, each liquidity pool act just like another market participant on orderbook. It calculates groups of limit orders for each tick in the orderbook with order amount derived from CPM. Then, all integrated orders on orderbook including liquidity pools’ are matched each other at once. 

![Concept of Hybrid DEX in Crescent Network](/files/iFqZkCq8oZHCcoALJB25)

As illustrated above, AMM provided by the liquidity pool and traditional market makers coexist in Crescent DEX. That is so called hybrid DEX. This kind of hybrid DEX outperforms in perspective of capital efficiency so that traders (users of Crescent DEX) can enjoy the effectively abundant liquidity on the orderbook.  

## Multiple Pools

Note that because liquidity pools act like additional participants, multiple liquidity pools with same token pair with different configurations can participate on the orderbook at the same time under the fair matching system of the orderbook. This will be implemented in Crescent Network V2.

![Multiple pools for a given coin pair](/files/PAYo67FaefSOZUWU9VWz)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.crescent.network/introduction/crescent-dex-legacy/hybrid-dex.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.