> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-information.md).

# Token Information

Query token details, bonding curve progress and launch status.

### Get token information

Use `getTokenState` to query a token’s launch configuration, bonding curve data and graduation status.

```ts
const blockNumber = await publicClient.getBlockNumber();
const state = await client.getTokenState(token, { blockNumber });
```

The result includes:

* `state.record`: launch configuration, including the curve address, quote token and creator.
* `state.curveState`: current reserves, available tokens and graduation readiness.
* `state.graduation.status`: launch status — `notGraduated`, `swept`, `poolCreated` or `emergencyExited`.

`getCurveProgress` measures tokens sold as a share of `initialSupply - reservedTokens`. It reaches 100% when the sellable reserve is exhausted. Check graduation status to confirm that the AMM pool is ready.

### Validate a token

For user-supplied addresses, call `isLaunchToken` before reading token data. Registry getters return zero-filled values for unknown addresses.

```ts
if (!(await client.isLaunchToken(token))) throw new Error("not a launch token");
```

### Keep data up to date

* Use the same `blockNumber` for related reads so they reflect the same point in time.
* Refresh curve data before quoting and graduation status after a transaction confirms.
* Launch economics are fixed at creation. Creator fee recipients and buyback settings can change; refresh them after update events.

### Direct contract calls

SDK equivalents: getCurveAddress, getLaunchRecord and the configuration/state readers. These view calls need no allowance or wallet signature.

* `curveFor(address token) → address curve`: resolve the token's trading contract. A zero address means it is not registered here.
* `getLaunchedToken(address token) → LaunchedTokenRecord`: token, curve, creator, fee recipient, quote asset and immutable launch economics.
* `validateAndResolve(address quoteToken, uint256 launchConfigId) → (LaunchConfig, QuoteTokenEconomics)`: validate the selected quote asset and template.
* `canLaunch(address creator) → bool`: check the current launch gate. Also read `feePolicy()`, `snipeTaxConfig()`, `launchFeeToken()`, `launchFee()`, `maxCreatorTaxBps()` and `maxCreatorInitialBuyBps()` before creation.

Read configuration at one block. Existing curves retain their snapshots: use `feePolicySnapshot()`, `snipeTaxConfigSnapshot()` and the launch record when quoting an existing token.


---

# 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.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/token-information.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.
