RICE AI

RICE AI (RICE) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

RICE AI — an AI/Robotics / DePIN / Data marketplace project on BNB Smart Chain that describes a “decentralized AI foundry” for collecting real‑world robotics data and training robotics foundation models; the token (symbol: RICE) is used as a utility token for rewards for data contributions, subscription payments/discounts, burn mechanics and governance (per the docs).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

What it is: a protocol/ecosystem where people and companies can share data for robotics and receive rewards.
Who it’s for: robot owners/operators and companies with data; research labs and companies that need datasets and models.
Why onchain/token: the token is needed to pay and accrue rewards in the marketplace, as well as for governance; the blockchain is used for accounting of the token and incentives.

How it works (very briefly)

The user does: uploads/provides robotics data to the RICE AI ecosystem.
The system does: accounts for the contribution and accrues token rewards; aggregates data for sale to buyers.
The user gets: a reward in the RICE token; (for clients) access to data and/or models via a subscription.
Where the blockchain is: accounting and circulation of the RICE utility token (BSC), incentive settlements and related mechanics.
Token role (if any): rewards for data contributions, subscription payment/discount, burn mechanics (part of the fees goes to burn) and governance (per the docs).

Quick links: AI thesis fit

Project passport

Field	Value
Project name	RICE AI
Also known as (aliases)	Rice AI, RiceAI
Logo (logo)	../assets/255_rice-ai_logo.svg
Token symbol (ticker)	RICE
Category	AI/Data \| AI/Robotics \| DePIN
Primary chain (chain)	BNB Smart Chain
Type	EVM
Network status	mainnet
Consensus (consensus)	PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date)	2025-08-18 (TGE per the docs)
Project status (status)	active (the docs were updated 5 months ago)
Token (standard)	BEP-20
Token contract	0xb5761f36FdFE2892f1b54Bc8EE8baBb2a1b698D3
Token model (token_type)	utility (governance)
Max supply	1,000,000,000 RICE
Issuance	fixed + burn (a deflationary model is claimed)
Tokenomics (tokenomics, brief)	rewards for robotics data contributions; part of the fees from data buyers is used for burn; governance token (per the docs).
Governance	DAO governance is claimed in the ecosystem documentation (details not disclosed)
Admins/keys	unknown
Audit	—
Bug bounty	— (not found)
Team (team)	Rice Robotics (as “backed by” in the docs)
Funding (investors/funding)	Rice Robotics “raised $7 million in 2023 funding round” (as a claim in the docs)
AI component (ai_component)	robotics foundation models, data foundry
Use‑case (use_case)	data collection for robotics, model training
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	1 / 1 / 3 / 2
Last verified	2026-02-06

Links (links_*)

Type	Link
Website	https://www.riceai.xyz/
Docs	https://rice-ai.gitbook.io/home
GitHub	—
Releases / Changelog	—
Whitepaper	https://riceai.xyz/whitepaper
Roadmap	https://rice-ai.gitbook.io/home/rice-protocol/development-roadmap
Security advisories	—
Explorer	https://bscscan.com/token/0xb5761f36fdfe2892f1b54bc8ee8babb2a1b698d3
X	https://twitter.com/realRiceAI
Discord	https://discord.com/invite/5fb2VUV29Z
Telegram	https://t.me/Rice_AI
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/rice-ai
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/rice-ai/

General project overview

In its documentation, RICE AI describes a “decentralized AI foundry” for robotics: the project claims that the robotics industry has a shortage of training data and proposes to build a market/protocol for collecting real‑world data via a token‑based incentive model. The data is intended to be sold to research labs and companies, and also to be used for training in‑house robotics foundation models available via a subscription (with a discount when paying with the native token).

Features/modules

Data marketplace / “AI data as an asset”: a protocol/marketplace where contributors provide robotics data and buyers get access to the data.
Incentives on the RICE token: rewards for data contributions + deflationary burn mechanics from fees.
AI Foundry: training foundation models for robots on the collected data (per the roadmap — 2026 Q1).
Hardware/DePIN component: the roadmap features Minibot M1/M2 as a data source and a tool to accelerate adoption.

Typical scenarios

