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

# Discover & signals

## Discover & signals

### Discover (home page)

The home page at [zardoz.fun](https://zardoz.fun) is the live token board for Robinhood Chain.

#### What each card shows

When enrichment has landed, cards display real **name, symbol, logo, price, mcap, liquidity, volume, age**, and **launchpad badge** (Zardoz, NOXA, Flap, Bankr, trench, Bags, Klik, …).

Cards stay in loading or partial state until real data arrives — no fake tickers or placeholder metrics.

#### Filters & sorting

| Control          | Effect                                                            |
| ---------------- | ----------------------------------------------------------------- |
| Pad filter       | Show only tokens from selected launchpad                          |
| Mcap / liq / vol | Minimum thresholds                                                |
| Age              | New pairs vs older                                                |
| Sort             | Last trade, volume, mcap, created time (`GET /api/tokens?sort=…`) |

#### Data sources

| Layer          | Source                                                |
| -------------- | ----------------------------------------------------- |
| Zardoz Instant | On-chain `TokenCreated` + `lib/data/zardoz-index.ts`  |
| External pads  | Factory allowlist in `lib/launchpads.ts` + pad APIs   |
| Market metrics | DexScreener, GeckoTerminal, Blockscout                |
| Live refresh   | Client + server aggregation in `lib/data/discover.ts` |

Open any card → full token page.

***

### Signals

[/signals](https://zardoz.fun/signals) surfaces actionable on-chain activity:

| Signal type      | Description                                              |
| ---------------- | -------------------------------------------------------- |
| **Cluster buys** | Multiple wallets buying the same token in a short window |
| **Heat**         | Volume / trade-count spikes vs baseline                  |
| **New pools**    | Fresh liquidity on Robinhood Chain                       |
| **Watched buys** | Trades from wallets in the /watch directory              |

#### API

```
GET https://zardoz.fun/api/signals?network=mainnet
GET https://zardoz.fun/api/signals/clusters?network=mainnet
```

`/api/signals/clusters` returns grouped wallet clusters with overlap scores for tokens held in common.

***

### Watch directory

[/watch](https://zardoz.fun/watch) — curated KOL and smart-wallet list.

```
GET /api/watch/wallets?q=vitalik&kind=smart
GET /api/watch/activity?limit=80&wallets=0xabc…,0xdef…
```

| Param     | Values                                            |
| --------- | ------------------------------------------------- |
| `q`       | Substring search on label / address               |
| `kind`    | `kol`, `smart`, `both`, or omit for all           |
| `wallets` | Comma-separated extra addresses for activity feed |

***

### Due diligence checklist

Before sizing a trade:

1. Confirm **launchpad** badge matches expectations
2. Check **holder concentration** on token page
3. Read **liquidity depth** and pool fee tier
4. Verify **contract** on [Blockscout](https://robinhoodchain.blockscout.com)
5. Cross-check price on chart vs DEX quote

Listings are aggregated best-effort — Zardoz does not audit token contracts.

Next: Trading · HTTP APIs


---

# 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://zardoz.gitbook.io/zardoz-docs-1/discover-and-signals.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.