> 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/game7-developer-program.md).

# Game7 Developer Program

The Game7 Developer Program is designed to support game developers who want to bring their games to the G7 Network. Applicants accepted into the Game7 Developer Program will receive support from Game7, and the collective Game7 products. This support includes:

1. Technical assistance integrating with the G7 Network using World Builder tooling.
2. Exposure to the Game7 community. With select games having the opportunity to be supported by  *Quests* and *LootDrops* via the [Game7 portal](https://app.game7.io).
3. Economic live-ops and tokenomics support
4. For games that garner significant interest in the community, grants to bootstrap liquidity for their tokens.

If you are interested in participating in the Game7 Developer Program, please fill the form below:

{% embed url="<https://nwhkxwwdwhn.typeform.com/to/nilcyzrS>" %}


---

# 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.game7.io/game7-developer-program.md?ask=<question>&goal=<user_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.