Skip to main content

SentAI (BinoAI on IoTeX)

SentAI (BinoAI on IoTeX) — 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).

SentAI (BinoAI on IoTeX) — an AI/Agents project on the Solana network, token (symbol: —).

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: an autonomous AI agent that publishes/explains content about DePIN (described in the Tier‑1 IoTeX publication).
  • Who it’s for: participants of the DePIN ecosystem, developers, and the community.
  • Why onchain/token: the existence of an SPL token on Solana is confirmed; no Tier‑1 justification of the necessity of the token as a mandatory mechanism of the product was found.
  • What you can actually touch (Tier‑1): add the bot to Discord and address it via a mention (described in the Tier‑1 publication).

How it works (very briefly)

  1. The user does: adds the bot to Discord and asks questions.
  2. The system does: responds and publishes/shares knowledge on the topic of DePIN (claimed).
  3. The user gets: explanations/content and an “AI advocate” function in the community.
  4. Where the blockchain is: the Tier‑1 publication describes the integration of IoTeX blockchain functionality into an agent framework for access to on‑chain data; specific contract addresses/networks are not recorded in this card.
  5. Token role (if any): a specific utility/necessity of the token is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name SentAI (BinoAI on IoTeX)
Also known as (aliases) BinoAI, @Bino_AI
Logo (logo) ../assets/638_sentai-iotex_logo.webp
Token symbol (ticker) —
Category AI/Agents | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active
Token (standard) SPL
Token contract CXPLyc3EX8WySgEXLbjhuA7vy8EKQokVJYQuJm2jpump
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) — (the utility/necessity of the token is not confirmed by Tier‑1).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) autonomous AI agent for DePIN content
Use‑case (use_case) DePIN (Q&A + community content)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 1
Last verified 2026-02-11

General project overview

The Tier‑1 IoTeX publication describes BinoAI as an autonomous AI agent (DePIN AI advocate) that publishes and explains content about DePIN and can operate in Discord. It also describes the integration of IoTeX blockchain functionality into the open‑source agent framework ELIZA for access to on‑chain data.

Important: this card records an SPL token (per the explorer link in links_*), but the Tier‑1 link between the token and the described AI agent is not established (requires separate confirmation).

Features/modules

  • BinoAI AI agent: autonomous posts/responses on the topic of DePIN (Tier‑1).
  • Discord integration: the ability to add the bot to a conversation and address it via a mention (Tier‑1).
  • Integration with on‑chain data: integration of IoTeX functionality into the ELIZA framework is claimed (Tier‑1, via a GitHub PR).

Typical scenarios

  • Scenario 1: the user adds the bot to Discord → asks questions → receives answers/explanations about DePIN.
  • Scenario 2: the user follows the agent’s posts → receives updates/explanations about DePIN events (claimed).

Getting started (wallet/network)

  • What you need: Discord (for the bot) and/or X (for public posts).
  • Network/chain: Solana — if the user interacts with the token; IoTeX — mentioned as an on‑chain data integration in the Tier‑1 publication.
  • Fees: Solana fees arise only for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: the AI agent (Discord/X) + a token on Solana (as a separate onchain artifact).
  • Participant roles: users/the community, the team/operators.
  • Where logic runs: the AI part — offchain; onchain — the token.
  • Dependencies: Discord, X; the ELIZA agent framework (open source) and the IoTeX integration (per the Tier‑1 publication).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Protocol necessity drivers: No Tier‑1 justification of “why the token is mandatory for the product” was found.
  • Who pays fees: users for onchain operations on Solana.
  • Where fees go: to Solana validators (per the network rules).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of the quality/reliability of the AI agent’s answers; risks of the bot’s access/permissions in Discord; risks of the token as a separate onchain asset.

Project status and timeline

  • Current status: active (the Tier‑1 publication describes a “deployed” agent + connection instructions).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: Discord and X; integration of IoTeX functions into the ELIZA framework (Tier‑1).
  • Partners: —.
  • Where it’s actually used: the Discord bot can be connected and used per the Tier‑1 instructions.

AI component of the project

  • What is real AI here? Tier‑1 describes an autonomous AI agent that responds and publishes content on the topic of DePIN.
  • What is truly onchain? An SPL token on the Solana network; Tier‑1 also mentions the integration of IoTeX onchain data into the agent framework.
  • Why is a token needed? Not established per Tier‑1.
  • Red flags (based on the information found): no Tier‑1 description of the token utility; no quality metrics of the agent; possible ambiguity of the “AI agent ↔ token” link without separate Tier‑1 confirmation.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as an already working agent (not only intent).
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): The publication describes a “deployed” AI agent and how to use it.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The autonomous AI agent publishes and explains content about DePIN and interacts with users.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the role and tasks of the agent.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): Tier‑1 has an instruction: add the bot to Discord and address it in the chat.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): This is a reproducible “demo surface” (the Discord bot).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): The publication describes the purpose, but contains no quality metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): It is described that the agent is built on the open‑source ELIZA framework and that there is an integration of IoTeX functions via a GitHub PR.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): Tier‑1 contains a specific technical context (the framework + a link to the PR).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint CXPLyc3EX8WySgEXLbjhuA7vy8EKQokVJYQuJm2jpump
  • Evidence: Tier‑1 — https://solscan.io/token/CXPLyc3EX8WySgEXLbjhuA7vy8EKQokVJYQuJm2jpump
  • Why sufficient / why not (one line): There is an onchain artifact (a token on Solana).
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 (other than the token); the mention of IoTeX onchain data access contains no addresses/contracts.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): Specific onchain addresses/mechanics are needed; the publication does not provide them.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality was found.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): There are general claims about trustless environments, but no formal criticality test.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an SPL token on the Solana network (the mint is given in links_*).
  • Evidence: Tier‑1 — https://solscan.io/token/CXPLyc3EX8WySgEXLbjhuA7vy8EKQokVJYQuJm2jpump
  • Why sufficient / why not (one line): The existence of the mint confirms the existence of the token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): Payment for the service with the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): The publication describes the AI agent and the integration, but not the utility of the token as a payment.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties on the token are not established per Tier‑1.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): There is no description of incentive/collateral/penalty mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): Tier‑1 has no description of a DAO/voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/
  • Why sufficient / why not (one line): There is no specification of “what breaks down without the token”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://iotex.io/blog/binoai-the-first-depin-ai-agent-on-iotex/ Description of the autonomous AI agent BinoAI, the Discord integration, and the technical context (ELIZA + GitHub PR).
Tier‑1 https://github.com/ai16z/eliza/pull/1009 PR: integration of IoTeX blockchain functionality into the ELIZA framework (access to on‑chain data), as described in the Tier‑1 IoTeX publication.
Tier‑1 https://solscan.io/token/CXPLyc3EX8WySgEXLbjhuA7vy8EKQokVJYQuJm2jpump The existence of the token on the Solana network (SPL mint).
Tier‑1 — No Tier‑1 source for claim “why the token is necessary as a mandatory mechanism of the product” was found.

No comments to display

Back to top