> 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/mean-reversion-oscillator/confluences.md).

# Confluences

Mean Reversion Oscillator Confluences

The **Mean Reversion Oscillator (MRO)** works best when used alongside other tools and market context. On its own, it shows when price is stretched away from its mean, but when combined with other signals, it becomes a powerful confirmation tool. Below are the **five strongest confluences** to increase reliability and reduce false signals.

* **Support & Resistance Levels**
  * When MRO signals **Overbought** at a resistance zone → stronger short bias.
  * When MRO signals **Oversold** at a support zone → stronger long bias.
* **Trend Filters (e.g., 200 EMA/SMA)**
  * Fade signals only in the direction of the higher-timeframe trend.
  * Example: Take oversold longs only when price is above the 200 EMA.
* **Volume & Liquidity Tools (VWAP / Volume Profile)**
  * If MRO is OB/OS while price is rejecting VWAP or a high-volume node, the confluence is very strong.
* **Volatility Bands (Bollinger / Keltner)**
  * MRO Overbought + price outside the upper band → potential reversal.
  * MRO Oversold + price outside the lower band → bounce setup.
* **Divergences with Price**
  * **Bullish divergence:** Price makes a lower low, but MRO prints a higher low → momentum loss in sellers.
  * **Bearish divergence:** Price makes a higher high, but MRO prints a lower high → momentum loss in buyers.

⚡ **Pro tip:** The highest probability trades occur when **3 or more confluences** align (e.g., MRO Oversold + Support + Bullish Divergence).


---

# 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/mean-reversion-oscillator/confluences.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.