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

# Home

## Welcome to Launchium Documentation

### Your Idea, Your Coin

Welcome to the official Launchium documentation. Here you'll find everything you need to know about launching your token on the world's first cross-platform social token launchpad.

#### Quick Start

* Launch your first token in 60 seconds
* Read the launch guide
* Join the presale

#### For Creators

* Getting Started - Launch your first token in 60 seconds
* Token Launch Guide - Detailed launch instructions
* FAQ - Common questions answered

#### For Developers

* API Documentation - Build on Launchium
* SDK & Integration - Libraries and tools
* Technical Architecture - How it works

#### For Investors

* LNCHM Token - Platform token details
* Presale System - Join the presale
* Roadmap - Future plans

#### Need Help?

* Contact Support - Get in touch with our team
* Join Telegram - 24/7 community support

***

**Current Status**:

* Presale Live (July 4-9, 2025)
* Twitter Launch: August 1, 2025
* Mobile App: Coming Q3 2025

**Quick Stats**:

* Network: Solana Mainnet
* Token Supply: 1 Billion
* Launch Cost: \~$0.01
* Success Rate: 5-10% (projected)


---

# 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://launchium.gitbook.io/launchium/home.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.