> 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/web-app/web/my-tokens.md).

# My Tokens

The **My Tokens** section gathers all tokens you’ve added across every Destination (Groups, RayBots, Discord channels, Dedicated bots) using the `/add TokenAddress` command.\
Everything is combined into one dashboard where you can manage, filter, and monitor all tracked tokens.

Here you can:

🎯 **Filter tokens** by Destination, Chain, Status, and Settings overrides.\
🔍 **Search tokens** by name or token address.\
🧩 **See where each token is tracked** (destination, bot, or group).\
📊 **Check last on-chain activity** for wallets interacting with this token.\
⚙️ **Edit settings, statuses, and alerts** for each token individually.\
🗑 **Delete or batch-manage tokens** using multi-select actions.

The dashboard works the same whether you track a few tokens or hundreds.

> *🎥 **Video example — Full walkthrough of the My Tokens dashboard in under 2 minutes***

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/qkqv8njh1p>" %}


---

# 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/web-app/web/my-tokens.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.