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

# Overview

#### What is CoinRotator?

CoinRotator is a cryptocurrency market scanner that analyzes trend patterns across 3,000+ digital assets. The platform provides daily trend signals (**UP, DOWN, HODL**) based on relative performance against BTC, ETH, and USDT, with new data sources being added with each upgrade.

<figure><img src="/files/zlGZsTT6hBUVFqGERCa1" alt="" width="375"><figcaption></figcaption></figure>

How CoinRotator Works

CoinRotator tracks over 3,000 cryptocurrencies across multiple data sources, with each coin assigned a trend status that updates daily at 01:00 UTC.

<figure><img src="/files/Ev6sMxniGN1viD01G4G2" alt="" width="375"><figcaption></figcaption></figure>

The determination of these trends is based on each coin's relative performance delta compared to BTC, ETH, and USDT:

* **UP**: Outperforming BTC, ETH, and USDT
* **DOWN**: Underperforming the three reference assets
* **HODL**: Mixed signals indicating inconclusive market direction, often occurring when BTC or ETH dominance impacts altcoin performance

<br>

<br>


---

# 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://coinrotator.gitbook.io/coinrotator-docs/overview.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.