> For the complete documentation index, see [llms.txt](https://docs.powerpool.finance/powerpool-and-poweragent-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powerpool.finance/powerpool-and-poweragent-network/powerpool-overview/powerpool/vision-2027.md).
# Vision 2027
In three years, dePIN networks such as PowerAgent will perform more and more transactions for users, compared to the current situation where users perform many manual actions. This will happen because users, AI agents and protocols will generate an increasing number of flows and intent-based strategies needed to use web3/Defi in a convenient and automated way for a growing user base.
As a result, Transaction as a Service dePIN networks will become the primary consumers of block space. It will account for a significant share of block space consumed for these transactions in the foreseeable future.
PowerPool DAO is bringing to market a network and set of tools designed to support this automated future. It will provide a reliable, decentralized, and permissionless service for user flows and intents, AI-generated policies, protocols, and dApps that require automation based on on-chain and off-chain triggers.
---
# 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.powerpool.finance/powerpool-and-poweragent-network/powerpool-overview/powerpool/vision-2027.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.