Scenario 1: a robot owner/operator provides data → the protocol accounts for the contribution → receives token rewards (per the tokenomics).
Scenario 2: a lab/company buys datasets → pays a fee → part of the fee is used to burn tokens (per the tokenomics).
Scenario 3: a client subscribes to models/access to foundation models → gets a discount when paying in RICE (per the tokenomics).

Getting started (wallet/network)

What you need: an EVM wallet for BNB Smart Chain and the RICE token (for participation in the incentive model/payments).
Network/chain: BNB Smart Chain.
Fees: BNB Chain fees (BNB) for onchain transactions with the token; protocol fees are described conceptually (fees from data buyers, subscriptions), but specific rates are not provided in the extracted Tier‑1.

Architecture/tech (non‑AI)

Components: the RICE token/smart contract (BSC), an offchain platform/marketplace for uploading/selling data, data storage/processing pipelines, an AI pipeline for model training (AI foundry — per the roadmap).
Participant roles: data providers (individuals/companies), data buyers (research labs/companies), robot users/owners, the team/platform operators.
Where logic runs: token accounting and part of the economic mechanisms — onchain (BSC); data collection/storage and model training — offchain (by the nature of the tasks).
Dependencies: data storage infrastructure and MLOps for model training; specific providers are not listed in the extracted Tier‑1.

Token/economics (expanded, no forecasts)

Token utility: rewards for providing robotics data; payment/discount for model subscriptions; governance token; a deflationary model via burn from fees (per the tokenomics).
Protocol necessity drivers: (a) to incentivize data contributions via rewards; (b) to give a discount when paying for the subscription; (c) governance of the protocol layer (per the tokenomics).
Who pays fees: data buyers (fees “from data purchasers”), as well as subscribers to the models/access (monthly subscription model) — per the tokenomics.
Where fees go: part of the fees from data buyers is used to burn tokens; network fees — to BNB Chain validators.
Issuance/burn: total supply 1,000,000,000; burn is claimed as part of the model (“portion of the fee ... will be used to burn tokens”).
Security/incentive mechanisms: the main claimed mechanic is token rewards for data contributions; slashing/collateral are not described in the extracted Tier‑1.
Distribution and token issuance schedule: the tokenomics give a table of allocations/vesting (ecosystem growth 39%, investor 18%, Floki/TokenFi community airdrop 14%, TokenFi presale 10%, liquidity 5%, MM 2%, treasury 5%, team 5%, Floki trading bot 2%).
Treasury: Treasury allocation 5% (2 years runway) — per the tokenomics; the treasury management mechanism is not disclosed in the extracted Tier‑1.

Governance

Who makes decisions: DAO governance is mentioned in the ecosystem description; details (voting mechanics/venues) are not provided in the extracted Tier‑1.
How protocol parameters change: via the development of the protocol/platform per the roadmap; a formal governance process is not described.
Where decisions are discussed/made: the official GitBook documentation and the project’s channels (X/Telegram/Discord in the links of this card).
Keys/multisig: — (not found in the extracted Tier‑1)

Security and incidents

Audits: — (not found in the extracted Tier‑1)
Bug bounty: — (not found in the extracted Tier‑1)
Incidents: — (not found in the extracted Tier‑1)
Threat model: risks of data quality/authenticity (data poisoning), centralization risks of the offchain part (marketplace/storage), risks of the token smart contract and of incentive distribution.

Project status and timeline

Current status: the token on BNB Chain is on mainnet; the roadmap describes phases for 2025–2026.
Key releases/milestones: Phase 1 — RICE token (2025 Q3); Phase 3 — data marketplace (2025 Q4); Phase 4 — AI foundry + GPU sharing feature (2026 Q1) — per the roadmap.
Roadmap: https://rice-ai.gitbook.io/home/rice-protocol/development-roadmap

Ecosystem/integrations

Integrations: BNB Chain (token); the tokenomics claim a partnership with PancakeSwap (and Floki/DWF Labs are mentioned as token launch partners).
Partners: Floki, DWF Labs, PancakeSwap — claimed in the tokenomics (as a token launch partnership).
Where it’s actually used: the docs describe a usage model for the data marketplace and model subscriptions; specific production integrations/data buyers are not listed.

AI component of the project

