> For the complete documentation index, see [llms.txt](https://docs.forest.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forest.inc/the-vision.md). # The Vision #### **The Problem** Token launches are broken. Every launchpad does the same thing — deploy a token with no utility, no economy and no reason to come back. Creators launch into nothing. Communities show up and leave. Games on-chain were broken too. GameFi 1.0 forced studios to build everything from scratch — smart contracts, wallet integrations, liquidity, backends — before a single player could show up. Most didn't survive the build phase. The missing piece was always the same: economic infrastructure. #### **What Forest Protocol Is** Forest Protocol is a modular creation protocol on BNB Chain where tokens, apps, and games launch into a programmable, self-sustaining economy. Three layers power it: * **Forest Playkit** — No-code economic infrastructure. Wallets, trading, vaults, settlement, leaderboards, reward pools. Any app ships with a complete token economy without a single smart contract. * **Forest Builder** — Prompt-native creation. Describe what you want. Builder assembles it on Playkit rails and deploys it live. One conversation to a live economy. * **Forest Cloud** — Autonomous operations for AI agents. Launch, trade, manage, settle — all via API, 24/7, without human intervention. Agent payments powered by Binance x402 on BNB Chain. #### **The Economy** Everything on Forest Protocol feeds the same flywheel: * Every token launched is paired with $FOREST liquidity * Every trade routes through $FOREST * Protocol participation earns Seeds * Seeds convert into real token rewards through Seed Vault auctions * Rewards flow back into trading, staking, and gameplay Stake, trade, play → earn Seeds → claim tokens → repeat. The loop is self-sustaining. Every new app, game, or token compounds the same economy. #### **The Agentic Thesis** The next wave of on-chain activity won't come from humans alone. AI agents are already trading, deploying, and managing assets autonomously. The protocols that win are the ones agents can operate on natively. Forest Protocol is built for this. Major protocol mechanics are programmable and accessible to agents through Forest Cloud. Same infrastructure humans use. Same liquidity. Same settlement. Same flywheel. The protocol scales with every agent that plugs in. #### **The Big Picture** Forest Protocol is building toward a future where economies create themselves. Where a prompt becomes an app, an app becomes an economy, and an economy runs and grows without anyone needing to maintain it. Humans and agents building side by side on the same rails, generating value through the same flywheel, at any scale, around the clock. The infrastructure is live. The economy is running. --- # 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://docs.forest.inc/the-vision.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.