# AI-Driven curation: the future of Web3 discovery

The rapid evolution of AI technology in 2024 reshaped how both the DAO and DappRadar UAB approach Web3 discovery and governance. Recognizing AI’s potential in streamlining operations, curating data, and enhancing decision-making, the DAO began implementing AI-driven solutions to improve governance efficiency and ecosystem engagement.

One of the key initiatives involves the development of AI Agents, designed to assist both projects and users in navigating the fast-paced Web3 landscape. These AI-powered tools aim to bridge on-chain and off-chain data, filtering high-quality insights while reducing noise in an increasingly saturated market.

| <h3><strong>AI Initiative</strong></h3> | <h3><strong>Function</strong></h3>                             |
| --------------------------------------- | -------------------------------------------------------------- |
| AI Agents for Curation                  | Automate data verification and ranking of Web3 projects        |
| AI-Powered Governance Tools             | Enhance proposal filtering and decision-making efficiency      |
| User-Centric AI Features                | Improve project discovery and engagement through data insights |

However, the DAO’s approach to AI is not purely automation-driven. A Human-in-the-Middle model will ensure that AI assists with curation, governance and decision-making, while human contributors refine and contextualize AI-generated insights. This hybrid approach will accelerate data aggregation, minimize misinformation risks and strengthens trust in curated Web3 intelligence.


---

# 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.dappradardao.com/dappradar-dao-report-2024/management-overview/ai-driven-curation-the-future-of-web3-discovery.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.