> For the complete documentation index, see [llms.txt](https://robindog.gitbook.io/robindog-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robindog.gitbook.io/robindog-docs/16-protocol-revenue-and-the-value-loop.md).

# 16 Protocol revenue and the value loop

RobinDog's sustainability should come from real product use rather than reliance on token price alone.

Potential protocol revenue may include prediction-market trading fees, service fees for Narrative Combo Positions, Creator-market revenue sharing, professional data, API, and research tools, and other publicly disclosed protocol services. Exact fees will be published before product launch.

Protocol revenue will prioritize product and security development, data and oracle costs, market resolution, liquidity development, Creator and ecosystem growth, and treasury reserves.

High-quality stories and Creators → More tradable markets → More real users and liquidity → More reliable probability and settlement data → More protocol revenue and ecosystem resources → More Story Trees and markets

$RDOG coordinates participants. It does not represent equity in the protocol, a fixed return, dividend rights, or a claim on treasury assets.


---

# 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://robindog.gitbook.io/robindog-docs/16-protocol-revenue-and-the-value-loop.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.