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

# Usage

Mean Reversion Oscillator Usage

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-bc046aa4a1999514b33f8d3d9c19179f2581758d%2Fdocs-mean-reversion-oscillator-002.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Mean Reversion Oscillator (MRO)** is not meant to generate standalone buy or sell signals. Instead, it acts as a **contextual guide**, helping traders see when price is stretched away from its mean and when a reversion or momentum shift may be more likely.

The **MRO** is best viewed as a **context indicator** that highlights when price is statistically stretched from its mean.

1. **Add to chart:** Paste the script in TradingView and load it in a separate pane.
2. **Set MA Length:** Use **20–50** for intraday, **100–200** for swing/position trading.
3. **Match StdDev Length:** Keep it close to the MA Length to avoid distortion (e.g., MA 200 → StdDev 200).
4. **Interpret readings:**
   * **>70 (Overbought):** Price stretched high, reversion or slowdown likely.
   * **<30 (Oversold):** Price stretched low, bounce potential.
   * **50 (Midline):** Neutral, momentum shift point.
5. **Use with confluence:** Strongest signals occur when MRO extremes align with **S/R levels, trend filters, or volume cues**.
6. **Adjust thresholds:** Default 70/30 is balanced; 80/20 gives fewer but stronger signals, 60/40 gives more but weaker ones.
7. **Stay trend-aware:** In strong trends, OB/OS can persist. Always check higher timeframe bias before fading moves.


---

# 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/usage.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.