Skip to main content

SKYAI

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

SKYAI — an AI/Other | Infra project on BNB Smart Chain: it claims an “extended MCP” and aggregated onchain data services so that AI/LLM clients can more easily read/use blockchain data. Token: SKYAI (BEP‑20).

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 project about “MCP” and onchain data (the website claims an “extended MCP” and “aggregated on‑chain data services”), but without public Tier‑1 documentation/a repository in links_*.
  • Who it’s for: potentially developers of AI agents/tools and teams that need access to structured onchain data (as claimed).
  • Why onchain/token: the SKYAI token on BNB Smart Chain is confirmed onchain; the necessity of the token for the service was not extracted per Tier‑1.

How it works (very briefly)

  1. The user does: (by design) requests onchain data/analytics via an MCP‑compatible client or integration.
  2. The system does: aggregates/normalizes onchain data and returns it in a format convenient for LLMs/agents (implementation details per Tier‑1 are not published in links_*).
  3. The user gets: structured onchain data/answers/tools for automation (as claimed).
  4. Where the blockchain is: the SKYAI token (BEP‑20) and all verification of the contract/supply — onchain; the addresses of the “MCP protocol” on the network are not specified in Tier‑1.
  5. Token role: the existence of the token is confirmed; utility/fees/governance were not found in Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name SKYAI
Also known as (aliases) SKY.AI
Logo (logo) ../assets/58_skyai_logo.png
Token symbol (ticker) SKYAI
Category AI/Other | 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 0x92aa03137385F18539301349dcfC9EbC923fFb10
Token model (token_type) —
Max supply 1,000,000,000
Issuance fixed cap
Tokenomics (tokenomics, brief) max total supply 1B (BscScan); the token’s utility was not extracted from Tier‑1.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) extended MCP + aggregated on-chain data
Use‑case (use_case) AI agents (access to on-chain data)
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

SKYAI is positioned as an infrastructure project that “bridges AI to the blockchain” via MCP and aggregated onchain data services. The meta description on the official website explicitly states: “Extended MCP and aggregated on‑chain data services”.

At the same time, links_* contains no Tier‑1 documentation, GitHub or changelog, so as of Last verified the project is assessed conservatively: the intent/positioning is recorded, but the technical details, demo/quickstart and the role of the token in the protocol are not confirmed by Tier‑1.

Features/modules

  • Extended MCP (claimed): MCP compatibility/extension for AI tools (as claimed).
  • Aggregated on-chain data services (claimed): aggregation/delivery of onchain data for AI/LLMs (as claimed).
  • SKYAI token (BEP‑20): an onchain fact (contract on BNB Smart Chain, max supply 1B).

Typical scenarios

  • Scenario 1 (developer): connect an MCP‑compatible client → receive aggregated onchain data → use it in an AI agent (as claimed; a Tier‑1 quickstart/SDK is needed).
  • Scenario 2 (user): use a ready‑made AI agent/interface for queries/analytics on onchain data (as claimed; no Tier‑1 demo was found in links_*).

Getting started (wallet/network)

  • What you need: — (no Tier‑1 guide/quickstart was found in links_*).
  • Network/chain: BNB Smart Chain (per the token on BscScan).
  • Fees: BNB gas for token operations; SKYAI protocol commissions/fees — not extracted.

Architecture/tech (non‑AI)

  • Components: the token contract is publicly confirmed; the MCP/data aggregation components are mentioned, but without a technical description/repository in links_*.
  • Participant roles: token users; potentially — data providers and developers of clients/agents (as claimed).
  • Where logic runs: presumably offchain (data aggregation/LLM clients); onchain, only the token is confirmed.
  • Dependencies: BNB Smart Chain; other dependencies (indexers/storage/orchestration) — not disclosed in Tier‑1.

Token/economics (expanded, no forecasts)

  • Token utility: — (no Tier‑1 description of utility/fees/governance was found).
  • Protocol necessity drivers: — (cannot be confirmed without docs/a whitepaper).
  • Who pays fees: —.
  • Where fees go: —.
  • Issuance/burn: max total supply 1B (BscScan); the rest — not extracted.
  • 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: — (not found in links_*/Tier‑1).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: the risks of a typical BEP‑20 token/contract (approvals/compromise of the owner’s keys, etc.); without docs, the risks of the MCP infrastructure cannot be assessed.

