> 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/market-valuation-and-on-chain/bitcoin-realized-price-bands/usage.md).
# Usage
Bitcoin Realized Price Bands Usage
Timing macro cycle tops and bottoms in Bitcoin is notoriously difficult. By comparing spot price against the Realized Price baseline, you can use these guidelines to execute long-term accumulation and distribution:
* **Accumulation**: Use the Lower Band and Realized Price levels to identify historic accumulation zones for long-term spot positions. When the price is below the Realized Price, the asset is historically undervalued.
* **Distribution**: Monitor the Overvalued and Extreme Bubble levels to gauge when the market is overheated and consider taking profits.
* **Timing with Signals**: Combine the built-in crossover signals with broader market context to time macro entries and exits effectively.
* **Macro Perspective**: Strip away short-term noise and evaluate Bitcoin's price relative to its fundamental on-chain cost basis.
---
# 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/market-valuation-and-on-chain/bitcoin-realized-price-bands/usage.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.
