> For the complete documentation index, see [llms.txt](https://fordex.gitbook.io/fordex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fordex.gitbook.io/fordex/market-screener/live-pairs-table.md).

# Live Pairs Table

## Live Pairs Table

The **Live Pairs Table** is the heart of Fordex. It shows real-time token activity across supported chains, allowing traders to identify trending tokens, hidden gems, or early risks.

#### **Displayed Metrics**

* **Pair** → Token/chain name, with quick link to the pair page.
* **Price** → Updated in real time via WebSocket.
* **24h Volume** → Total trading volume in the last 24 hours.
* **Liquidity (USD)** → Available liquidity in the pool.
* **FDV / MC** → Fully Diluted Valuation and Market Cap.
* **% Change** → Price changes at 5m, 1h, and 24h intervals.
* **Age** → How long the pair has existed since creation.

#### **User Controls**

* **Sortable columns** → Click column headers to sort ascending/descending.
* **Quick actions** → Pin, add to watchlist, or open pair page directly.

#### **Use Case**

* Find **new pairs <24h** before they trend.
* Identify **top movers** in real time.
* Spot liquidity injections or rug-pull warnings instantly.


---

# 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://fordex.gitbook.io/fordex/market-screener/live-pairs-table.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.