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

# Development Roadmap

## ✅ Phase 1: RICE Token (2025 Q3)

Launching a utility token will be essential for fostering collaboration and innovation.

* Launch a utility token.
* Establish a Strong Partnership with Floki.
* Build a strong web3 community through giveaways, social engagement, and KOL marketing.

## Phase 2: Minibot M1 (2025 Q3)

A companion robot that rewards users through interaction. Interactive data contributes to the RICE AI protocol as a large data model. The goal of the M1 minibot is to accelerate the adoption of the RICE AI data-sharing protocol.

* Production line setup for Minibot M1.
* IP Collaboration with other Web3 brands to launch their own version of the M1 minibot (e.g, Floki Minibot M1)
* AI agent mini-game launch. Users can customize their own AI agent’s behavior and characteristics; this AI agent can later be imported into an M1 minibot, giving your companion a physical body.

## Phase 3: AI Data Sharing Protocol (2025 Q4)

The AI Data Sharing Protocol allows AI researchers or engineers to get access to the massive data collected through the millions of integrated robots deployed worldwide. The focus is on an "AI data as an asset" marketplace, providing users with valuable datasets for their robots. RICE AI will be the decentralized version of[ scale.ai](http://scale.ai) (<https://scale.com/>), specifically for robot intelligence.

* Launch RICE Robotics Data Marketplace.
* Build more tools for data collection into the protocol.
* Develop an app for Apple Vision Pro users to contribute robotics training data (with a rewards system).
* ⁠⁠SDK integration to 3rd party robots such as affordable humanoid robots G1 and H1 from Unitree.
* Prototype and Mass Production of Minibot M2.

## Phase 4: AI Foundry for building foundation models for robots (2026 Q1)

Powered by the decentralized data sharing protocol, our AI foundry disrupts the robotics industry with a decentralized marketplace to build foundation models for AGI robots that are actuated in the physical world.

Imagine buying your robotics parts, assembling your customized robot, and plugging in RICE AI to power its intelligence. Like ChatGPT powering thousands of newly emerging text-based applications today, RICE AI will be the affordable way to power robots in the future. Tapping into the DePIN industry for better infrastructure for robotics AI.

* Launch RICE AI Foundry used for training foundation models like robotics motion and spatial awareness.
* Launch GPU sharing feature for AI training.&#x20;
* RICE Humanoid Robots R\&D kickstart. <br>


---

# 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://rice-ai.gitbook.io/home/rice-protocol/development-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.
