# STAKEHOLDERS

At Polyquest, we are redefining the landscape of prediction markets with a unique profit-sharing model that ensures maximum value for all participants—whether they are users, quest creators, affiliates, or strategic partners. As a **Web3.5 DeFi Community Platform**, we blend the best of Web 3.0 principles with innovative financial mechanisms to create a sustainable, engaging, and profitable ecosystem.

Our approach is centered around a fair and transparent fee structure. With a low market contract fee of approximately 2%, we provide a competitive edge over traditional and even many Web3 platforms, which often charge much higher fees. By keeping our fees low, we attract a broader user base and foster deeper community engagement, driving higher transaction volumes and growth.

But our revenue model extends beyond just market contract fees. We have developed additional features such as the "Pay-to-Survey" mechanism, **APY-to-Prediction Conversion**, and **Market Contract API**, which open up new revenue streams and expand the scalability of our platform. These innovative features not only enhance user experience but also create multiple avenues for affiliates and partners to engage and earn, aligning our success with that of our stakeholders.

This unique combination of low fees, diverse revenue streams, and community-centric growth positions Polyquest as a leader in the next generation of prediction markets. As we continue to evolve, we are committed to sharing our success with those who contribute to and support our ecosystem.


---

# Agent Instructions: 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:

```
GET https://docs.polyquest.xyz/polyquest-for/stakeholders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
