> 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/usdpower-token/value-accrual.md).

# Value Accrual

**$POWER is designed as a systemic value-capture token across the entire Power ecosystem**. Unlike tokens tied to a single game or product (content tokens), $POWER accrues demand from multiple sources: players, studios, brands, IPs, and partners. Every transaction, integration, and launch compounds value back into the token economy through a blend of buybacks, sinks, staking, and treasury growth.

**Expansion loop:**

* Fableborne proves the tech and monetization loops actually work (first sink + first proof).
* Protocol SDK/API extends those systems to external studios, multiplying usage.
* Fiat + token flows are consistently converted into $POWER via buybacks, treasury, and burns.
* Power Labs creates a pipeline of new products, each tied back to $POWER.
* New games/IP add more sinks and velocity, broadening token demand.
* Ecosystem grows into AI, branded IP, mainstream integrations, and expanding surface area.
* Each cycle compounds, the more integrations, the more $POWER is bought, staked, and burned.


---

# 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/usdpower-token/value-accrual.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.