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

# Background

AiMEE's inception started from the collective vision of blockchain enthusiasts, developers, and entrepreneurs who identified a gap in the integration of AI within messaging platforms. \
\
With a team of developers specializing in machine learning, blockchain technology, and marketing and branding specialists,  AiMEE has become a symbol of innovation within the Telegram sector.

AiMEE underwent meticulous development,  creating a Minimum Viable Product (MVP) that served as the cornerstone for testing and research. During this phase, AiMEE was rigorously fine-tuned, leveraging the dataset gathered to optimize its functionalities and user experience. This process enabled the team to enhance AiMEE's capabilities, making sure it emerged as a fully operational and versatile solution capable of meeting the dynamic needs of its users.

Now it is time to release AiMEE to the public, allowing every chat to hold the power of AI within their community.


---

# 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://aimee-1.gitbook.io/aimee/welcome-to-aimee/background.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.