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

# What Is Flaunch?

Flaunch is a protocol for launching tokens and routing the value they generate after launch.

It is built around three core mechanics:

1. Trading fees can be allocated to the creator.
2. Creator revenue is paid in ETH.
3. The rights to that revenue are represented by an NFT that can be held, transferred, or managed by another contract.

This means a Flaunch token is not only a token launch. It is also a revenue position that can be used by creators, launchpads, and treasury products.

## What Flaunch Does

When a token is launched on Flaunch, the creator can define:

* The Token Metadata
* The Starting Market Cap
* The Fair Launch Supply And Duration
* The Creator Revenue Allocation
* The Launch Time
* Whether Revenue Should Flow To A Wallet Or A Manager

After launch, fees continue to flow according to those settings.

## What Else It Enables

* Fixed-Price Fair Launches That Remove Early Price Risk
* Auto Buybacks That Follow The Price Upward
* Transferable Revenue Rights That Can Move To Better Stewards
* Community-Owned Structures Built Around Shared Fee Flows

## Why Builders Use It

Flaunch gives builders more than a token launcher.

It can be used to:

* Launch Tokens Quickly
* Build Launchpads On Top Of The API Or SDK
* Route Revenue Into Treasury Managers
* Build Products Around Tokenized Revenue Rights

## Continue Reading

{% content-ref url="/pages/ktCvruUTVUKV5eFyfc7x" %}
[Launch a Token](https://docs.flaunch.gg/getting-started/flaunch-a-coin.md)
{% endcontent-ref %}

{% content-ref url="/pages/KKanSI9loqloPkqKzc2C" %}
[Build a Launchpad](https://docs.flaunch.gg/getting-started/launch-a-launchpad.md)
{% endcontent-ref %}


---

# 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.flaunch.gg/getting-started/why-flaunch.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.
