> For the complete documentation index, see [llms.txt](https://docs.gearrunner.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gearrunner.app/overview.md). # Overview Gear Runner is a **mobile-first HealthFi game** that transforms everyday movement into meaningful progression. By combining fitness tracking, AI-powered health guidance, and game-based mechanics, Gear Runner turns walking, running, and daily activity into an engaging experience that rewards consistency rather than intensity. Players improve their health, unlock in-game progression, and participate in a dynamic game world where **smart movement, long-term habits, and strategic choices** matter more than short-term effort. Gear Runner's core is not about earning quickly, but about **building sustainable habits, staying active, and enjoying a game that grows alongside your fitness journey**. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gearrunner.app/overview.md?ask=&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 `build a script that syncs our docs to a CMS` 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.