# Exchange Listing

Token listings are managed in [this repository](https://github.com/balancer-labs/assets), with the following categories:

* `eligible.json`: assets that were eligible for liquidity mining in Balancer V1
* `listed.json`: assets listed on balancer.exchange
* `ui-not-eligible.json`: assets vetted by community members
* `untrusted.json`: assets that are incompatible with Balancer

Note that you can always create a pool or trade with an "unlisted" token, using the token address. You just can't search by token name, and the UIs will display a warning when interacting with "custom" tokens. (Needless to say, do your own research when using such tokens!)

There are two kinds of token "listings" on Balancer. The first is listing on the [Exchange](https://balancer.exchange/#/swap). Listed tokens appear on the main page as swapping options. It is possible to access unlisted pairs through a "deep link" with their addresses (balancer.exchange/#/swap/\<address1>/\<address2>), but it displays unlisted tokens as addresses, and with a warning.

There is no formal process for listing tokens on the Balancer exchange UI. That is up to the team's discretion and relies on internal factors around trading volume, usage, and legitimacy. (As noted above, it's always possible to trade tokens via contract address.)

The listing criteria below are taken from this [accepted proposal](https://forum.balancer.finance/t/proposal-to-update-the-whitelist-process/217/4). (We will endeavor to keep this up-to-date, but see the [Balancer Forum](https://forum.balancer.finance/) for the very latest.)


---

# Agent Instructions: 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:

```
GET https://balancer.gitbook.io/balancer-v2/v1/core-concepts/bal-liquidity-mining/exchange-and-reward-listing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.