# The How

### Barebones

The underlaying structure that's also the core of Cerbero Tools is its **backend**.\ <mark style="color:$info;background-color:$info;">A single place where all the data is processed block by block with blazing speeds.</mark>\
All of this could not happen if it wasn't for the **local and private nodes** that we are hosting, which require beefy and costly machines that run **24/7** and are not shared with anyone else.\
The backend exposes a feature rich **API** that is consulted by all the other tools in the suite, along with websockets that send live data when events happen (<mark style="color:$primary;">this API might become public at some point in the future!</mark>)

### Telegram

The data is process by all of the bots and then a tailored message is sent for each event, that being a swap, transfer, a mined block, a contract deploy, a contract verification, burn, and more.\
Each message has data that has been gathered from mostly **first party** and some third party services.\
Each one is sent to the appropriate **VIP** (gate kept) topic or group.


---

# 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://cerbero-tools.gitbook.io/home/welcome-to-cerbero-tools/the-how.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.