> For the complete documentation index, see [llms.txt](https://docs.touchgrass.today/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.touchgrass.today/08-our-why.md). # Our Why Touch Grass exists because it's easy to spend a whole day behind a screen without meaning to. The platform turns going outside into something you actually track, build a streak around, and get rewarded for — not because a walk needs gamifying, but because a nudge helps. That same spirit extends past the people using the app. A portion of NFT mint proceeds from Grass Touchers and Screen Touchers, and a portion of pump.fun creator rewards earned from $TOUCHGRASS trading volume, go toward supporting youth athletics — funding sporting equipment for kids in the local community. More activity on Touch Grass, more trading volume, more minted NFTs — more impact for kids getting active outside too. It's the same idea running in both directions: get yourself outside, and help make it easier for someone else's kid to do the same. --- # 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.touchgrass.today/08-our-why.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.