> For the complete documentation index, see [llms.txt](https://credia-layer.gitbook.io/credialayer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://credia-layer.gitbook.io/credialayer/product-service/smart-heatmap.md). # Smart Heatmap The Smart Heatmap is a visual intelligence layer of Credia — designed to show traders where capital, sentiment, and narratives are flowing in real time.\ Instead of scrolling through endless dashboards, users can instantly identify which tokens, sectors, and themes are heating up, and which ones are losing momentum. **How It Works** * **Sector Mapping:** Groups tokens and projects into narrative clusters (AI, DeFi, L2s, memes, etc.) to track sector-level flows. * **Momentum Signals:** Highlights surges in activity, liquidity shifts, and social traction within specific clusters. * **Real-Time Updates:** Continuously refreshes to ensure traders see current, actionable movements. **Key Benefits** * **Clarity:** A single visual layer to cut through complexity and noise. * **Timing:** Detect hot narratives before they peak, supporting early positioning. * **Strategy Ready:** Use heatmaps as entry points into deeper AI-driven analysis and execution. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://credia-layer.gitbook.io/credialayer/product-service/smart-heatmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.