> For the complete documentation index, see [llms.txt](https://hello-fun-1.gitbook.io/hello.fun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello-fun-1.gitbook.io/hello.fun-docs/hello-intelligence/hello-pilot.md).

# HELLO Pilot

### Turn Ideas Into Launches

HELLO Pilot is the AI Launch Assistant for Hello.Fun.

It gives creators an optional AI assisted way to move from an idea toward a prepared token launch.

Instead of working through every part of the creation process alone, creators can use Pilot to help shape and prepare the launch before reviewing the final configuration.

The creator remains in control throughout the process.

### An Optional Way to Create

HELLO Pilot does not replace the standard Hello.Fun launch flow.

Creators can choose between:

* Creating their launch manually
* Using HELLO Pilot for AI assistance

Both routes ultimately lead to the same Hello.Fun launch process.

```mermaid
flowchart TD
    A["Token Idea"] --> B{"Choose Creation Route"}
    B -->|"Manual"| C["Prepare Launch Manually"]
    B -->|"HELLO Pilot"| D["AI Assisted Preparation"]
    C --> E["Review Launch"]
    D --> E
    E --> F["Approve With Wallet"]
    F --> G["Launch"]
```

Pilot changes how a creator can prepare for launch.

It does not remove the creator's final review or wallet approval.

### From Idea to Launch

HELLO Pilot is designed to make the beginning of the launch journey easier.

A creator can start with an idea and use Pilot to work through the information and configuration needed to prepare the token.

```mermaid
flowchart LR
    A["Idea"] --> B["HELLO Pilot"]
    B --> C["Prepare Launch"]
    C --> D["Review"]
    D --> E["Wallet Approval"]
    E --> F["Live Market"]
```

The goal is to reduce the distance between having an idea and being ready to launch it.

### Creator Control

HELLO Pilot assists with the creation process, but it does not take control of the creator's wallet.

Before launch, the creator can review the final configuration.

The launch transaction is then approved through the creator's connected wallet.

This keeps the creator at the center of the final decision.

### Review Before Launching

AI assistance does not remove the need to review a launch carefully.

Before approving the transaction, creators should confirm the final launch information and settings presented to them.

Once the launch transaction is executed, properties that are fixed at launch remain subject to the same Hello.Fun rules whether the launch was prepared manually or with HELLO Pilot.

### The Same Hello.Fun Market

A token prepared with HELLO Pilot does not enter a separate AI market.

Once launched, it follows the normal Hello.Fun market lifecycle.

```mermaid
flowchart LR
    A["HELLO Pilot"] --> B["Launch"]
    B --> C["Bonding Curve"]
    C --> D["Graduation"]
    D --> E["Uniswap v4"]
    E --> F["Open Market Trading"]
```

The same token structure, pairing system, bonding curve, graduation process and market rules apply.

HELLO Pilot assists with getting to the launch.

Hello.Fun handles what happens after it.

### Part of HELLO Intelligence

HELLO Pilot is the **CREATE** layer of HELLO Intelligence.

**CREATE → HELLO Pilot → Turn ideas into launches.**

It is the first step in a wider intelligence ecosystem designed around the full life of a token, from creation and discovery to analysis, monitoring and understanding.

### Create Your Way

Build it yourself or create with AI assistance.

Review the launch.

Approve it from your wallet.

Enter the market.

**Your idea. Your launch. Your call.**


---

# 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://hello-fun-1.gitbook.io/hello.fun-docs/hello-intelligence/hello-pilot.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.