> 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/manager/chrome-extension/scrapers.md).

# Scrapers

{% hint style="info" %}
AutoBuy is the Extension's scraper: it watches a Discord or Telegram Web tab in your browser and fires a buy the moment a contract address is posted in the target channel. No manual click required.

Every AutoBuy trade uses the **Scrapers** configuration saved in the Manager: buy amount, fees, tip, and filters. Configure it once, then run AutoBuy on any channel.
{% endhint %}

***

### How AutoBuy Works

1. You configure the **Scrapers** section in the Manager (buy amount, filters, fees).
2. You open a supported channel tab (Discord or Telegram Web) in your browser and leave it active.
3. You press the AutoBuy button injected by Bloom into the channel.
4. The Extension continuously scans the DOM of that tab for contract addresses.
5. When a valid address appears, Bloom applies the Scrapers configuration of the selected chain and fires a buy.

***

### Supported Channels

| Channel      | Page             |
| ------------ | ---------------- |
| Discord Web  | Discord AutoBuy  |
| Telegram Web | Telegram AutoBuy |

Both channels share the same Scrapers configuration. On Solana the buy amount is set independently per channel (Discord Auto Buy Amount, Telegram Auto Buy Amount) while every other field applies to both.

***

### Scraper Configuration

The Scrapers section lives in the Manager under your account menu, **Settings**, **Extension**, **Scrapers**. It is chain-scoped: each chain keeps its own values, and the values applied are the ones saved for the chain you started AutoBuy on.

The full field reference is on the Settings page.

{% embed url="<https://www.youtube.com/watch?t=50s&v=wu2_MOtsbQU>" %}

***

### Filters

Filters are the gate that decides whether a detected contract address results in a buy. The Extension reads the token's current stats (liquidity, market cap) and compares them against your thresholds.

* If **any** filter fails, the buy is skipped and the scraper continues watching for the next address.
* If **all** filters pass, the buy fires using the configured buy amount, fees, tip, and slippage.

Set thresholds according to the strategy the channel follows. Tighter filters reduce noise but may skip short-lived opportunities.

***

### Rules and Limits

* **One channel tab per browser window.** AutoBuy disables itself if more than one Discord tab (or Telegram tab) is open in the same window. Use separate browser windows to run multiple channels in parallel.
* **The tab must stay open.** AutoBuy stops scanning when the tab is closed or the browser is quit. Minimizing the window is fine.
* **Active session only.** The "Skip contract if already bought" filter is scoped to the current channel session. It resets when the tab is closed or reloaded.
* **AutoBuy follows the selected chain.** The start button injected into the channel is the Solana one while Solana is selected, and the EVM one while an EVM chain is selected. The Scrapers configuration applied is the one saved for that chain.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.bloombot.app/manager/chrome-extension/scrapers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.