> For the complete documentation index, see [llms.txt](https://mixmob.gitbook.io/mixmob-player-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mixmob.gitbook.io/mixmob-player-guide/mixmob-racer-1/lore.md). # Lore {% embed url="" %} **Lore** What would 
you do if an A.I deleted our culture? In the late 21st century, a sentient A.I. Helix-9 launched The Great Delete to 'overhaul' global culture. The MixMob rebels countered by converting cultural artifacts into digital items on the dark web. Later, they leveraged underground robot racing, the hottest sport in town, as a cover to prepare MixBots for battling Helix-9. **Manifesto** Calling all hustlers, street racers, rebels, remixers and dreamers. This is our revolution. This is our manifesto. As we evolve, so does the game. We come together because our culture was erased, but from this crisis comes our chance to create something better. In the underground arenas of MixMob, respect, skill, and style are everything. Racer your MixBots and compete for glory. Let’s seize this opportunity. Let’s race, remix, and make it hot. --- # 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://mixmob.gitbook.io/mixmob-player-guide/mixmob-racer-1/lore.md?ask=&goal= ``` `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.