> For the complete documentation index, see [llms.txt](https://docs.dapplooker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapplooker.com/dapplooker-analytics/case-studies/dapplooker-telegram-bot.md).
# DappLooker Telegram Bot
The rapid growth of the cryptocurrency market has led to an increased demand for accurate and timely data analytics. To address this need, DappLooker introduced its innovative Telegram Bot, an extension of its data analytics platform. This case study delves into the features and benefits of the bot and investigates its successful integration within the GRT Curation community.
Key Features of the DappLooker Telegram Bot:
1. Real-time Data Updates: The Telegram Bot connects to DappLooker's data source in real time, ensuring that the latest information is readily available to users. This feature is particularly crucial in the ever-changing cryptocurrency landscape, where timely data can influence trading decisions significantly.
2. Detailed Analytics: DappLooker's Telegram Bot offers comprehensive analytical insights into various cryptocurrencies and blockchain metrics. From price trends and trading volumes to on-chain activities and network statistics, the bot provides a holistic view of the crypto market.
3. Visualizations and Infographics: To simplify complex data, the bot generates visualizations and infographics. This feature enhances data comprehension and enables even novice users to grasp critical insights.
**Use Case: Integration in GRT Curation Community:**
The GRT Curation community, known for its involvement in Governance Tokens, adopted the DappLooker Telegram Bot to streamline information dissemination and promote data-driven discussions.
---
# 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.dapplooker.com/dapplooker-analytics/case-studies/dapplooker-telegram-bot.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.
