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

# World Builder

**World Builder** deploys economy-enabling infrastructure and services - including marketplaces, DEXs, bridges, protocols, account systems, economy live-ops, and data analytics services - expressly designed for builders and creators looking to develop on the G7 Network.&#x20;

By leveraging World Builder, games can implement secure, battle-tested solutions in hours instead of months, accelerating development cycles and significantly reducing costs by:&#x20;

* **Connecting players' accounts with their corresponding Web3 accounts**, including everything from importing existing Web3 accounts to providing them with smart contract accounts.&#x20;
* **Understanding player behavior**. World Builder comes with a powerful analytics stack and works closely with Summon and HyperPlay to allow developers to see exactly what their players are doing on and off-chain, and to connect this with their in-game analytics for a complete view of their activities.&#x20;
* **Bootstrapping game economies**. World Builder has a variety of tools developers can use to create dynamic sinks in their game economy, control inflation, and distribute rewards.


---

# 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.game7.io/world-builder.md?ask=<question>&goal=<endgoal>
```

`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.
