> For the complete documentation index, see [llms.txt](https://smol404.gitbook.io/smol404-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smol404.gitbook.io/smol404-docs/launchpad/overview.md). # Overview SMOL404 is designed to become infrastructure for the wider BNB agent economy. The launchpad allows builders to create their own liquid BAP 578 ecosystems without developing a 404 implementation from scratch. The basic process is: **Build an agent** ↓ **Create its BAP 578 identity** ↓ **Connect execution infrastructure** ↓ **404ize the agent ecosystem** ↓ **Bootstrap liquidity** ↓ **Launch the market** Execution infrastructure can include custom systems or tools such as Binance Agent OS. The launchpad itself remains focused on the ownership and market layer. Its role is to turn an NFA ecosystem into a liquid market. ### Why launch through SMOL404? A normal NFA project may launch a collection and then depend on secondary NFT trading for liquidity. SMOL404 allows builders to begin with a fungible market. This provides several advantages. #### Immediate market access Users can trade the ecosystem token from launch through standard BNB Chain liquidity infrastructure. #### Fractional onboarding New users can enter with smaller amounts rather than buying an entire agent. #### Better price discovery A liquid pool creates a continuously updating market price for the ecosystem. #### Broader distribution Token markets are already deeply integrated into wallets, DEXs, analytics platforms and trading interfaces. #### Agent identity remains preserved Builders gain fungible liquidity without giving up the BAP 578 NFA layer. #### New monetization models Liquid agent ecosystems can potentially create new economic structures around agent usage, access, performance or revenue. SMOL404 does not prescribe one model. It provides the market primitive builders can build on top of. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://smol404.gitbook.io/smol404-docs/launchpad/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.