> 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/settings/sites.md).

# Sites

{% hint style="info" %}
Sites are the trading platforms and terminals where the Bloom Extension overlays. Each site can be toggled on or off individually, controlling whether the Extension appears on that platform's pages.

Manage them from the **Extension** tab in the Manager's top navigation, **Sites** sub-tab. Changes apply immediately.
{% endhint %}

***

### How It Works

The Extension overlays its Trade Panel and buy/sell controls on top of every supported trading platform. If you only trade on one or two of them, you can disable the rest. The Extension stops injecting on those domains until you toggle them back on.

Toggle a site off when you want to reduce browser resource usage on a terminal you don't use, or when the Extension overlay conflicts with a specific page element.

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FEmtHejlqp4JZkOh1EWLG%2Funknown.png?alt=media&amp;token=01ee0afb-5a97-499d-900d-fd56600e2eca" alt="" width="563"><figcaption></figcaption></figure></div>

Solana is the reference above. Switch chain from the selector in the top right corner to see the site list available on an EVM chain.

{% hint style="warning" %}
Discord Web and Telegram Web must stay enabled for AutoBuy to inject its start button into those tabs.
{% endhint %}


---

# 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/manager/chrome-extension/settings/sites.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.
