Skip to main content

AI21X

AI21X — 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).

AI21X — an AI/Other project on the BNB Smart Chain 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: only the onchain fact of the BEP‑20 token’s existence is confirmed per Tier‑1; a description of the product is not established.
  • Who it’s for: not established (no Tier‑1).
  • Why onchain/token: onchain = issuance/accounting/transfers of the token on the BNB Smart Chain network; the role of the token in the product is not established.

How it works (very briefly)

  1. The user does: interacts with the token (receiving/transferring/holding).
  2. The system does: the BNB Smart Chain network records the contract state and transactions.
  3. The user gets: onchain confirmation of ownership/transfers.
  4. Where the blockchain is: the token contract and operations with it — onchain on BNB Smart Chain.
  5. Token role (if any): not established (no Tier‑1 description of utility/necessity).

Quick links: AI thesis fit

Project passport

Field Value
Project name AI21X
Also known as (aliases) —
Logo (logo) ../assets/883_ai21x_logo.png
Token symbol (ticker) —
Category AI/Other
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) —
Token (standard) BEP-20
Token contract 0xA2171868C06e578ffF91fDfD186b22A3dF3fF2C7
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) unknown
Use‑case (use_case) unknown
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 1 / 0 / 1
Last verified 2026-02-11

General project overview

Only the onchain fact of the BEP‑20 token’s existence on the BNB Smart Chain network is confirmed per Tier‑1 sources. A Tier‑1 description of the product, the AI component and the role of the token in the product is not established.

Features/modules

  • Not established (no Tier‑1 description of the product).

Typical scenarios

  • Not established (no Tier‑1 description of the product).

Getting started (wallet/network)

  • What you need: an EVM wallet that supports BNB Smart Chain.
  • Network/chain: BNB Smart Chain.
  • Fees: BNB Smart Chain network fees for transfers/operations.

Architecture/tech (non‑AI)

  • Components: the token contract on the BNB Smart Chain network.
  • Participant roles: token holders and participants of the BNB Smart Chain network.
  • Where logic runs: accounting/transfers of the token — onchain on BNB Smart Chain.
  • Dependencies: BNB Smart Chain RPC/wallets/infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: not established (no Tier‑1).
  • Protocol necessity drivers: not established (no Tier‑1).
  • Who pays fees: users of the BNB Smart Chain network.
  • Where fees go: to the BNB Smart Chain network validators (per the network rules).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks are typical for tokens and wallet/RPC infrastructure; without a Tier‑1 description of the product, the threat model is not established.

Project status and timeline

  • Current status: mainnet (based on the fact of the token’s existence on the network).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? not established (no Tier‑1 description of an AI component).
  • What is truly onchain? the token contract on the BNB Smart Chain network (contract and transactions — onchain).
  • Why is a token needed? not established (no Tier‑1 description of utility/necessity).
  • Red flags (based on the information found): AI labels without a Tier‑1 tech description/demo/metrics; reducing the “onchain part” to token issuance; absence of verifiable product artifacts.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality no Tier‑1 data 0
Onchain necessity low (token only) 1
Token necessity not established 0
Evidence partial Tier‑1 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 declaration of AI intent was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no verifiable Tier‑1 artifact with an AI roadmap/intent.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): what exactly the AI does is not established (no Tier‑1 description).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 description of the AI feature, we set 0.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): demos/examples of the AI in operation were not found in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no Tier‑1 demo/example → 0.
  • 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 — —
  • Why sufficient / why not (one line): no Tier‑1 metrics/context → 0.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the tech description/architecture of the AI component was not found in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 tech description, we set 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: 0xA2171868C06e578ffF91fDfD186b22A3dF3fF2C7
  • Evidence: Tier‑1 — https://bscscan.com/token/0xA2171868C06e578ffF91fDfD186b22A3dF3fF2C7
  • Why sufficient / why not (one line): the onchain fact of the token contract is confirmed by the explorer.
  • 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).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no Tier‑1 addresses/description of onchain logic other than the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established (no Tier‑1 description of the product).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 justification of criticality, we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the token exists (BEP‑20 on BNB Smart Chain).
  • Evidence: Tier‑1 — https://bscscan.com/token/0xA2171868C06e578ffF91fDfD186b22A3dF3fF2C7
  • Why sufficient / why not (one line): the token is identified by the contract address.
  • 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): not established (no Tier‑1 description of payment utility).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 description of utility, we set 0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): not established (no Tier‑1).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description of incentives/collateral.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): not established (no Tier‑1).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description of governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): not established (no Tier‑1 allowing replaceability to be assessed).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): with insufficient data, we set 0 (conservatively).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://bscscan.com/token/0xA2171868C06e578ffF91fDfD186b22A3dF3fF2C7 The BEP‑20 token contract address on the BNB Smart Chain network (onchain fact).
Tier‑1 https://ai21x.ai/ The presence of an official website (without a sufficient Tier‑1 description of AI/utility).
Tier‑1 — No Tier‑1 source for claim “what is real AI here” was found.
Tier‑1 — No Tier‑1 source for claim “why is a token needed (utility/necessity)” was found.
Tier‑2 https://coinmarketcap.com/currencies/ai21x/ Reference token profile (metadata, links).

No comments to display

Back to top