> 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/macro-and-liquidity/macro-credit-model/features.md).

# Features

Macro Credit Model Features

The Macro Credit Model transforms complex fixed-income data into an actionable, visual format right on your TradingView chart, equipping you with robust tools to assess true market risk.

* **Excess Spread Calculation**: Automatically computes the pure credit risk premium by subtracting Investment Grade spreads from High Yield spreads.
* **Statistical Z-Score Normalization**: Uses a configurable lookback period (e.g., 252 days) to dynamically calculate whether current spreads are statistically elevated or suppressed.
* **Dynamic Risk Zones**: Clearly defined and customizable threshold levels for "Stress", "Elevated", "Low", and "Extreme" credit environments, complete with background highlights.
* **On-Chart Signals**: Plots clear signal markers (◼ for Stress, ☐ for Elevated/Low) when the credit spread crosses critical structural thresholds.
* **Comprehensive Dashboard**: Displays real-time metrics including the raw Excess Spread (in basis points), current Z-Score, historical percentile, spread momentum, and a VIX cross-validation check.


---

# 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/macro-and-liquidity/macro-credit-model/features.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.
