> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/statistics/ohlc-range-map-tm/liquidity.md).
# Liquidity
OHLC Range Map Liquidity
The **OHLC Range Map** includes an advanced liquidity detection system that identifies and highlights areas of significant market interest. These zones reflect where buy and sell orders tend to accumulate and where price is more likely to react, especially when they align with key **Manipulation** and **Distribution** levels.
By visually mapping the overlap between liquidity clusters and manipulation or distribution zones, the tool helps traders anticipate potential **market reversals and turning points**. The sensitivity of liquidity detection can be adjusted through a customizable **threshold setting**, allowing users to control the level of detail based on their trading strategy and selected timeframe.
When price approaches a Manipulation or Distribution level that coincides with a liquidity zone, it often represents a **high-probability reversal area**. These confluences frequently signal engineered moves by larger market participants—such as **stop runs or liquidity grabs**—followed by strong directional reactions. Recognizing these conditions can give traders a valuable edge in **entry timing, trade confirmation, and risk management**.
The OHLC Range Map distinguishes between two types of liquidity levels:
* **Liquidity Levels** – Active zones where liquidity remains available and price is likely to respond.
* **Invalidated Liquidity Levels** – Zones where liquidity has already been consumed or taken out.
Users can toggle invalidated liquidity levels on or off, making it easy to focus on **untapped liquidity** while still retaining the ability to review historical liquidity events for added market context.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.candelacharts.com/statistics/ohlc-range-map-tm/liquidity.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