Project status and timeline

  • Current status: the website is active; the token on BNB Smart Chain is active.
  • Key releases/milestones: — (no Tier‑1 changelog/release in links_*).
  • Roadmap: — (links_* shows —).

Ecosystem/integrations

  • Integrations: — (no Tier‑1 integrations/SDK were found).
  • Partners: —.
  • Where it’s actually used: — (apart from the fact that the token exists).

AI component of the project

  • What is real AI here? per Tier‑1, only the positioning is confirmed (MCP + onchain data “for AI”); there are no technical details/demo/metrics at the Tier‑1 level in links_*.
  • What is truly onchain? the SKYAI token (BEP‑20) on BNB Smart Chain; no other “protocol” contracts/addresses are specified in Tier‑1.
  • Why is a token needed? per Tier‑1, no description of the token’s utility (fees/access/governance) was found.
  • Red flags (based on the information found): AI‑washing — high risk (no Tier‑1 technical description/demo/SDK); onchain‑washing — risk (no onchain artifacts other than the token); token‑washing — risk (utility not confirmed). What to double‑check: Tier‑1 docs/repository/quickstart, the addresses of protocol contracts (if any), an explicit role of the token.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the official website claims an “Extended MCP” and “aggregated on-chain data services” for linking AI↔blockchain.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): this is a Tier‑1 declaration of direction (intent) without technical details/a demo.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): Tier‑1 has no description of a specific AI function/models/pipelines; only positioning.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): without a technical description/SDK/examples, one cannot state “what exactly the AI does”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo/quickstart/SDK for MCP/data was found in links_*.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): without a reproducible demo/guide, AI_2=0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): metrics/benchmarks are not published in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is no public Tier‑1 documentation/architecture of the MCP/data in links_*.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): without docs/a repo we record 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: token contract 0x92aa03137385F18539301349dcfC9EbC923fFb10
  • Evidence: Tier‑1 — https://bscscan.com/token/0x92aa03137385F18539301349dcfC9EbC923fFb10
  • Why sufficient / why not (one line): the contract address and basic parameters are 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: no MCP/data addresses/contracts were found in Tier‑1; only the token is confirmed.
  • Evidence: Tier‑1 — https://skyai.pro, https://bscscan.com/token/0x92aa03137385F18539301349dcfC9EbC923fFb10
  • Why sufficient / why not (one line): without protocol addresses we set 0 (conservatively).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without a Tier‑1 description of the onchain part (other than the token), it cannot be proven that the product breaks down without a blockchain.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): we record 0 until a Tier‑1 technical description/contracts appear.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, SKYAI (BEP‑20).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x92aa03137385F18539301349dcfC9EbC923fFb10
  • Why sufficient / why not (one line): the token contract is confirmed onchain.
  • 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): no payment role of the token was found in Tier‑1.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): without docs/terms we record 0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): no Tier‑1 incentives/staking/collateral were found.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): we record 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): no governance role of the token was found in Tier‑1.
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): we record 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): without a Tier‑1 description of the utility, we do not draw a conclusion about replaceability (conservatively 0).
  • Evidence: Tier‑1 — https://skyai.pro
  • Why sufficient / why not (one line): insufficient data.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://skyai.pro Tier‑1: the project’s positioning (“extended MCP”, “aggregated on‑chain data services”).
Tier‑1 https://bscscan.com/token/0x92aa03137385F18539301349dcfC9EbC923fFb10 Tier‑1: the onchain fact of the SKYAI token (BEP‑20), max total supply 1B, holders.
Tier‑1 https://t.me/SKYAI_MCP Tier‑1: the project’s official channel/communication (existence, without verification of individual claims).
Tier‑1 — No Tier‑1 docs/SDK/quickstart/repository on MCP and aggregated data was found (not confirmed by Tier‑1).
Tier‑2 https://www.coindesk.com/press-release/2025/04/24/skyai-launches-groundbreaking-mcp-protocol-igniting-web3-ai-revolution-with-unprecedented-data-liquidity-and-simplified-blockchain-access Context: PR material with extended claims (not a Tier‑1 source for technical details).
Tier‑2 https://bsc.news/post/sky-ai Context: an overview/retelling of the claims (not Tier‑1).
Tier‑2 https://linktr.ee/SKYAIpro Context: the project’s link aggregator (not Tier‑1).
Tier‑3 — —

No comments to display

Back to top