> 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/investing/macro-and-liquidity/macro-liquidity-gap/usage.md). # Usage Macro Liquidity Gap Usage Finding deep value "Buy Zones" relies on understanding the divergence between central bank liquidity and asset prices. Here is how to interpret the divergence lines and actionable signals: * **Identifying Value**: When the Divergence line drops below the Buy Level threshold, the indicator paints a green **Buy Zone**. This implies that the selected index has fallen much further than the underlying global money supply supports, highlighting a macroeconomic value area. * **Catching Bottoms**: Watch for the **Buy Signal** triangles on the main chart. These appear exactly when the market exits the deep Buy Zone, historically signaling the end of a liquidity-driven correction and the beginning of a fresh uptrend. * **Macro Context**: Use the divergence line to gauge the broader environment. A rising divergence line means liquidity is expanding faster than the market index, which provides a bullish tailwind. --- # 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/investing/macro-and-liquidity/macro-liquidity-gap/usage.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.