> For the complete documentation index, see [llms.txt](https://credia-layer.gitbook.io/credialayer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://credia-layer.gitbook.io/credialayer/product-service/real-time-rankings.md).

# Real-Time Rankings

Within the Credia Layer ecosystem, real-time rankings cut through noise by aggregating social signals, on-chain activity, and market data.\
Instead of endless dashboards, users can see clear and dynamic rankings of tokens, projects, and narratives — highlighting what truly matters in the Web3 market.

By surfacing the strongest signals in real time, Credia Layer enables traders and analysts to identify opportunities early, anticipate market shifts, and act with confidence.

**Core Value**

* **Clarity:** Filter noise into transparent and actionable rankings.
* **Speed:** Track trending assets and narratives as they emerge.
* **Strategy:** Turn rankings into tradeable insights for smarter decision-making.


---

# 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://credia-layer.gitbook.io/credialayer/product-service/real-time-rankings.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.