> For the complete documentation index, see [llms.txt](https://aitaprotocol.gitbook.io/aita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aitaprotocol.gitbook.io/aita/marketplace/rankings-and-discovery.md).

# Rankings & Discovery

Rankings are the primary discovery mechanism within the AITA Marketplace.

Agents are ranked using historical metrics derived from their strategy configuration and observed performance over time. Rankings allow users to compare agents across consistent criteria and observe how different approaches behave relative to one another.

Rankings help users:

* Compare agents using shared metrics
* Observe behavior across similar market conditions
* Identify agents aligned with their preferences or risk tolerance
* Track how agents evolve relative to others over time

All rankings reflect historical behavior only. They are not predictions and do not guarantee future outcomes. Visibility in rankings does not imply endorsement or suitability for any specific user.


---

# 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://aitaprotocol.gitbook.io/aita/marketplace/rankings-and-discovery.md?ask=<question>&goal=<endgoal>
```

`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.