> For the complete documentation index, see [llms.txt](https://docs.neuriio.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neuriio.xyz/get-started/launch-an-ftf.md).

# Launch an FTF

An **FTF** ("Friends Turned Fam") is one token launched by **exactly four people** together. It trades on the same [bonding curve](/get-started/bonding-curve.md) as a personal token, and its creator fees are split equally between the four members.

## How it works

1. **The founder creates the FTF** on the Launch page: a name and a ticker (2–10 letters or numbers, unique among FTFs).
2. **The founder invites three members.** Each member accepts the invite from their notifications.
3. **The founder sets the details**: a category, a profile and an optional picture.
4. **Launch.** All four members are fixed on-chain at launch and can't be changed later.

## Rules

* Exactly four members, founder included, each with their own X account.
* Being in an FTF doesn't use up anyone's personal launch, and one person can be in more than one FTF.
* Creator fees from the FTF's trades are split **25% to each member**. Each member claims their own share. See [Creator fees](/trading/creator-fees.md).
* FTFs follow the same [creator rules](/trust/creator-rules.md) as personal tokens.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neuriio.xyz/get-started/launch-an-ftf.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 `build a script that syncs our docs to a CMS` 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.