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

# Gems

**Gems is the curated end of Research — high-signal candidates by GraphDex terminal metrics, in tight windows only.**

<div align="center"><figure><img src="/files/dh5jftRzDL6XdZlr6N3A" alt="Research — Gems table"><figcaption><p>Research — Gems tab, high-signal candidates in tight windows.</p></figcaption></figure></div>

Gems narrows the Solana token universe to pairs that already prove themselves on the metrics GraphDex considers signal. The selection algorithm isn't documented in the UI — treat the tab as an opinionated shortlist, not a curated buy list. It surfaces activity that *looks* like signal; it doesn't promise that any specific row is safe or profitable.

The column set matches the rest of Research, with one extra: a **1H** movement column. Time windows are tight by design — Gems lives at the short end of the horizon.

{% hint style="success" %}
**Short windows, sharper shortlist**

Use Gems when you want fewer rows that move on better metrics, then confirm on the token page before trading.
{% endhint %}

## TIME WINDOWS

Gems supports four short windows — by design, there's no 6h or 24h option here.

* **1m**
* **5m**
* **30m**
* **1h**

Use shorter windows for very recent activity, and the 1h window for a slightly broader view of pairs that continue to stand out.

## WHAT THE TABLE SHOWS

* **Pair** — token symbol and paired asset.
* **Market Cap** — current MC at the time of view.
* **Live Liquidity** — pool depth right now.
* **TXNS** — total transaction count with buy / sell split.
* **Volume** — trade volume for the row over the active window.
* **1H** — price movement over the last hour.
* **Audit** — contract-level risk markers; rows may surface percentage-based signals in the audit area.
* Audit percentages are risk and activity indicators — **not** approval labels.

## HOW TO READ GEMS

Gems is the place to read more carefully, not less — fewer rows means each one carries more weight.

* Compare **Market Cap** against **Live Liquidity** — a high MC backed by thin liquidity is volatility, not strength.
* Confirm **TXNS** is matched by meaningful **Volume**.
* Read the **buy / sell** split on TXNS — one-sided activity in tight windows is a flag.
* Check **1H** movement against the window you've picked — does the row's narrative match its motion?
* Read **Audit** and any holder-related percentages before opening the row in Trading.
* Open the [Token Page](/graphdex-docs/trading/token-page.md) before placing an order — every time.

## LIMITS OF GEMS

The UI doesn't expose the full selection algorithm, and the tab is not a curated list of "safe" tokens.

* Gems surfaces candidates that *stand out* by terminal metrics.
* It doesn't explain why any specific row was selected.
* It doesn't replace your own review on the token page.
* It doesn't override audit or holder warnings — those still apply.

{% hint style="warning" %}
A Gems row is a hint, not a recommendation. Always confirm on the [Token Page](/graphdex-docs/trading/token-page.md), check [Audit Signals](/graphdex-docs/research/audit-signals.md), and review [Trading Settings](/graphdex-docs/trading/trading-settings-overview.md) before sending an order.
{% endhint %}

## FAQs

<details>

<summary>What time windows does Gems support?</summary>

**1m, 5m, 30m, 1h.** No 6h or 24h — Gems is the short-window surface.

</details>

<details>

<summary>How is Gems selected?</summary>

By GraphDex terminal metrics. The full algorithm isn't exposed in the UI — read the tab as an opinionated shortlist, not a curated buy list.

</details>

<details>

<summary>What do the audit percentages mean?</summary>

They're risk and activity indicators surfaced inline on the row. Treat them as a glance signal, not an approval — open the token page for the full audit context. See [Audit Signals](/graphdex-docs/research/audit-signals.md).

</details>

<details>

<summary>How is Gems different from New and Trends?</summary>

* **New** — as-it-happens feed, no time window.
* **Trends** — sustained activity across six time windows.
* **Gems** — high-signal candidates in four tight windows.

See [Research Overview](/graphdex-docs/research/research-overview.md) for the full comparison.

</details>

<details>

<summary>Is a Gems row a buy signal?</summary>

No. Gems is curated discovery, not a recommendation. Confirm metrics, audit, and your Trading Settings before placing an order.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/research/gems.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.
