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

# Welcome to Bloom

<div align="left"><figure><img src="https://3158159183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAZVSZEL47N9f4qOtz3Wz%2Fuploads%2FoGRPP59SVvlGkh676euK%2FTwitter_header_-_7_0-00-02-01.png?alt=media&amp;token=9a7075c4-40df-4b5c-b2c1-8949cd3d9110" alt="Bloom welcome image."><figcaption></figcaption></figure></div>

{% hint style="info" %}
Bloom is a trading product for new and experienced traders, with a web Manager, a Chrome Extension and a Telegram Bot.
{% endhint %}

## Why Bloom

* Trade faster on Bloom's optimized, fully rebuilt infrastructure.
* Combine web-based and Telegram tools.
* Switch from desktop to mobile trading, anywhere and anytime, through Bloom Manager, Chrome Extension and Telegram Bot.
* Trade multi-chain on Solana, Ethereum, BSC, Base, Robinhood, Arc, HyperEVM and Ink.

## The Ecosystem

Bloom Manager is the web [dashboard](https://manager.bloombot.app/). It covers portfolio overview, task creation, wallet management, profit and loss (PnL) analytics, referral tracking and full configuration of every Bloom product.

The Chrome Extension sits on top of your trading terminal and adds one-click execution through the Quick Panel. You manage its settings in Bloom Manager.

The Telegram Bot handles mobile-first trading and automation. Spot trading, sniping, copy trading, AFK Mode, limit orders, Twitter automation, cross-chain bridging and more run directly from Telegram with no external tools required.

## Core Features

| Feature                      | Description                                            |
| ---------------------------- | ------------------------------------------------------ |
| **Spot Buy & Sell**          | Buys and sells instantly.                              |
| **Sniper**                   | Catches new token opportunities quickly.               |
| **Copy-Trading**             | Copies successful traders in real time.                |
| **AFK Mode**                 | Automates your trading while you are away.             |
| **Twitter/X Mode & Tracker** | Automates buying, selling and strategies on Twitter/X. |
| **Chrome Extension**         | Adds advanced tools to your trading terminal.          |
| **Multiple Limit Orders**    | Places multiple limit orders for your strategies.      |
| **In-Bot Bridge**            | Bridges tokens between blockchains within the bot.     |
| **Advanced Settings**        | Customizes your trading experience.                    |

## Rewards & Benefits

Every trade generates cashback. A three-level referral program adds passive income.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloombot.app/welcome-to-bloom.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
