> 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/risk-and-portfolio-management/vix-risk-z-score/features.md). # Features VIX Risk Z-score Features The VIX Risk Z-Score transforms complex volatility data into a clear, actionable visual framework right on your TradingView chart. * **Statistical Z-Score Normalization**: Automatically converts the raw VIX data from FRED into a rolling Z-Score, adjusting to the inherent volatility environment over a customizable deep lookback period (default 365 days). * **Automated Risk Thresholds**: Features customizable Overbought (Panic) and Oversold (Complacency) thresholds, defaulting to +2.0 and -2.0 standard deviations. * **Main Chart Candle Overlay**: Seamlessly colors your main chart's price candles based on the VIX Z-Score condition, allowing you to track volatility extremes without taking your eyes off the price action. * **Dynamic Gradient Fills**: Highlights extreme volatility zones in the oscillator pane using beautiful gradient fills to quickly draw your attention to statistical outliers. * **Customizable Theming**: Full control over the colors representing Panic (default Blue), Complacency (default Orange), and Neutral (default Gray) market regimes. --- # 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/risk-and-portfolio-management/vix-risk-z-score/features.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.