> 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/pulse/from-signal-to-research.md).

# From Signal to Research

**Pulse points at a token. Research tells you whether it's worth a second look.**

<div align="center"><figure><img src="/files/8lUlmsCcRJFqsPsTLnjB" alt="From Pulse cards into Research tables"><figcaption><p>A Pulse card is the start of a flow; Research is the next stop.</p></figcaption></figure></div>

Pulse compresses fast lifecycle and activity signals into scannable cards. **Research** widens the view — table-based comparisons across New, Trends, and Gems, with the same token shown next to its peers.

Use Pulse to surface candidates. Use Research to test them.

{% hint style="success" %}
**Two-screen rhythm**

Scan in Pulse → verify in Research → decide in Trading. Skipping the middle step is where most rushed trades come from.
{% endhint %}

## Suggested Flow

1. Find a token in **Pulse**.
2. Note the **token name, pair, or address**.
3. Open **Research**.
4. Check whether the token appears in **New**, **Trends**, or **Gems**.
5. Compare **Market Cap**, **Live Liquidity**, **TXNS**, **Volume**, **1H movement**, and **Audit signals**.
6. Apply filters to narrow related tokens if needed.

## Why Research After Pulse

Pulse is a stream — token activity over a short window. Research is a table — peer comparisons within the same discovery context.

* [**New**](/graphdex-docs/research/new-tokens.md) — compare fresh token pairs side-by-side instead of one at a time.
* [**Trends**](/graphdex-docs/research/trends.md) — compare recent activity within selected time windows.
* [**Gems**](/graphdex-docs/research/gems.md) — review tokens that stand out by terminal metrics, not just by Pulse cadence.

A Pulse card answers *"is this happening right now?"*. Research answers *"how does it look against everything else happening right now?"*.

## When to Stop

If Research surfaces any of the following, **do not continue into a trade** without deeper review:

* Weak liquidity (low LIQ relative to MC).
* Suspicious audit signals (concentrated holders, bundled supply, insider activity).
* Low transaction count or thin volume.
* Inconsistent volume vs. price action.

Stopping a flow at Research is a feature, not a failure. The cheapest trade is the one you didn't take.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/mbUy3xsH1kNAopC6jTrw"><strong>Reading Signals</strong></a></td><td>The Pulse card field guide.</td><td><a href="/files/8lUlmsCcRJFqsPsTLnjB">/files/8lUlmsCcRJFqsPsTLnjB</a></td></tr><tr><td><a href="/pages/u7WCycdkf5le4FRMndCn"><strong>Research Overview</strong></a></td><td>The hub for the second step in the flow.</td><td><a href="/files/JBN29ujDJykAmMONwLxK">/files/JBN29ujDJykAmMONwLxK</a></td></tr><tr><td><a href="/pages/AVc6N5MIhAcmqbV8qsf1"><strong>From Signal to Trade</strong></a></td><td>What happens after Research clears a token.</td><td><a href="/files/8lUlmsCcRJFqsPsTLnjB">/files/8lUlmsCcRJFqsPsTLnjB</a></td></tr></tbody></table>

{% hint style="info" %}
Once Research clears a token, the next stop is [From Signal to Trade](/graphdex-docs/pulse/from-signal-to-trade.md) — the pre-flight before any order goes out.
{% endhint %}

## FAQs

<details>

<summary>Do I have to use Research before trading from Pulse?</summary>

Not technically — Pulse cards include a \`Buy 0.01\` shortcut. But skipping Research is how most bad trades start. Two screens, two minutes; almost always worth it.

</details>

<details>

<summary>What if the token isn't in New / Trends / Gems?</summary>

That itself is signal. Tokens that surface in Pulse but don't qualify for any Research bucket are usually fresher, smaller, or thinner than the comparison tables include. Investigate manually on the token page.

</details>

<details>

<summary>How long should the Pulse → Research step take?</summary>

30–90 seconds. You're scanning, not auditing. The full audit happens on the \[token page]\(../trading/token-page.md) after Research clears.

</details>

<details>

<summary>Which Research view should I open first?</summary>

Match the Pulse lane. New lane → \[Research/New]\(../research/new-tokens.md). Migrated lane → \[Research/Trends]\(../research/trends.md). Quality signal → \[Research/Gems]\(../research/gems.md).

</details>

<details>

<summary>Can I jump from Pulse directly to Trading?</summary>

Yes — the card exposes a shortcut. But the \[From Signal to Trade]\(from-signal-to-trade.md) checklist still applies. Speed doesn't substitute for review.

</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/pulse/from-signal-to-research.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.