> 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/roadmap/phase-4-inference-api.md).

# Phase 4: Inference API

Extend the GPU network into developer-facing compute infrastructure through an inference API priced around actual compute usage.

Phase 4 is the planned developer-facing infrastructure phase. It introduces an inference API on top of the GPU network.

### Compute usage

```
GPU infrastructure
        ↓
Compute capacity
        ↓
Inference API
        ↓
Developer usage
        ↓
Compute revenue
        ↓
Additional ecosystem revenue
```

Developers pay per token of compute. The mining pool can grow with usage. The roadmap does not define API endpoints, supported models, pricing, or service levels.

### Intended economic progression

* **Phase 1:** Trading activity funds the initial mining system
* **Phase 2:** Treasury accumulation targets physical GPUs
* **Phase 3:** External operators expand GPU capacity
* **Phase 4:** Developers consume that compute through an inference API

Phase 4 depends on GPU infrastructure being available for developer-facing compute. The roadmap describes this phase as the intended point where the ecosystem becomes self-sustaining. It is a roadmap outcome, not a guaranteed result.


---

# 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/roadmap/phase-4-inference-api.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.