> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/omen-listed/overview.md). # Overview An overview of OMEN Listed, a planned token listing program for reviewing crypto projects and identifying tokens approved for listing on OMEN Utility. ### Overview OMEN Listed is a planned token listing program designed to help users discover projects reviewed for inclusion in the OMEN ecosystem. The program will provide a submission and review process for crypto projects seeking to be listed on OMEN Utility. Projects that pass the review process may receive an OMEN Listed badge to distinguish them from other assets on the platform. The goal is to make project information easier to identify while establishing a consistent process for evaluating listing requests. ### How It Works OMEN Listed is intended to follow three main steps: 1. **Project Submission :** A project submits its token for consideration through the designated submission process. 2. **Review :** The OMEN team evaluates the submission against the program requirements and review criteria. 3. **Listing Decision :** Projects approved through the review process may receive an OMEN Listed badge and be considered for listing on OMEN Utility. Submission does not guarantee approval. Listing decisions remain subject to the program requirements and review process. ### The OMEN Listed Badge The OMEN Listed badge is intended to identify tokens approved through the OMEN Listed review process. The badge will help users distinguish approved listings from other tokens displayed on the platform. However, the badge should not be interpreted as a guarantee of investment performance, token safety, liquidity, or future project success. Crypto assets carry risks, and users should conduct their own research before making financial decisions. ### Review Principles OMEN Listed aims to establish a consistent approach to reviewing projects. Review considerations may include: * Project and token information. * Transparency of publicly available information. * Token contract and network details. * Available market and liquidity information. * Other factors relevant to the listing requirements. The final review criteria and submission requirements will be published when the program is formally introduced. ### Current Status OMEN Listed is part of the planned OMEN Protocol ecosystem. Submission availability, review requirements, listing decisions, and badge issuance will be confirmed through official OMEN Protocol announcements. Until the program is officially launched, this page describes the intended direction rather than an active submission service. ### Next Steps For details on the intended submission workflow, see **Submission & Review Process**. --- # 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://omen-protocol.gitbook.io/omen-protocol-docs/omen-listed/overview.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.