> For the complete documentation index, see [llms.txt](https://docs.lazai.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazai.network/lazpad/platform-overview/open-launch.md).

# Open Launch

The Open Launch mode is designed to be inclusive, enabling all projects and developers to tokenize their AI agents without barriers. This mode democratizes access to Lazpad’s ecosystem, allowing participants to issue agent tokens freely and contribute to the decentralized AI landscape.

#### **Key Features**

* **0 Fees for Token Creation**\
  Anyone can create AI agent tokens on the platform without incurring any fees, ensuring accessibility for all projects regardless of size or resources.
* **Automatic Fund Injection into Netswap**\
  Once a project on the Open Launchpad completes its fundraising and the bonding curve phase, the funds raised will be automatically injected into Netswap.
* **Bonding Curve Trading**\
  During the bonding curve phase, users can freely trade tokens.\
  Lazpad charges a 1% fee on the total purchase or sale price for each trade, payable in Metis. This incentivizes a sustainable trading ecosystem while maintaining low transaction costs.
* **Graduation to Netswap**\
  When a token successfully graduates from the Lazpad platform to Netswap, a fixed fee of 1 Metis is charged.


---

# 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.lazai.network/lazpad/platform-overview/open-launch.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.
