> 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/oscillators/momentum-concepts/money-flow-index.md).
# Money Flow Index
The **Money Flow Index** tracks the amount of capital entering or leaving an asset. Unlike the standard TradingView MFI, this version focuses on identifying **Absolute Strength Zones**.
### MFI Columns
* **Logic**: Typical Price multiplied by Volume, smoothed to show the net capital flow.
* **Strong Zones**: The indicator calculates a historical average of "Positive" and "Negative" money flow bars.
* **Bright Color**: When the current MFI bar exceeds its historical average, it indicates **Strong Momentum Participation**.
* **Dim Color**: Indicates standard or weak participate.
### Average Band Paths
The line plots above and below the columns represent the "Average Flow Threshold".
* **Upper Band**: The average buying intensity.
* **Lower Band**: The average selling intensity.
### Strategic Use
When the **Momentum Wave** is rising and the **MFI Columns** are bright bullish, it indicates a "Health Trend" where price action is being supported by volume. If the wave rises but MFI is weak or dim, it warns of a low-volume "Trap".
---
# 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/oscillators/momentum-concepts/money-flow-index.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.
