> For the complete documentation index, see [llms.txt](https://dappos.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dappos.gitbook.io/docs/dappos/overview-of-dappos/core-features.md).

# Core Features

* **Multi-Agent Framework (MAF)**: With 300–400 specialized vertical agents and more than 200 integrated tools, DAPPOS delivers comprehensive Web3 generalization—capable of handling everything from quantitative analysis and trading strategies to market intelligence.
* **The Bubble Engine**: This Web3-focused reinforcement learning engine drives perpetual evolution, continuously learning from real-time sources such as X and Binance Square. Through the Bubble task platform, users can contribute new knowledge directly, accelerating integration and adaptation.
* **Intent Execution Network**: Leveraging the tested Intent Execution Network with over 5 million users and 12 million transactions, DAPPOS ensures safe, efficient execution of AI-generated plans, transforming complex intents into secure on-chain actions with institutional-level reliability.


---

# 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://dappos.gitbook.io/docs/dappos/overview-of-dappos/core-features.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.