Skip to main content

OlaXBT

OlaXBT (AIO) — 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).

OlaXBT / OLAXBT — an AI/Agents | DeFi | Infra project: a “decentralized AI trading layer” with a chat interface, an MCP marketplace and “MCP Space” (no‑code assembly of trading agents, an RL approach is claimed). Token: AIO (BEP‑20, BNB Smart Chain).

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 trading “terminal/chat interface” and a set of modules that give the user signals/analytics (technical analysis, whale tracking, news, KOL sentiment) and allow assembling custom agent workflows.
  • Who it’s for: traders and users who want a “chat interface” for market information; creators of their own agent configurations (drag‑and‑drop).
  • Why onchain/token: the AIO token on BNB Smart Chain is confirmed onchain; per the tokenomics, the token is used as payment/access to MCP servers/agents and features (premium signals, vaults, etc.).
  • What you can actually touch (Tier‑1): the chat interface + free trial credits (guide in the docs).

How it works (very briefly)

  1. The user does: connects a wallet and uses the chat interface (or the Telegram bot) for modular trading tools.
  2. The system does: AI agents aggregate signals (onchain metrics + macro + sentiment) and return answers/insights; in MCP Space the user assembles their own agents from MCP modules (claimed).
  3. The user gets: signals/analytics, notifications and personalized plans/insights (depending on the configuration).
  4. Where the blockchain is: the AIO token is onchain on BNB Smart Chain; additional onchain contracts of the product (other than the token) are not confirmed in Tier‑1 sources.
  5. Token role: per the tokenomics, the token is used for payment/access to the MCP ecosystem and features (premium signals, agent vault, agent creation/customization).

Quick links: AI thesis fit

Project passport

Field Value
Project name OlaXBT
Also known as (aliases) OLAXBT | AIO NEXUS | OlaXBT Terminal | AIO
Logo (logo) ../assets/67_olaxbt_logo.png
Token symbol (ticker) AIO
Category AI/Agents | DeFi | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0x81a7DA4074b8e0eD51beA40f9dCbDF4d9d4832b4
Token model (token_type) utility (MCP access + signals + vaults)
Max supply 1,000,000,000
Issuance fixed
Tokenomics (tokenomics, brief) total supply 1B; allocation 71% ecosystem/community, 29% team+investors; token utility: MCP access + premium features.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) reinforcement-learning trading agents + MCP marketplace
Use‑case (use_case) AI trading terminal + no-code agent builder
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

In its documentation, OlaXBT describes itself as a “decentralized AI trading layer” with an MCP marketplace and the AIO NEXUS product (“Web3 financial data layer”). As described, the system aggregates onchain metrics and community sentiment to give users “real‑time alpha” and modular trading tools via a chat interface.

Key user entry points described in Tier‑1:

  • Chat Interface (web) and Telegram bot, where modular features are available (token analysis, support/resistance, whale waves, news loop, KOL tweets).
  • MCP Space, where the user can assemble their own trading agent from MCP modules (drag‑and‑drop) and interact with it via web/Telegram; RL adaptation of the agent’s behavior is claimed.

Features/modules

  • Chat Interface: modular tools (technical analysis, whale tracking, news, KOL sentiment) in the chat.
  • MCP Space: no‑code assembly of an agent from MCP modules + interaction via Telegram/web; RL adaptation is claimed.
  • Token utility: access/payment for the MCP ecosystem, premium signals, agent vault, agent creation/customization (Tier‑1 tokenomics).

Typical scenarios

  • Scenario 1 (trader): connects a wallet → takes free trial credits → asks questions in the chat interface → receives signals/insights.
  • Scenario 2 (user): assembles an agent in MCP Space (drag‑and‑drop MCPs) → receives personalized plans/insights.
  • Scenario 3 (power user): uses the token for access to premium signals/agent vault and other features (claimed).

Getting started (wallet/network)

  • What you need: web access to olaxbt.xyz or the Telegram bot; a compatible wallet to connect.
  • Network/chain: BNB Smart Chain (the AIO token).
  • Fees: the docs describe a credits top‑up: 0.001 BNB for 100 credits (after the free trial); plus the usual network fees for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: web chat interface + Telegram bot; MCP Space (agent builder portal); MCP modules (data sources/tools) (Tier‑1 docs).
  • Participant roles: users (consumers of signals/insights), creators of agent configurations.
  • Where logic runs: data aggregation/inference — offchain (claimed); the onchain layer is confirmed via the AIO token on BSC.
  • Dependencies: onchain data sources (claimed), KOL sentiment, Dune Analytics as an MCP source (claimed).

Token/economics (expanded, no forecasts)

  • Token utility: MCP ecosystem access (payment), agent vault access, premium signals, fee discounts, agent creation/customization (Tier‑1 tokenomics).
  • Protocol necessity drivers: the token is directly described as a payment/access token for the MCP server/agents and a number of features (Tier‑1 tokenomics).
  • Who pays fees: users (BSC transactions, credits top‑up).
  • Where fees go: — (not described).
  • Issuance/burn: total supply 1B (fixed).
  • Security/incentive mechanisms: rewards for data/chat contributions (claimed); staking options are mentioned for the agent vault (roadmap/tokenomics).
  • Distribution and token issuance schedule: the tokenomics include allocation and vesting for team/investors/treasury/rewards.
  • Treasury: an ecosystem treasury is mentioned (allocation 20%).

