> For the complete documentation index, see [llms.txt](https://goattrading.gitbook.io/dojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://goattrading.gitbook.io/dojo/features/discovery.md). # Discovery Our token discovery does not only use the name of the token, but also includes searching in bios of tokens and searching images of tokens. We use AI to determine the contents of an image when a token is initially created, and users can receive search results based on that alone even if the search is not in the token name or bio. We also allow filtering and sorting of all tokens to be able to search based on specific creation dates, market caps, and volumes, and to sort based on prices, date, and more. Filtering will continue to be advanced with more and more variables. The AI search is still experimental and has little data to relate to, so there could be false positives to begin with and over time this will become more advanced. --- # 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://goattrading.gitbook.io/dojo/features/discovery.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.