> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/token-information/symmio-foundation.md).

# Symmio Foundation

All official information about the SYMM token lives with the Symmio Foundation, including:

* **SYMM token**
* **Points Program**
* **Utility** 
* **Governance mechanisms**
* **Distribution details**
* **Development plans & Future Roadmaps**

and any associated updates are available exclusively through the following Symmio Foundation resources:

* [Symmio Foundation](https://symmio.foundation): high-level overviews, announcements, and background on the $SYMM token and the ecosystem.
* [Symmio Foundation Docs](https://docs.symmio.foundation): Explore the comprehensive documentation hub for in-depth details, technical specifications, and token-related policies.

Treat these as the only reliable sources for $SYMM token information. For anything else, the official communication channels are listed on both sites.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.symm.io/token-information/symmio-foundation.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.