> For the complete documentation index, see [llms.txt](https://help.quantower.com/quantower/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quantower.com/quantower/analytics-panels/chart/technical-indicators/moving-averages/demand-index.md).
# Demand Index
The Demand Index is a technical indicator that uses both price and volume to measure buying and selling pressure in the market.
Developed by James Sibbet, this indicator is often seen as a leading signal of future price changes. Sibbet outlined six key rules for interpreting the Demand Index, which are useful for traders looking to apply it effectively:
1. A divergence between the Demand Index and prices suggests a potential price reversal.
2. A high peak in the Demand Index often comes before new price highs.
3. When prices rise but the Demand Index falls, it usually indicates a market top.
4. The Demand Index crossing the zero line signals a change in trend.
5. If the Demand Index stays around zero, it shows weak price movement that likely won’t last.
6. A long-term divergence between the Demand Index and prices points to a major market top or bottom.
To improve the accuracy of their trades, traders should combine the Demand Index with other technical indicators and chart patterns.
Demand Index indicator in Quantower platform
---
# 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://help.quantower.com/quantower/analytics-panels/chart/technical-indicators/moving-averages/demand-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.
