> For the complete documentation index, see [llms.txt](https://docs.deep3.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deep3.ai/the-business/our-dapps.md).

# Our dapps

<figure><img src="/files/5ca6K7aTKoh1PgtW8xwF" alt=""><figcaption></figcaption></figure>

Deep3 Labs integrates advanced AI into blockchain, transforming how users interact with Web3. Our dapps in trading, advertising, and security deliver personalized insights, precision targeting, and robust protection against bots. By leveraging on-chain data and sophisticated algorithms, our trading dapps provide actionable market intelligence, while our advertising tools drive tailored engagement and our security solutions detect suspicious activity. We build these dapps not only to deliver real value but also to showcase our ML tools—which are available for other developers—to drive a smarter, safer, and more rewarding blockchain ecosystem.


---

# 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.deep3.ai/the-business/our-dapps.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.