> For the complete documentation index, see [llms.txt](https://allyhq.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://allyhq.gitbook.io/docs/ally-ad-protocol/protocol-stakeholders.md).

# Protocol stakeholders

The protocol engages five principal stakeholders:

1. **Users:**
   1. **Benefits:** Access to optimal swaps without fees and an opportunity to earn passive yields.
   2. **Contributions:** They view advertisements.
2. **Advertisers:**
   1. **Benefits:** Show advertisements to a targeted crypto audience, utilizing user address information for precise targeting.
   2. **Contributions:** Provide monetary compensation.
3. **Governance Token Holders:**
   1. **Benefits:** Potential appreciation of the value of their stake in the company.
   2. **Role:** Oversee and manage the protocol.
4. **DeveloperDAO** (Comprising the core developer team and external contributors):
   1. **Benefits:** Receive fair compensation for their contributions.
   2. **Role:** Propel the enhancement of the protocol.
5. **MarketingDAO** (Comprising the core advertising network team and external affiliates):
   1. **Core Team Benefits:** Increase the value of their company stake by optimizing protocol revenues and token buybacks through negotiations with advertisers.
   2. **Affiliate Benefits:** May receive a share from the MarketingDAO treasury.
   3. **Role:** Drive user growth within the protocol.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://allyhq.gitbook.io/docs/ally-ad-protocol/protocol-stakeholders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.