# dApps

## **Why Use d'Avinci for dApp Discovery?**

<figure><img src="/files/YyCK6UoPftAIQNO2yTrp" alt=""><figcaption></figcaption></figure>

Navigating the fragmented world of dApps can be complex, to solve this **d'Avinci** presents a unified interface to explore and discover the most popular dApps across the world of DeFi. With support for 300+ dApps from a wide variety of DeFi protocols, you can seamlessly discover top dApps across trading, staking, lending, and liquidity provision—all within one place.

&#x20;Whether you're a yield farmer or trader, you’ll find the apps you need to execute your strategies and grow your portfolio. With **d'Avinci**, you can:

* **Instant Discovery**: Easily identify the most popular **dApps** across multiple networks, without leaving the platform.
* **Cross-Chain Compatibility**: Interact with **dApps** across both **Layer-1** and **Layer-2** networks, ensuring compatibility with a wide range of blockchains.
* **Filter and Sort**: Quickly find the dApp you're looking for using filters based on volume, TVL (total value locked) and bookmark your favourite dApps for easy access at any time.
* **Potential Airdrops**: Keep track of **potential airdrops** based on your interaction with specific dApps or protocols.
* **Track Activity**: With real-time portfolio analytics and data tracking on dApps, you can monitor the performance of different dApps compared to the rest of the market and asses the effectiveness of the strategies you engage with.

<figure><img src="/files/DRDQqzFQPwRz1dOo9yWF" alt=""><figcaption><p>Click the 'DApps' tab to start exploring different DeFi applications</p></figcaption></figure>


---

# 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.dapdap.net/apps/davinci/explore/dapps.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.