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

# Maze

FruitSalad's Maze Game is an exhilarating journey that combines strategy, quick thinking, and knowledge. Your objective is simple: find the exit within a challenging maze while facing barriers that can only be overcome by answering questions correctly. As you navigate the labyrinth, you'll encounter barriers that require your knowledge and intellect to overcome. Answer the questions correctly to clear the path, but beware—the clock is ticking, and time is running out. Can you conquer the maze, overcome the obstacles, and make your way to the exit in time, or will you face the consequences of the unknown? It's a thrilling adventure that puts your problem-solving skills to the test!


---

# 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/maze.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.
