> For the complete documentation index, see [llms.txt](https://doc.suprage.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.suprage.app/getting-started/what-is-suprage.md).

# What is Suprage?

**Suprage** is a web-based **Market Intelligence Terminal** for the [Supra](https://supra.com) blockchain. It aggregates on-chain trading data from the [Atmos](https://atmos.ag) DEX, computes live signals and a market-sentiment index, and wraps everything in a fast, cyberpunk-styled dashboard.

It is also the home of the **$RAGE** token economy: your $RAGE balance determines your **tier**, which unlocks progressively deeper analytics across the terminal.

## Who it's for

* **Supra traders** who want a single screen for live prices, momentum, swap flow, and market sentiment.
* **$RAGE holders** who want to unlock premium analytics and climb the leaderboard.

## What it does

| Capability                                                      | Where                                                       |
| --------------------------------------------------------------- | ----------------------------------------------------------- |
| Live token prices & multi-timeframe momentum (15m → 24h)        | [Market Board](/user-guide/pages/market-board.md)           |
| Real-time swap feed from the chain                              | [Flow Radar](/user-guide/pages/flow-radar.md)               |
| Market sentiment score (0–100)                                  | [Rage Index](/user-guide/pages/rage-index.md)               |
| Notable market events                                           | [Market Radar](/user-guide/pages/market-radar.md)           |
| Top movers, bubble map, key metrics                             | [Dashboard](/user-guide/pages/dashboard.md)                 |
| TradingView-style OHLC charts (incl. pre-graduation pump phase) | [Market Board](/user-guide/pages/market-board.md)           |
| Holder ranking                                                  | [Leaderboard](/user-guide/pages/leaderboard.md)             |
| Real-time price feeds                                           | [Oracle Pulse](/user-guide/pages/oracle-pulse.md)           |
| Live network metrics                                            | [Network Analytics](/user-guide/pages/network-analytics.md) |

## What makes it different

* **Tier-gated depth.** Everyone sees the market. The more $RAGE you hold, the more granular the data becomes — shorter timeframes, signal columns, chart tools, and full Flow Radar filters. See [RAGE Tiers & Premium](/user-guide/rage-tiers-and-premium.md).
* **Real on-chain data.** Prices, swaps, and balances come straight from Supra and Atmos, not a third-party aggregator. Historical price charts include the pre-graduation "pump" phase of new tokens.
* **Always fresh.** Market data refreshes continuously, so what you see reflects the live state of the market.

Continue to [Core Concepts](/getting-started/core-concepts.md) to learn the vocabulary, or jump straight to the [Quick Start](/getting-started/quick-start.md).


---

# 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://doc.suprage.app/getting-started/what-is-suprage.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.