> For the complete documentation index, see [llms.txt](https://oap.gitbook.io/the-open-ads-protocol-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oap.gitbook.io/the-open-ads-protocol-litepaper/the-oap-token/token-utility.md).

# Token Utility

At it's core, the OAP token is a utility token specifically designed for our decentralized advertising layer. This section outlines the role and functions of OAP in the platform's ecosystem, describing its impact on advertisers, consumers, and ad publishers.

#### **Transactional Role**  <a href="#transactional-role" id="transactional-role"></a>

The OAP token serves as the native currency within the platform. Advertisers use the token to purchase ad space and impressions and Publishers receive it as payment. This token-based model ensures liquidity and encourages participation, creating a demand for $OAP.

#### **User Engagement Incentives**  <a href="#user-engagement-incentives" id="user-engagement-incentives"></a>

Users who interact with or view ads receive OAP tokens. This approach enhances user engagement, provides advertisers with meaningful audience feedback, and encourages a fair attention economy.

#### **Data Sharing Rewards**  <a href="#data-sharing-rewards" id="data-sharing-rewards"></a>

Users are incentivized with OAP tokens to share additional information about their browsing habits or interests. This enables advertisers to target their campaigns more effectively.

#### **Referral Incentives**  <a href="#referral-incentives" id="referral-incentives"></a>

To encourage platform growth, OAP tokens are offered as rewards for successful referrals. Bringing new advertisers or users to the platform benefits all participants and promotes expansion of the OAP ecosystem.


---

# 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://oap.gitbook.io/the-open-ads-protocol-litepaper/the-oap-token/token-utility.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.