> For the complete documentation index, see [llms.txt](https://hub.fruitsalad.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.fruitsalad.ai/arcade/challenges/gravity-zone.md).

# Gravity Zone

Step into the world of FruitSalad's Gravity Zone, an intense and heart-pounding challenge inspired by the thrill of space exploration. In this immersive experience, you find yourself in a space environment, where your mission is to step on the correct platform ahead of you. One wrong move, and you'll plunge into the abyss of space. It's a high-stakes game that demands split-second decisions, agility, and nerve-wracking precision. Can you navigate the cosmic terrain and make every step count, or will you become lost in the infinite void of space? Brace yourself for an adrenaline-pumping adventure that will test your reflexes and determination to the limits!


---

# 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://hub.fruitsalad.ai/arcade/challenges/gravity-zone.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.
