> For the complete documentation index, see [llms.txt](https://docs.metapool.app/master/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metapool.app/master/faq-frequently-asked-questions/faq-mpdao-and-governance/faq-community-representatives.md).
# FAQ Community Representatives
What is a community representative?
A community representative is an individual who voluntarily presents an initiative proposal to Meta Pool's DAO. These individuals typically lead communities or organizations and are seeking funding. They share a common vision with Meta Pool, aligning their goals with those of the protocol and decentralized finances.
Which are the requirements for being considered a community representative?
To be eligible as a community representative, one must be a publicly recognized individual who has gained a positive reputation within the community and presents an initiative proposal to the DAO.
Meta Pool may utilize the i-am-human platform, a proof-of-personhood platform, to verify the identity of individuals.
What is the difference between community representatives and ambassadors?
Ambassadors are part of an internal program to widespread Meta Pool contents worldwide. A community representative can be any individual leading a community.
---
# 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.metapool.app/master/faq-frequently-asked-questions/faq-mpdao-and-governance/faq-community-representatives.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.