# ChainBot Introduction

<https://chainbot.io>

ChainBot is a powerful real-time data monitoring and alert platform. It allows you to customize and automate the monitoring of on-chain or third-party platform data according to your needs and provides real-time feedback and alerts through your configured channels, enabling you to stay on top of your project's progress.

ChainBot currently supports the following major categories of monitoring:

> 1. [On-chain Event Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/event-bot)
> 2. [On-chain DEX Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/dex-bot)
> 3. [On-chain Transaction Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/transaction-bot)
> 4. [On-chain Value Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/value-bot)
> 5. [NFT Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/nft-bot)
> 6. [Third-party Snapshot Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/snapshot-bot)
> 7. [On-chain Block Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/block-bot)
> 8. [On-chain Arweave Bot Monitoring](https://docs.chainbot.io/basic-usage/bots/arwwave-bot)

### What key issues does ChainBot address?

> The ChainBot platform is designed to be more flexible and general at the underlying level. The scenarios below are just frequent use cases; for more functionalities, please read the content of "Monitoring/Bots."

1. A whale withdraws a large amount of liquidity from the pool, requiring timely notifications for the next steps.
2. Real-time price change alerts in DEX; for instance, when a new shitcoin is listed in the DEX, you need to monitor its price closely.
3. Monitoring when the NFT floor price drops below the issuance price.
4. High-quality article monitoring alerts on Mirror, allowing you to learn new content promptly.
5. Monitoring hacker address activities; for example, when the FTX hacker address has fund transfers, you need to receive alert notifications immediately.
6. Send alert notifications when the concerned project executes a corresponding proposal on Snapshot, instead of manually refreshing the official UI intermittently.

### Terminology

1. **Bot**

   A set of continuous monitoring rules and alert templates for different categories of data is called a Bot. Bots can be private or public; public Bots can be subscribed to by any user. When a Bot meets the configured conditions, alerts will be sent to all Subscriptions that subscribed to that Bot according to the user's alert channel settings.
2. **Condition(s)**

   The conditions for a Bot to trigger an alert;

   Condition(s) support the comparison of multiple fields. When multiple fields are filled out, the logic for triggering the alert is "AND," meaning an alert will only be triggered when Condition A and Condition B are both met;
3. **Subscription**

   Users need to set up the method and frequency of Bot alerts through Subscriptions. A Subscription can only belong to one Bot, but a Bot can be subscribed to multiple times by different users;
4. **List**

   A List is a collection of multiple Bots. Users can set different types of Bots in different Lists according to their needs for easy management.
5. **Fork**

   Fully copying all data from the original Bot.
6. **Contract**

   Smart contracts deployed on the blockchain.
7. **Notify Channel**

   Alert channels and configurations for receiving messages, such as Slack/Pushover;
8. **Notify Template**

   The template content of the subscription alert notification. When configuring a Bot, the platform will automatically generate a default alert template, which users can modify according to their needs.
9. **DataSources**

   Data sources supported by the underlying architecture of the ChainBot platform.


---

# Agent Instructions: 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://docs.chainbot.io/readme.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.