> For the complete documentation index, see [llms.txt](https://docs.maplestoryn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maplestoryn.io/welcome-to-maplestory-n/our-ecosystem.md).
# Our Ecosystem
## The Ecosystem: MapleStory Universe
\
MapleStory Universe is a Virtual Worlds ecosystem designed to host a variety of applications built on the backbone of the MapleStory IP. This ecosystem serves as a hub for creativity, collaboration, and community engagement, supported by integral components that form a comprehensive ecosystem.
MapleStory IP boasts over 250 million+ registered users globally. With its various content and extensive resource pool from 22 years of live operations, MapleStory has built a robust ecosystem filled with items that can be NFTized and strong community features, equivalent to 5B+ USD lifetime revenue, making it ideal for blockchain integration.
Spearheaded by industry veterans who’ve developed multi-billion-dollar franchises, including MapleStory, Mabinogi and Dungeon & Fighter, the MapleStory Universe has 100+ employees globally supporting the project.
MapleStory Universe is expanding the ways players interact with game IPs, broadening the user base and ensuring the longevity of the IPs for decades to come. It is committed to creating an ecosystem where players are not just consumers, but co-creators among the ecosystems.
---
# 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.maplestoryn.io/welcome-to-maplestory-n/our-ecosystem.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.
