> For the complete documentation index, see [llms.txt](https://insightsai.gitbook.io/insightsai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://insightsai.gitbook.io/insightsai/information/introduction.md).

# Introduction

Welcome to Insights AI, the ultimate tool for empowering your trading. Designed exclusively for Telegram, Insights AI revolutionizes your trading experience by offering cutting-edge analytics and insights.

Insights AI is not just a bot—it's a breakthrough in trading intelligence. With powerful AI-driven analytics at your fingertips, you'll gain an unprecedented edge in the crypto market. Whether you're evaluating ROI, tracking win rates, or analyzing trades, Insights AI provides comprehensive data to inform every decision.

With Insights AI, become a more confident and informed trader. It's like having a personal trading analyst, continuously guiding you with detailed reports and predictive insights.&#x20;

Welcome to a new era of empowered trading, where data-driven strategies lead to smarter, more successful investments. Embrace the future of trading with Insights AI. Your journey towards optimized, intelligent trading starts here.


---

# 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:

```
GET https://insightsai.gitbook.io/insightsai/information/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
