> For the complete documentation index, see [llms.txt](https://whitepaper.usegpu.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.usegpu.app/gpu-infrastructure/compute-revenue.md). # Compute Revenue Understand how GPU rental and future inference services are intended to create additional revenue for the USE-GPU ecosystem. GPU rental and inference services are future revenue paths. They are not Phase 1 revenue. In Phase 1, creator-fee revenue funds the mining system while the treasury accumulates. ### GPU rental The intended rental path begins after GPU infrastructure becomes available. ``` GPU INFRASTRUCTURE ↓ AVAILABLE COMPUTE CAPACITY ↓ RENTAL ↓ RENTAL REVENUE ``` Phase 3 is designed to extend capacity beyond the initial project-owned hardware. ``` GPU OPERATOR ↓ CONTRIBUTES GPU ↓ GPU BECOMES AVAILABLE FOR RENTAL ↓ RENTAL FEE GENERATED ↓ 70% TO OPERATOR ``` External GPU operators can contribute hardware and receive **70% of rental fees**. The roadmap does not define the allocation of the remaining rental fee. ### Inference services Phase 4 plans to introduce an inference API for developer-facing compute usage. ``` GPU INFRASTRUCTURE ↓ COMPUTE CAPACITY ↓ INFERENCE API ↓ DEVELOPER USAGE ↓ COMPUTE REVENUE ``` Developers pay per token of compute. The roadmap does not define API design, supported models, pricing, or service levels. ### Mining-pool expansion Later GPU rental and inference-service revenue can contribute to the mining pool. This expands the intended revenue base beyond the creator fee that funds Phase 1. The intended economic progression is: ``` Trading activity → creator-fee revenue → mining and treasury ↓ GPU infrastructure → rental and compute revenue → broader economic activity ``` The roadmap describes Phase 4 as the intended point where the ecosystem becomes self-sustaining. This is a planned outcome, not a guarantee. --- # 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://whitepaper.usegpu.app/gpu-infrastructure/compute-revenue.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.