> For the complete documentation index, see [llms.txt](https://p00ls.gitbook.io/token-integrations-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://p00ls.gitbook.io/token-integrations-guide/polls/asking-your-token-holders.md).

# Asking your Token Holders

Community participation is one thing, but community collaboration is participation taken to a new level. Take advantage, or rather let your community take advantage of token weighted voting. Design polls, pose questions to the community, or give them a say in something monumental.&#x20;

1 token is 1 vote. The more tokens someone has the more voting power they get. When it comes to releasing a new collection, having this type of data is powerful. For you your community, when they see you honor something they voted on and they feel like they had something to do with the outcome, they will feel much closer to it.


---

# 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://p00ls.gitbook.io/token-integrations-guide/polls/asking-your-token-holders.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.
