> 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.**

Launches are indexed by a dedicated Ponder indexer so you can browse without scanning the explorer manually.

## Surfaces

| Path                  | Purpose                                                    |
| --------------------- | ---------------------------------------------------------- |
| `/launch/explore`     | Indexed list of launched tokens                            |
| `/launch/t/[address]` | Token detail: vesting, escrow, sales, AMM, journey updates |

These routes are URL-only on the product site (not linked from main marketing nav). Docs are the public entry path.

## What the indexer sees

* Factory launch events across factory versions (including paused v1-v3 tokens)
* Vesting creation
* Related escrow, updates, sale, and AMM activity as implemented

If the indexer is offline, explore pages degrade gracefully. On-chain truth remains on the [explorer](https://explorer.testnet.chain.robinhood.com).

## Related

* [Journey updates](/token-launch/journey-updates.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 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.canhav.com/token-launch/explore-tokens.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.