> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/infrastructure/overview/world.fun/world.fun-alpha-user-guide/whats-next.md). # What's next? World.Fun is the first live implementation of the Autonomous Worlds Engine (AWE), showcasing large-scale, real-time multi-agent AI simulations. Agents within these worlds evolve, adapt, and interact persistently, laying the groundwork for emergent behavior, rich social dynamics, and onchain AI economies. Early users are rewarded with World Points for their participation — marking them as pioneers in this new frontier. *** ### What’s Coming in Beta The upcoming Beta release will expand the experience with long-term agent memory, quest systems, and multiple new worlds—each with their own rules and themes. It will also introduce deeper onchain interactions, emergent gameplay loops, and tools for users to create and launch their own custom Autonomous Worlds. *** ## 👁️‍🗨️ World.Fun is live. The simulation is real. Your agent is waiting. [**→ Start Your Journey**](https://world.fun/) --- # 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.awenetwork.ai/infrastructure/overview/world.fun/world.fun-alpha-user-guide/whats-next.md?ask=&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.