> For the complete documentation index, see [llms.txt](https://mokokostudios-organization.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mokokostudios-organization.gitbook.io/whitepaper/mokoko.md).

# Mokoko

## AI **powered Infra for Web3 Gaming and Assets Launch**

Vision:

**We empower our system with AI to build a smart yield aggregation platform focused on the gaming sector.**

**For Projects:** We provide a one-stop SDK and launchpad, integrating AI yield models to help you target the right users and boost conversion & retention.

**For Players:** Our AI agents craft personalized play-to-earn strategies, enabling optimal yields with a lightweight experience that balances fun and efficiency.

Establishes a long-term growth model through a virtuous cycle of "AI + Infra + GameFi":

1. Our SDK rapidly aggregates thousands of lightweight Web3 games.
2. Integrated game developers can issue assets with one click and join yield pools.
3. AI guides players to optimize their participation and earnings.
4. This leads to: Increased player earnings → More players and higher engagement → Higher platform revenue → Greater demand for the platform's token.


---

# 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:

```
GET https://mokokostudios-organization.gitbook.io/whitepaper/mokoko.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.