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

# Structuring

To make RayBot work for you — and not the other way around — it’s important to properly organize the process and bring order to the data you’re tracking.

One of the simplest ways to do this is to structure your wallets by assigning them to different bots within RayBot.

For example, you can set up:

* a dedicated Multi Buy bot for the Solana (SOL) network, adding only wallets related to Solana,
* a separate Multi Buy bot for the EVM ecosystem, including only EVM wallets,
* and a specialized bot for monitoring top traders’ transactions.

This approach helps you separate the “crowd” from the top wallets. You can monitor everything if you want, but that quickly turns your feed into pure noise where it’s hard to catch truly valuable signals.

Organizing wallets this way keeps your feed focused on the signals that matter to you.


---

# 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.raybot.app/start/use-cases/use-cases/structuring.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.
