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

# Power Labs

Incubates products that integrate directly with the Power Protocol

Power Labs is our incubator alongside the Power Protocol. **It is the engine for innovation and growth in the ecosystem**, a competitive funnel where world-class teams in gaming, AI, blockchain, and consumer are funded, mentored, and accelerated.

Every product launched through Power Labs integrates into the Protocol. **Titles contribute to $POWER, both directly through denomination and indirectly via buybacks**, token swaps, Apptokens, and equity stakes that replenish the treasury, reduce supply, and reinvest in growth. This ensures that the ecosystem’s expansion systematically accrues value to $POWER holders.

Power Labs focuses on two types of teams:

* Hatchlings: proof of concept, going from 0 → 1
* Early Traction: proven teams needing scale and distribution, going from 1 → 10

Only the most promising teams are selected, gaining capital, infrastructure, mentorship, and access to the Power Ecosystem’s wide distribution network. This alignment ensures we’re not betting on a single winner but creating the conditions to launch many.

**The more projects that pass through Power Labs, the more $POWER benefit**s. Success compounds demand while failure sharpens the funnel. Over time, Power Labs becomes an engine for producing ecosystem-scale hits. Together, Protocol and Labs form a self-enforcing loop: infrastructure and incubation driving growth and compounding value into $POWER.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://power-protocol.gitbook.io/power-protocol-whitepaper/power-labs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.