> For the complete documentation index, see [llms.txt](https://docs.osmi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.osmi.ai/roadmap.md).

# Roadmap

OSMI’s journey to decentralize AI has been marked by exciting milestones, from launching the initial PoC and node network in 2023 to the public beta release in 2024. With the foundation firmly in place, we’re ready to take OSMI to the next level with the $OSMI token launch in Q4 2024. This token will unlock core functionalities, allowing users to purchase node licenses, access AI inference capabilities, and utilize new image creation features, all while supporting a deflationary model with token burns.

Looking ahead to 2025, OSMI will introduce staking rewards, a GPU marketplace for private data ingestion, and API access for commercial use, opening up decentralized AI capabilities to businesses and developers worldwide. Each step of our roadmap is designed to build a resilient, scalable, and community-driven ecosystem, making OSMI a trailblazer in the future of people-powered AI.

<figure><img src="/files/wGo8HEqaW6YSevCO1new" alt=""><figcaption><p>OSMI Roadmap</p></figcaption></figure>


---

# 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://docs.osmi.ai/roadmap.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.