> 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/key-features.md).

# Key Features

Gravity aims to make it easier for traditional game developers to enter the Web3 space and for users to understand and adopt blockchain technology. We want to create games that appeal to both GameFi and traditional gamers, making blockchain gaming accessible to everyone, including those unfamiliar with NFTs or unable to invest in them. To achieve this, we're developing a smart scholarship system and other mechanisms to allow all players to enjoy the game and progress without barriers.

To support this goal, we've been working on the **Gravity SDK,** a set of tools that streamline the game development process, reducing the time it takes to launch a mobile game by 6-8 months. The SDK will attract a wider range of high-quality games, helping to grow the blockchain gaming ecosystem.

<figure><img src="/files/WdwzLaUd6ZptsGG2gKFx" alt=""><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/key-features.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.