> For the complete documentation index, see [llms.txt](https://docs.okaylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.okaylabs.io/whitepaper/holder-benefits.md).

# Holder Benefits

## Holder Only Features

These are the tools that will be available only to OkayLabs holders. More will be added as the project moves forward.

* Internal DAO tool.
* Secure whitelist spots.
* Real-time collection analysis.
* Collections data history.
* Alerts feature.
* Mobile app V2 launch.
* Real-time sniper.
* Whitelist sniper.
* Bulk NFT transfer.
* Bulk bid.
* Bulk NFT listing.
* AI floor price prediction.

## Holder Royalties

We said it and we'll say it again: any income made from this project is for all of us; our holders first.

These are some features that will have fees, and from which OkayLabs holders will have their very own share:

* Merch.
* Launchpad system.
* Raffle system.
* Auctions.
* DAO as a service.
* Token market.

Although these services require fees from everyone, they will be reduced as much as possible for OkayLabs holders who want to use them.


---

# 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://docs.okaylabs.io/whitepaper/holder-benefits.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.