What is real AI here? the project describes training robotics foundation models (“AI foundry”) and using the data to train AGI robots; the roadmap also mentions an “AI agent mini-game” and importing agent behavior into a physical robot.
What is truly onchain? the RICE token on BNB Chain and the related incentives/accounting; the data itself and model training — offchain.
Why is a token needed? rewards for providing data, subscription discounts/payments, burn mechanics via fees and governance token (per the tokenomics).
Red flags (based on the information found): AI‑washing — there are no model metrics/benchmarks in the extracted Tier‑1; onchain‑washing — the core ML and the data pipeline are offchain; token‑washing — it needs to be verified whether payments/discounts via the token are actually enforced and whether the burn mechanics are real.

DecAI Fit component summary

DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	medium	1
Onchain necessity	medium	1
Token necessity	high	3
Evidence	Tier‑1 present	2

Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

AI_0 (decision): 0
Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 1
Claim (one line): training of “in-house robotics foundation models” on the collected data and providing access to them via a subscription is claimed.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): this specifically describes an AI product (foundation models) and the associated access.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): no public demos/replicable examples of the foundation models or the foundry in operation were found in the extracted Tier‑1.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/development-roadmap
Why sufficient / why not (one line): the roadmap describes future releases, but contains no demos/repro steps in the extracted form.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: — (not found)
Context (version/date/how measured): — (not found)
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): the extracted Tier‑1 contain no benchmarks/quality metrics of the models or of the training process.
Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

AI_4 (decision): 0
Claim (one line): the extracted Tier‑1 contain a description of the goals and components (data marketplace, AI foundry, GPU sharing), but without technical specifications of the models/pipelines.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/development-roadmap
Why sufficient / why not (one line): the roadmap is not a technical description (no architecture/versions/limitations).
Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

OC_1 (decision): 1
Chain: BNB Smart Chain
Addresses/identifiers: 0xb5761f36FdFE2892f1b54Bc8EE8baBb2a1b698D3
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics ; https://bscscan.com/token/0xb5761f36fdfe2892f1b54bc8ee8babb2a1b698d3
Why sufficient / why not (one line): the docs give the CA, and BscScan confirms the contract and max total supply.
Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

OC_2 (decision): 0
What useful logic is onchain: the extracted Tier‑1 describe primarily the token economy and incentives; explicit onchain modules of the protocol (other than the token) are not described.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): the docs contain no addresses/descriptions of onchain contracts of the data protocol, only the token and the economic model.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: rewards/discounts/accounting can be implemented in a centralized way; the extracted Tier‑1 contain no argument that the system does not work without onchain.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): onchain is used for the token and incentives, but the irreplaceability of the blockchain is not proven in the extracted material.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a native token, RICE, on BNB Chain.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): the docs directly describe the token and its parameters (supply/CA).
Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

TK_1 (decision): 1
Claim (one line): the subscription for access to robotics foundation models is paid monthly; a discount is offered when paying with the native token.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): the docs directly describe the subscription model and the discount when paying with the token.
Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

TK_2 (decision): 1
Claim (one line): robotics data contributors receive token rewards; part of the fees from data buyers is used for burn (deflationary economy).
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): incentives and burn are described in the tokenomics.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 1
Claim (one line): the token is used as a governance token for the data collection protocol.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): the token’s governance utility is claimed in the documentation.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): the token is embedded in the core economy (rewards, burn from fees, subscription discount, governance), so it does not look easily replaceable without a design change.
Evidence: Tier‑1 — https://rice-ai.gitbook.io/home/rice-protocol/tokenomics
Why sufficient / why not (one line): the token’s utilities are described as components of the protocol economy.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://rice-ai.gitbook.io/home/background/introducing-rice-ai	positioning (a decentralized ecosystem for robotics/AGI) and the link to Rice Robotics; the funding claim.
Tier‑1	https://rice-ai.gitbook.io/home/rice-protocol/tokenomics	token utility (rewards/subscription discount/burn/governance), supply and CA, allocations/vesting.
Tier‑1	https://rice-ai.gitbook.io/home/rice-protocol/development-roadmap	the roadmap and release plan (data marketplace/AI foundry/GPU sharing).
Tier‑1	https://bscscan.com/token/0xb5761f36fdfe2892f1b54bc8ee8babb2a1b698d3	confirmation of the onchain token contract and max total supply.