> For the complete documentation index, see [llms.txt](https://whitepaper.gravityhub.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gravityhub.xyz/onboarding-strategy/onboarding-developers/developer-sponsorship.md).

# Developer Sponsorship

Our main goal remains to attract the best developers to the Gravity ecosystem because they provide the content or services that players are looking for. We will use a portion of our tokens to sponsor the most talented developers, which will take various forms, here are some examples:

**No-cost advertising credits**: Gravity will have an advertising system that will allow game developers and others to promote their games, services, and products to players across the platform. Advertising credits will be purchased in the Gravity Developer Center with GVT tokens.

Gravity will sponsor advertising campaigns for certain developers by providing them with "free credits".

<br>


---

# 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://whitepaper.gravityhub.xyz/onboarding-strategy/onboarding-developers/developer-sponsorship.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.