> For the complete documentation index, see [llms.txt](https://docs.cryptocart.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptocart.cc/the-ccv2-token/cryptocart-dashboard.md).

# CryptoCart Dashboard

The CryptoCart Dashboard platform is designed to provide comprehensive insights and analytics for monitoring store traffic, and performance for our Gift Card Store. We have been making some fine tunes based on community feedback, such as integrating a chart of the CryptoCart Vault balance to showcase how every purchase on our store buys back and supply from the open market, and removes it from circulation and no markup to our customers.

<figure><img src="/files/XeH7uohHWyjJnCz6vEco" alt=""><figcaption></figcaption></figure>

This release is currently on V1, and subject to changes based on community feedback and suggestions. If you had any input, or would like any additional data exposed feel free to let us know or bring it up to the community for discussion.


---

# 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://docs.cryptocart.cc/the-ccv2-token/cryptocart-dashboard.md?ask=<question>&goal=<endgoal>
```

`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.