> For the complete documentation index, see [llms.txt](https://docs.ordex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ordex.io/services/listing.md). # Listing All collections featured on ORDEX must apply for listing by providing the necessary json files and information related to your project.\ \ Listings can only occur when the collection has been fully ethscribed in order to create a json file which holds all metadata of the assets within the collection.\ \ This metadata will be used to verify which ethscriptions belong in the official collection to avoid any malicious activity or "copy cat" items from scams which may occur following a launch of a successful project.\ \ At ORDEX we also use this metadata to display any unique traits for items within the collection as well as rarity rankings which can be included within the json file.\ \ To apply for listing you can open a ticket in our Discord server or complete the following form.\ \ Apply here:\ --- # 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.ordex.io/services/listing.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.