> 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/momentum-and-oscillators/sequential-exhaustion.md).

# Sequential Exhaustion

Sequential Exhaustion is not just another oscillator. It is a precision instrument designed for traders who demand clarity in the face of market volatility. By shifting the focus from closing prices to the actual "exhaustion" of demand at price extremes, this tool identifies high-probability reversal points before they become obvious to the rest of the market.

In modern markets, traditional indicators often lag or provide false signals during "blow-off tops" or "climax bottoms."&#x20;

Sequential Exhaustion solves this by:

* **Filtering Noise**: Focusing on price action at the margins.
* **Visualizing Pressure**: Using the Momentum Radar to show exactly when a move is overextended.
* **Validating Reversals**: Providing a signal hierarchy that distinguishes between minor pullbacks and major trend changes.


---

# 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/momentum-and-oscillators/sequential-exhaustion.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.
