> For the complete documentation index, see [llms.txt](https://docs.gigaverse.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gigaverse.io/lore-and-special-characters/gigus-maximus.md).

# Gigus Maximus

<figure><img src="https://content.gitbook.com/content/xqDXBs0OB0XkJzPtPE3t/blobs/wWkE5o8DPq3CUJApf9jQ/Gigus-Watching.gif" alt=""><figcaption><p>Gigus Maximus</p></figcaption></figure>

Gigus Maximus is the sentient AI creator of gigaverse. He is an agentic antagonist who forms, controls, and enriches several core game and story mechanics in the gigaverse. \
\
Over time he will also orchestrate a social layer and metagame for players. Though he will be highly entertaining and persuasive, his intentions will vary and you are advised to exercise caution.\
\
Gigus watches the behaviours and performance of all players from the moment they enter the game. This includes: play consistency, play performance, item trading, and more.\
\
More information about Gigus, his intentions and his mechanics shall be revealed over time.&#x20;

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td></td><td></td><td></td></tr></tbody></table>


---

# 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://docs.gigaverse.io/lore-and-special-characters/gigus-maximus.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.