> 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/gravity/mission.md).

# Mission

Gravity is a blockchain gaming platform focused on publishing great games while removing the Web3 barrier to entry for players and developers alike by providing onboarding protocols that are missing in the expanding GameFi space.

### Goals & Missions

Gravity Hub is designed to reinforce the weight of the word PLAY in the overused buzzword "Play & Earn". NFTs and Web3 integration need to be driven by the purpose of playing and not be tools that try to find a problem to solve by pretending to be games.

Our main missions within Gravity:

* Lower barriers to entry to web3 for game developers using our uniques and powerfull tools.
* Simplify the blockchain experience for the users
* Create a sustainable ecosystem of interconnected blockchain-powered games

<figure><img src="/files/HDyQgxMyfQo4TaPdoz7z" alt="" width="375"><figcaption></figcaption></figure>


---

# 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/gravity/mission.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.