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

# Bots

On Telegram/Discord, every project strives to create its community, which separates the parties involved and filters the majority of announcements. This has the additional effect of focusing attention on a small number of well-known products or services, while a big number of good projects miss getting the spotlight they deserve.

*Waxzilla* leverages *bots* for all Wax-related Telegram channels and Discord servers to aid in the cross-promotion of various WAX-based products/services. These bots are used to send Telegram/Discord notifications to people who wish to remain on top of what's happening within the ecosystem.

The users who subscribe to our bots receive notifications for new product listings in specific categories like wallets, marketplaces, P2E, etc. Bots send notifications related to new giveaways and send suggestions of projects based on users' previous activity and interactions. \
\
Discord Bot - \
Telegram Bot -&#x20;


---

# 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://ledgers-organization.gitbook.io/waxzillas-whitepaper/bots.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.
