> For the complete documentation index, see [llms.txt](https://docs.definitive.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.definitive.fi/users/guides/hiding-assets-or-marking-as-spam.md).
# Hiding Assets or Marking as Spam
Your Definitive Vault operates entirely on-chain. This allows you to receive legitimate airdrops—but it also means you may occasionally receive unwanted or spam tokens.
Most of these are automatically filtered using the **“Hide Dust & Spam”** feature. However, some airdrops may appear valuable at first due to artificially inflated prices caused by low or nonexistent liquidity. These may not be filtered automatically, but are easy to remove manually.
**Desktop**\
Click the three-dot menu next to the token and select **“Mark as Spam.”** This will remove the token from your interface and exclude its value from your portfolio.
**Mobile**\
On the home page, press and hold the asset. It will bring up the options for it and select **“Mark as Spam.”** This will remove the token from your interface and exclude its value from your portfolio.
---
# 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.definitive.fi/users/guides/hiding-assets-or-marking-as-spam.md?ask=&goal=
```
`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.