# Quick start for token launcher developers

This page outlines the minimal steps to integrate with Flap for token launcher developers. Each step links to the detailed documentation.

1. **Find the `Portal` entrypoint.** Use the deployed addresses listed in [Deployed Contract Addresses](/flap/developers/token-launcher-developers/deployed-contract-addresses.md).
2. **Launch a token through `Portal`.** `Portal` is the core protocol for launching standard tokens and tax tokens. See [Portal vs VaultPortal](/flap/developers/basic-and-mechanism/portal-vs-vaultportal.md) for the conceptual difference, then follow [Launch token through Portal](/flap/developers/token-launcher-developers/launch-token-through-portal.md) for the implementation details.
3. **Launch a token through `VaultPortal` (tax tokens with vaults).** `VaultPortal` builds on top of `Portal` to add Vault functionality for tax tokens. Follow [Launch token through VaultPortal](/flap/developers/token-launcher-developers/launch-token-through-vaultportal.md). Each vault factory defines its own vault data schema—see [Registered vaults](/flap/developers/token-launcher-developers/registered-vaults.md) before encoding `vaultData`.


---

# Agent Instructions: 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:

```
GET https://docs.flap.sh/flap/developers/token-launcher-developers/quick-start-token-launcher-developers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.