> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/blockchain/build/launch-dapps-on-iotex/submit-tokens-to-the-iotex-ecosystem.md). # Submit Tokens to the IoTeX Ecosystem If you already [deployed a token on the IoTeX blockchain](/blockchain/build/defi/deploy-tokens.md), and you want it to show up into IoTeX ecosystem tools such as the [block explorer](https://iotexscan.io/) and the official [ioPay wallets](https://iotex.io/iopay), then you can **register your token metadata** into the ecosystem using the link below: {% embed url="" %} After your submission is accepted, your token metadata will show up in the IoTeX explorer at :

and in the official [ioPay wallet apps](https://iotex.io/iopay):

Your Dapp, as well as any other ecosystem tool like [iotube](https://iotube.org/) bridge or [mimo](https://mimo.finance/) DEX, can also [fetch the metadata](https://github.com/iotexproject/iotex-token-metadata#usage) and use it in their frontends. --- # 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.iotex.io/blockchain/build/launch-dapps-on-iotex/submit-tokens-to-the-iotex-ecosystem.md?ask=&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.