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

# Browsing and discovering tokens

The homepage is the browse surface for every token the platform has launched.

![The token grid](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-51850800700b0fadcef969b315bb2e6425585fe3%2Fhome-grid.png?alt=media)

## Sorting and filtering

| Control     | Options                                                                         |
| ----------- | ------------------------------------------------------------------------------- |
| Search      | Name, ticker, or contract address                                               |
| Sort        | Market cap, Newest, 24h volume                                                  |
| Paired with | All, xStocks, PreStocks, Tessera, Sunrise, Currencies, Leverage, Solana, Custom |

Each card shows the token's symbol and name, its market cap in USD, what it is paired with, its category badge, 24h volume, and 24h price change.

## Where the numbers come from

Market data on StonkFun is read from the chain rather than scraped. Current price, supply and market cap come from the Raydium pool accounts the platform created, with the quote token's price converted into USD. Volume and 24h price change come from the platform's own trade records: every swap on every platform pool is decoded from that pool's own events and reconciled against the pool's vaults.

Only three things are stored rather than read live, because the chain cannot answer them: when the platform first indexed a pool, its peak market cap, and the graduation event.

## Live updates

Each open tab subscribes to the platform's pools directly and ticks market caps in near real time, falling back to polling where that is unavailable.

## The token page

![Token page header and metrics](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-8d8f99a8f32b80c7cb9380cabefc89b7845aaec0%2Ftoken-header.png?alt=media)

A token page carries:

| Section      | Contents                                                                               |
| ------------ | -------------------------------------------------------------------------------------- |
| Header       | Logo, name, symbol, mint address, socials, launchpad badge                             |
| Metrics      | Market cap, price, 24h volume, liquidity, holder count                                 |
| Chart        | Candles built from the platform's own trade records                                    |
| Checklist    | Mint authority revoked, freeze authority revoked, liquidity locked, metadata immutable |
| Transactions | Live swap feed with trader tagging for the dev wallet and the pool                     |
| Holders      | Ranked holder table with tags and top-holder concentration                             |
| Swap         | Embedded Jupiter widget, or a link out to jup.ag                                       |
| Creator fees | On a standard launch, the claim panel for whoever holds the Fee Key                    |
| Rewards      | On a reward coin, distribution totals for holders                                      |

![Ranked holder table](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-adca0f96533bcfd16e1bdc5a6184af487bea73cd%2Ftoken-holders.png?alt=media)

The right rail carries the swap widget, the token's Ecosystem Flywheel status, its platform-burn and buyback totals, and the mint, pool and quote addresses.

![Token page side panels](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-a020647cebd7c33684b55a2959d801dff3687bd9%2Ftoken-panels.png?alt=media)

## Graduation status

Tokens carry one of three statuses, driven purely by market cap:

| Status            | Threshold                          |
| ----------------- | ---------------------------------- |
| New               | Below `$32,000`                    |
| About to graduate | `$32,000` and above                |
| Graduated         | `$40,000` and above, and permanent |

Graduation never regresses. Once a token has touched `$40,000` it stays graduated even if the market cap later falls. See [Graduation](/stonkfun-docs/core-concepts/graduation.md).

## Platform-wide dashboards

| Page                                                 | What it shows                                                    |
| ---------------------------------------------------- | ---------------------------------------------------------------- |
| [`/revenue`](https://www.stonkfun.xyz/revenue)       | Traded volume, platform revenue, buybacks, `$STONK` burned       |
| [`/rewards`](https://www.stonkfun.xyz/rewards)       | Lifetime holder payouts per reward coin and recent distributions |
| [`/flywheel`](https://www.stonkfun.xyz/flywheel)     | The current buyback rankings and recent ecosystem burns          |
| [`/developers`](https://www.stonkfun.xyz/developers) | The public API reference                                         |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stonkfun.gitbook.io/stonkfun-docs/getting-started/browsing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
