> For the complete documentation index, see [llms.txt](https://raids-organization-1.gitbook.io/raid-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raids-organization-1.gitbook.io/raid-whitepaper/what-is-raid-all-about.md). # What is RAID all about? RAID, a cutting-edge telegram bot, introduces an exciting concept that enables anyone to initiate raids on their Telegram posts and Twitter tweets. With RAID, users have the power to choose the exact number of raids they desire, making it a uniquely customizable bot within the social media domain. By leveraging RAID, individuals (token owners, call channel owners, twitter accounts and so on!) can enhance their online presence by boosting engagement and increasing exposure. This innovative tool provides users with an opportunity to organically amplify their reach while staying within the boundaries of ethical promotional practices. With its user-friendly interface and powerful functionality, RAID offers a seamless experience for token holders who wish to optimize their social media impact. Now, let's explore the remarkable features and benefits that RAID brings to the table in the next whitepaper sections! --- # 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://raids-organization-1.gitbook.io/raid-whitepaper/what-is-raid-all-about.md?ask= ``` 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.