> For the complete documentation index, see [llms.txt](https://docs.marketcompass.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketcompass.ai/tech-solutions/data-visualization.md).

# Data Visualization

At Market Compass, we believe in the power of data visualization to empower users with actionable insights and intelligence. Through our individual dashboards and comprehensive filtering capabilities, users can explore and analyze cryptocurrency data with precision and ease. Here's how we enable users to uncover valuable insights through data visualization:

**1. Individual Dashboards:**

* We provide each user with a personalized dashboard tailored to their specific interests and preferences.
* Users can customize their dashboards by selecting data filters, visualization options, and analytical tools to suit their investment strategies.

**2. Advanced Filtering Options:**

* Our platform offers advanced filtering options to allow users to refine their data queries based on various criteria.
* Users can filter data by narrative, project, token, data source, X (Twitter) account, influencers, and data types (fundamental analysis vs. marketing content).

**3. Overall Sentiment Analysis:**

* We present users with an overall sentiment analysis, indicating the general sentiment within the cryptocurrency market.
* This high-level overview helps users gauge market sentiment trends and sentiment-driven price movements.

**4. Narrative Sentiment Analysis:**

* Users can explore sentiment analysis results specific to different narratives within the cryptocurrency ecosystem.
* By analyzing narrative sentiment, users can identify leading narratives and assess their impact on market dynamics.

**5. Project Sentiment Analysis:**

* Our platform provides sentiment analysis for individual blockchain projects, allowing users to evaluate the sentiment surrounding each project.
* Users can identify projects with positive sentiment trends and potential for future growth and adoption.

**6. Narrative Mindshare:**

* We offer insights into narrative mindshare, highlighting which narratives are currently dominating discussions within the cryptocurrency community.
* Users can identify emerging narratives and assess their relevance to investment opportunities.

**7. Project Mindshare:**

* Users can explore project mindshare data to identify leading projects within each narrative.
* This information helps users discover new and under-the-radar projects with high potential for future growth.

**8. Price Prediction:**

* Our platform provides price prediction models based on historical data and sentiment analysis.
* Users can leverage these predictive models to anticipate future price movements and make informed investment decisions.


---

# 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.marketcompass.ai/tech-solutions/data-visualization.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.