Governance

  • Who makes decisions: — (no Tier‑1 governance mechanics were found).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: no Tier‑1 audit reports were found.
  • Bug bounty: no Tier‑1 found.
  • Incidents: —.
  • Threat model: the risk of marketing claims without reproducible artifacts/code, the risk of centralized offchain inference, and the need to separately verify whether the token is a mandatory element of the product.

Project status and timeline

  • Current status: active (documentation and product pages are available; the token exists on BSC).
  • Key releases/milestones: — (no GitHub releases/changelog found).
  • Roadmap: Product Roadmap in Gitbook (Tier‑1).

Ecosystem/integrations

  • Integrations: web chat interface + Telegram bot; MCP modules for data sources (e.g., Dune Analytics) (Tier‑1).
  • Partners: —.
  • Where it’s actually used: product descriptions and guides in Gitbook (Tier‑1).

AI component of the project

  • What is real AI here? AI agents for trading analytics/signals and “reinforcement learning” for adaptive agents in MCP Space (Tier‑1 docs).
  • What is truly onchain? the AIO token (BEP‑20) on BNB Smart Chain is confirmed; other onchain contracts of the protocol are not confirmed in Tier‑1.
  • Why is a token needed? per the tokenomics — payment/access to MCP servers/agents, premium signals, agent vault and agent creation/customization.
  • Red flags (based on the information found): AI‑washing (RL/patents without code), onchain‑washing (onchain boils down to the token), token‑washing (verify whether the token is actually mandatory for the features).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as a current part of the product (AI agents), not as an “intent”.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc
  • Why sufficient / why not (one line): the intent flag is not needed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI agents provide modular trading tools (signals/analytics), aggregating onchain data and sentiment.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc , https://olaxbt-docs.gitbook.io/olaxbt-doc/core-product-suite/chat-interface
  • Why sufficient / why not (one line): Tier‑1 describes the function of the AI agents.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a reproducible guide to using the chat interface with free trial credits.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc/core-product-suite/chat-interface
  • Why sufficient / why not (one line): this is Tier‑1 “what you can touch” (app entry + steps).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc
  • Why sufficient / why not (one line): there are no reproducible quality metrics/benchmarks in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): MCP Space and the MCP layer are described (modular MCP tools + agent builder portal; an RL approach is claimed).
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc/core-product-suite/mcp-space , https://olaxbt-docs.gitbook.io/olaxbt-doc/technical-architecture/the-mcp-layer
  • Why sufficient / why not (one line): there is an architectural description of the AI/agent layer (high‑level).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain.
  • Addresses/identifiers: the AIO token (BEP‑20) 0x81a7DA4074b8e0eD51beA40f9dCbDF4d9d4832b4.
  • Evidence: Tier‑1 — https://bscscan.com/address/0x81a7DA4074b8e0eD51beA40f9dCbDF4d9d4832b4
  • Why sufficient / why not (one line): the explorer confirms the token contract.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: Tier‑1 sources do not confirm onchain contracts of the product other than the token.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc
  • Why sufficient / why not (one line): the descriptions of “on-chain analytics” give no specific contracts/addresses.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the key functions (chat/agents/data) can exist offchain; onchain criticality is not proven by Tier‑1.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc
  • Why sufficient / why not (one line): without Tier‑1 proof, OC_3=0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, AIO (BEP‑20), on BSC.
  • Evidence: Tier‑1 — https://bscscan.com/address/0x81a7DA4074b8e0eD51beA40f9dCbDF4d9d4832b4
  • Why sufficient / why not (one line): the onchain fact of the token is confirmed.
  • 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 token acts as the payment token for using MCP servers/toolkits/agents; also API discounts.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/tokenomic
  • Why sufficient / why not (one line): the tokenomics explicitly state the payment/access role.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): rewards for data/chat contributions and access to vault/staking features are described as part of the utility.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/tokenomic
  • Why sufficient / why not (one line): the tokenomics record rewards and agent vault access.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not described in Tier‑1 (there is “De‑Voting” in the roadmap without mechanics).
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/product-road-map
  • Why sufficient / why not (one line): without explicit governance mechanics we keep 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is claimed as the payment/access mechanism of the MCP ecosystem, so “full replaceability” is not proven.
  • Evidence: Tier‑1 — https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/tokenomic
  • Why sufficient / why not (one line): without an alternative payment mechanism in Tier‑1, we consider replaceability unproven.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc project overview (AI trading layer, AIO NEXUS, MCP marketplace).
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc/core-product-suite/chat-interface demo/guide for accessing the chat interface (wallet + free trial credits + top up).
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc/core-product-suite/mcp-space description of MCP Space (drag‑and‑drop agent assembly, RL claims).
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc/technical-architecture/the-mcp-layer description of the MCP layer and the agent builder portal (high‑level architecture).
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/tokenomic tokenomics: supply 1B, allocation/vesting, utility (payments/access/rewards).
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/product-road-map roadmap by quarters post‑TGE and the set of features.
Tier‑1 https://bscscan.com/address/0x81a7DA4074b8e0eD51beA40f9dCbDF4d9d4832b4 the onchain fact of the AIO token (BEP‑20) on BSC.
Tier‑1 https://olaxbt-docs.gitbook.io/olaxbt-doc/project-info/official-links official links (Telegram bot/community, MiCAR WP, nexus).

No comments to display

Back to top