> 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/10-disclaimer.md).

# Disclaimer

This documentation is for informational purposes only and does not constitute financial, investment, or legal advice. Nothing in this book should be interpreted as a promise of future value, returns, or performance for $TOUCHGRASS, Grass Touchers, Screen Touchers, or any other Touch Grass asset.

$TOUCHGRASS and the NFT collections described here are digital assets with fluctuating prices. Their value can go up or down, and you should only participate with what you can afford to lose. Marketplace item prices, reward amounts, and other figures denominated in USD or $TOUCHGRASS are subject to change as token price fluctuates.

Program rules, rewards, eligibility requirements, and features described in this book are subject to change. Where a detail is marked TBD or exploratory, it is not yet confirmed and should not be relied upon.

Always do your own research before participating in any Web3 platform, including Touch Grass.


---

# 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/10-disclaimer.md?ask=<question>&goal=<endgoal>
```

`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.