> For the complete documentation index, see [llms.txt](https://docs.epsilon.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epsilon.exchange/products/explore.md).

# Explore & analytics

The Explore section turns Epsilon into a market research tool with real-time, on-chain data for Robinhood Chain.

## Tokens

Browse and search every token on the chain with price, volume, liquidity, and price-change metrics. Filter by exchange to focus on a specific venue.

## Token detail

Each token has a detail page with:

* Price chart (TradingView) with multiple timeframes.
* Pools and pairs you can trade against.
* Holders and top traders.
* Recent transactions.

You can trade directly from the token page: the swap form and order forms are right next to the chart.

## Pools

Inspect pools and pairs across Robinhood Chain's venues, including liquidity and volume, to understand where trading is happening.


---

# 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://docs.epsilon.exchange/products/explore.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.