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

# Token Page

The token page is where a user inspects one token in detail.

It combines market data, chart context, technical levels, holder data when available, and the latest operator read.

## Key Areas

* Token identity and social links
* Price, market cap, liquidity, and volume
* Chart and technical levels
* Latest operator read
* Holder and wallet context when available
* Watchlist controls

## Suggested Workflow

1. Check market cap, liquidity, and volume first.
2. Read the operator read before staring at the chart.
3. Review the chart levels and current price location.
4. Check holder or wallet context if available.
5. Decide whether the token deserves continued attention.

The token page should stay focused and readable. Backend packet details should be distilled into the operator read unless the user opens deeper packet or audit views.


---

# 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://dopameme.gitbook.io/docs/using-dopameme/token-page.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.