> For the complete documentation index, see [llms.txt](https://docs.liquidus.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquidus.finance/liquidus-wallet-app/wallet-basics/the-side-menu-and-what-to-do-there/import-a-custom-token.md).

# Import a custom token

1. Liquidus comes with many tokens whitelisted. These tokens have their respective token logo and the price in USD is tracked.
2. To add other tokens, open the side menu and click “Add Custom Token”.
3. Please note, that anyone can create fake tokens. Always double-check the token address you want to import and check on pages like “CoinGecko” to confirm the token address. 
4. On the “Import Token” page, enter the token contract address. It will read the information such as token name, symbol, and decimals. 
5. If all looks good, click “Import” to add the token to Liqudius. Note that custom imported tokens have a standard grey “LIQ” token logo and their USD price is not tracked. 
6. To remove a custom-added token, from the “Wallet” page, click on the token. On the token page, click on the red bin icon to remove the token.


---

# 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.liquidus.finance/liquidus-wallet-app/wallet-basics/the-side-menu-and-what-to-do-there/import-a-custom-token.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.