> 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-trade.md).

# From Signal to Trade

**A Pulse card and a Buy button are not a trade plan — they're the start of one.**

<div align="center"><figure><img src="/files/8lUlmsCcRJFqsPsTLnjB" alt="From Pulse signal to a confirmed trade"><figcaption><p>Pulse cards expose a `Buy 0.01` shortcut — fast access is not the same as informed access.</p></figcaption></figure></div>

Pulse cards expose a `Buy 0.01` control for fast access from signal to order. Fast access is a tool — it's also the easiest way to act before you've finished thinking. This page is the pre-flight checklist between a Pulse signal and a confirmed trade.

{% hint style="warning" %}
**Speed is a setting, not a strategy**

A one-click Buy doesn't review the token, the wallet, or the settings. You do.
{% endhint %}

## The Pre-Trade Checklist

Before turning a Pulse signal into an order:

* **Token identity.** Confirm the ticker AND the contract address.
* **Card metrics.** Read MC, V, F, TX on the Pulse card.
* **Percentage signals.** Check any percentage values for risk markers (concentrated holders, bundled supply, etc.).
* **Token page.** Open the token in [Trading](/graphdex-docs/trading/token-page.md).
* **Liquidity profile.** Verify LIQ, MC, 5M Vol.
* **On-chain context.** Review Transactions, Top holders, Token details.
* **Audit signals.** Security, Dev Holders, Top 10 Holders, Sniped, Insiders, Bundled — see [Audit Signals](/graphdex-docs/research/audit-signals.md).
* **Trade Strategy.** Confirm [Slippage](/graphdex-docs/trading/slippage.md), [Priority Fee](/graphdex-docs/trading/priority-fee.md), [Validator Bribe](/graphdex-docs/trading/validator-bribe.md).

The whole flow takes 60–120 seconds. The trade that follows it is much more likely to be deliberate.

## Quick Buy Caution

`Buy 0.01` lives on the card for speed. That same speed makes it easy to act before reviewing the token fully.

* Use it **only after** the pre-trade checklist clears.
* Treat `Buy 0.01` as the *execution* step, not the *decision* step.
* If you're unsure about the token, the wallet, or the settings — **don't use it**. Use the standard Buy flow instead.

For the full coverage of what aggressive shortcuts can break, see [Risk of Fast Execution Settings](/graphdex-docs/trading/risk-of-fast-execution-settings.md).

## No Financial Advice

Pulse signals are market information — not recommendations. GraphDex surfaces what's happening; the decision to act is yours.

* You are responsible for every trade you place.
* Past activity is not a guarantee of future performance.
* Risk signals are inputs to your judgment, not substitutes for it.

## 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>Field guide for every value on a Pulse card.</td><td><a href="/files/8lUlmsCcRJFqsPsTLnjB">/files/8lUlmsCcRJFqsPsTLnjB</a></td></tr><tr><td><a href="/pages/auDxLb3GSIVsuY5RI0FC"><strong>From Signal to Research</strong></a></td><td>The step before this one — verifying the token in tables.</td><td><a href="/files/8lUlmsCcRJFqsPsTLnjB">/files/8lUlmsCcRJFqsPsTLnjB</a></td></tr><tr><td><a href="/pages/OMivUziEbyoA9jTgesYW"><strong>Risk of Fast Execution</strong></a></td><td>What goes wrong when Quick Buy meets Turbo.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
Pulse signals are the start of a flow — the end is a deliberate order placed inside [Trading](/graphdex-docs/trading/trading-overview.md).
{% endhint %}

## FAQs

<details>

<summary>Is `Buy 0.01` safer than the full Buy flow?</summary>

It's faster, not safer. The same risks apply — wrong token, wrong settings, wrong wallet. Run the pre-trade checklist either way.

</details>

<details>

<summary>What's the difference between Quick Buy and standard Buy?</summary>

Quick Buy submits with a single click using current Trading Settings. Standard Buy walks through the panel — direction, amount, mode, settings — with a second confirmation. Use standard Buy when reviewing time matters more than execution speed.

</details>

<details>

<summary>Can I trade directly from Pulse without opening Research?</summary>

You can. Whether you should depends on the signal strength and your familiarity with the token. New lane + unfamiliar ticker = open Research first.

</details>

<details>

<summary>What if the audit signals look mixed?</summary>

Mixed signals are also signal. If you can't articulate why the trade is worth the visible risk, the trade probably isn't worth it.

</details>

<details>

<summary>How small should my first trade on a new token be?</summary>

Position sizing is personal. A common pattern: a deliberately small first position to test execution and liquidity, then scale up only if both behave.

</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-trade.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.