> 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/volume-concepts.md).

# Volume Concepts™

The core philosophy behind the **Volume Concepts** is that volume is the primary driver of price. When price moves without volume, it is often a "trap" or a temporary fluctuation. When price moves with high volume, it represents a true shift in market sentiment.

Most traditional trading tools use a "one-size-fits-all" approach to market data. They assume that every price move is equally important. The Volume Concepts challenges this by using advanced statistical modeling that treats the market as a dynamic, living system. Instead of looking for simple crossovers, it looks for **Intensity** and **Exhaustion**.

#### Why use a Matrix approach?

The indicator synchronizes different layers of data:

* **The Price Layer**: Tracking where the current price sits relative to its recent history.
* **The Volume Layer**: Measuring the strength behind every move.
* **The Volatility Layer**: Automatically adjusting the "sensitivity" of the tool based on how fast the market is moving.

By bringing these three layers into a single, easy-to-read oscillator, the Volume Concepts removes the need for multiple cluttered indicators on your chart. It provides a "single source of truth" for momentum and trend health, helping you stay on the right side of the market with confidence.


---

# 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/volume-concepts.md?ask=<question>&goal=<user_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.
