> For the complete documentation index, see [llms.txt](https://polyway.gitbook.io/polyway/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polyway.gitbook.io/polyway/ecosystem-overview/plw-token.md).
# PLW Token
The PLW Token is the Polyway ecosystem’s native asset, which gives its holders access to exclusive benefits, including:
\- Distribution of 35% of all platforms revenues from betting, casino, and prediction markets via a staking contract as rewards.
\- Participation in DAO voting on platform traction, empowering holders as stakeholders and decision-makers.
\- Extra rewards and bonuses for active participation in platform activities, such as bets on sports, and other events.
\- Free bets, token drops, cashback benefits, and much more.
To further upend benefits and value for PLW Token holders over the long term, Polyway applies a deflationary mechanism, which involves the use of 10% of all platform profits for the buyback and burning of PLW Tokens.
\
---
# 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://polyway.gitbook.io/polyway/ecosystem-overview/plw-token.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.