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

# Explore tokens

**Available now.**

The **Explore** tab (`/explore`) is the board of everything launched and published through CanHav, on both chains. A toggle switches it between two views.

## Views

| View                 | URL                      | What it lists                                                                                                                                                                                                               |
| -------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tokens (the default) | `/explore`               | Every token launched through CanHav, newest first. Each card shows the price and liquidity when a pool exists, or the curve price and graduation progress while the token is on its curve, plus the supply and launch date. |
| Projects             | `/explore?view=projects` | Every project published from the studio, newest first. A project needs no token to be listed. Published token designs are not on the board.                                                                                 |

A token card opens [the token page](/token-launch/token-page.md) at `/launch/t/[address]`. A project card opens its public page at `/p/[slug]`.

`/projects` redirects to the Projects view, and the old `/launch/explore` redirects to `/explore`.

## What the indexer sees

Launches are indexed by a Ponder indexer, one instance per chain, so you can browse without scanning an explorer.

* Launch events from the curve launcher and every factory version (including tokens from the paused v1 to v3 factories on Robinhood Chain Testnet)
* Curve creation, buys, sells and graduation
* Vesting creation
* Escrow, updates, sale, and AMM activity

Token transfers are not indexed, so there is no holders list.

If an indexer is offline, the board and token pages for that chain say so rather than failing. On-chain truth stays on the chain's explorer: [Robinhood Chain Testnet](https://explorer.testnet.chain.robinhood.com) or [Arbitrum Sepolia](https://arbitrum-sepolia.blockscout.com).

## Related

* [The token page](/token-launch/token-page.md)
* [Bonding curve](/token-launch/bonding-curve.md)
* [Public pages](/public-pages/public-pages.md)
* [Contract addresses](/token-launch/contract-addresses.md)
* [FAQ](/token-launch/faq.md)


---

# 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://docs.canhav.com/token-launch/explore-tokens.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.