> For the complete documentation index, see [llms.txt](https://wp.readdee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.readdee.com/why-readdee.md).

# Why ReadDee

In the evolving digital realm, ReadDee stands out with its innovative Social platform built on Web3.0, enhancing user privacy, and financial rewards through a token system. This platform cultivates a vibrant ecosystem where creativity and engagement thrive.

Key Features of ReadDee:

* Web3 : Built on blockchain technology, ReadDee offers unparalleled privacy and complete control over your data.
* Community Gov: As a decentralized autonomous organization (DAO), ReadDee allows users to directly influence platform governance and decisions.
* Data Storage and NFTs: Ensuring content authenticity and monetization opportunities, ReadDee transforms your creations into unique NFTs.
* Engagement Mining: Users earn rewards through active participation, enhancing community contributions.
* Ecosystem : An open platform that encourages users to expand the ReadDee ecosystem by building and connecting communities.

Join ReadDee to experience the future of content sharing and community engagement where your voice and privacy are prioritized.


---

# 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://wp.readdee.com/why-readdee.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.