> 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/ai-health-coach.md). # 🧠 AI Health Coach **AI Health Coach** is a core HealthFi layer, bridging real-world fitness behavior with long-term digital progression. This system is not designed as a generic chatbot, but as a **behavioral optimization engine** focused on habit formation, consistency, and health improvement. ### Purpose of the AI Coach The AI Health Coach exists to solve a critical weakness of early Move-to-Earn models: **users chased rewards, not health outcomes**. Instead of rewarding raw volume or extreme activity, the AI Coach: * Encourages sustainable movement patterns * Adapts goals to individual fitness levels * Reinforces long-term habits rather than short-term spikes This positions Gear Runner as a **HealthFi product**, not just a GameFi app. --- # 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://docs.gearrunner.app/ai-health-coach.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.