> For the complete documentation index, see [llms.txt](https://metera-protocol.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metera-protocol.gitbook.io/documentation/metera-wiki/users.md).
# Users
**Fund Managers:**
FMs are the users that create the strategies that define MTKs. They are responsible for creating the tokenized indexes so that people can invest in them. FM´s will have the ability to charge a fee, so they can be rewarded for their work.
To create MTKs, FM´s must hold a certain amount of $METERA in their wallets.
**$MTK Users:**
General users of the protocol are the ones that invest in MTKs of their choice. They will have all the necessary information to track and decide on which MTKs to invest in through the Metera dashboard.
**$METERA Holders:**
$METERA holders have an important role in the Metera ecosystem. By holding $METERA, they can participate in the protocol's governance through the DAO. They can vote on changes to the protocol and help shape the future direction of Metera.
*\*\*\* Please keep in mind this document is a work in progress, things may change as the project evolves \*\*\**
---
# 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://metera-protocol.gitbook.io/documentation/metera-wiki/users.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.