> For the complete documentation index, see [llms.txt](https://docs.catcoin.io/history/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catcoin.io/history/products/exchanges/dappradar.md).
# DappRadar
{% embed url="" %}
Official Catoin DappRadar link
{% endembed %}
### About us
We want to make exploring, tracking & managing dapps, insightful, convenient and rewarding for all. We started in 2018, bringing high quality, accurate insights on decentralized applications to a global audience and rapidly became the go-to, trusted industry source. Today, we’re the starting point for dapp discovery - hosting 13551 dapps from over 48 protocols - offer comprehensive NFT valuation & portfolio management and lead the way in data led, actionable industry reporting.
### We’re the #1 global NFT & DeFi dapp store
Across the globe consumers are discovering dapps and managing their NFT/DeFi portfolios with **DappRadar**. We’re visited by over 500,000 users\* every month, our data powers leading industry partners and our quarterly reports are the trusted authority on multichain dapp market insight.
More details here
---
# 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.catcoin.io/history/products/exchanges/dappradar.md?ask=&goal=
```
`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.