CryptoAI
CryptoAI — 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).
CryptoAI — a project with claimed AI bots/tools; a token on the Ethereum network.
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 set of claimed bots/tools (Telegram/web) for tasks around crypto communities.
- Who it’s for: users and communities that need such tools.
- Why onchain/token: onchain — token circulation and a verifiable contract address; the necessity of the token for the product requires re‑checking per Tier‑1.
How it works (very briefly)
- The user does: interacts with a bot/web interface.
- The system does: performs the claimed function (bot/tool); details of the AI part are not confirmed by Tier‑1 artifacts.
- The user gets: the result of the tool’s operation (claimed on the website).
- Where the blockchain is: the ERC‑20 token and its contract on Ethereum.
- Token role (if any): the token is used in the ecosystem (claimed); the strict necessity of the token for the functions is not established.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | CryptoAI |
| Also known as (aliases) | CAI, Crypto AI |
| Logo (logo) | ../assets/751_cryptoai_logo.bin |
| Token symbol (ticker) | CAI |
| Category | AI/Other | Consumer |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0xf36c5f04127f7470834ed6f98bddc1be62aba48d |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | utility/access in the ecosystem (as claimed) |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI bots/tools |
| Use‑case (use_case) | bots/tools for communities |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 1 / 0 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://crypto-ai.io |
| Docs | https://cryptoai.gitbook.io/cryptoai-whitepaper-v.1.0/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://cryptoai.gitbook.io/cryptoai-whitepaper-v.1.0 |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xf36c5f04127f7470834ed6f98bddc1be62aba48d |
| X | https://twitter.com/cryptoai_erc |
| Discord | — |
| Telegram | https://t.me/cryptoai_erc |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/cryptoai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cryptoai/ |
General project overview
Per Tier‑1 sources, the project positions a set of bots/tools (including for Telegram) and links access/privileges to token ownership. No confirmation of specific AI models/metrics and protocol necessity of the onchain part, other than the token, was found.
Features/modules
- Claimed bots/tools for tasks around crypto communities.
- Access/privilege mechanics via the token (claimed).
Typical scenarios
- Scenario 1: a user launches a bot in Telegram and gets the claimed function.
- Scenario 2: a user uses the web interface (if available) for the claimed tools.
Getting started (wallet/network)
- What you need: an EVM wallet for interacting with the ERC‑20 token.
- Network/chain: Ethereum.
- Fees: Ethereum network fees for onchain operations.
Architecture/tech (non‑AI)
- Components: an ERC‑20 token on Ethereum + offchain services/bots (details not established).
- Where logic runs: key functions — offchain; onchain — the token and its contract.
Token/economics (expanded, no forecasts)
- Token utility: benefits/access for token holders are claimed.
- Necessity of the token: no technical justification of “why it is impossible without the token” was found in Tier‑1 sources.
Governance
- Not established per Tier‑1 sources.
Security and incidents
- Audits/bug bounty/incidents: not established per Tier‑1 sources.
Project status and timeline
- Current status: active (based on the availability of official channels/pages).
- Roadmap: —.
Ecosystem/integrations
- Not established per Tier‑1 sources.
AI component of the project
- What is real AI here? AI bots/tools are claimed, but no Tier‑1 confirmation of a specific model/metrics/architecture was found.
- What is truly onchain? The ERC‑20 token and its contract on Ethereum.
- Why is a token needed? The use of the token for access/privileges and operations in the ecosystem is claimed; protocol necessity requires Tier‑1 confirmation.
- Red flags (based on the information found): there is no public Tier‑1 artifact with metrics/model versions; there is no repository/releases; the onchain part appears limited to the token.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium 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 | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): AI bots/tools are claimed on the official website.
- Evidence: Tier‑1 — https://crypto-ai.io
- Why sufficient / why not (one line): this confirms intent/positioning, but does not prove a specific AI component and its quality.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): no sufficient Tier‑1 description of a specific AI feature/model was found (in terms of “what exactly the AI does”).
- Evidence: Tier‑1 — https://cryptoai.gitbook.io/cryptoai-whitepaper-v.1.0/
- Why sufficient / why not (one line): without a clear description of the AI part we set 0 (conservatively).
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): a public demo of AI features, verifiable without assumptions, is not established.
- Evidence: Tier‑1 — https://crypto-ai.io
- Why sufficient / why not (one line): in the absence of a verifiable demo, we set 0 (conservatively).
- 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): without numerical metrics and context we set 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): no tech description of the AI component with versions/architecture was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a tech description, we set 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: 0xf36c5f04127f7470834ed6f98bddc1be62aba48d
- Evidence: Tier‑1 — https://etherscan.io/token/0xf36c5f04127f7470834ed6f98bddc1be62aba48d
- Why sufficient / why not (one line): the token contract address and the network are verifiable via 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 (other than the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 confirmation of onchain logic beyond the token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that the product breaks down without the blockchain.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a justification of onchain criticality, we set 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, CAI (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0xf36c5f04127f7470834ed6f98bddc1be62aba48d
- Why sufficient / why not (one line): the existence of the token is verifiable via the explorer.
- 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 Tier‑1 confirmation of mandatory payment for services with the token was found.
- Evidence: Tier‑1 — https://cryptoai.gitbook.io/cryptoai-whitepaper-v.1.0/
- Why sufficient / why not (one line): in the absence of an explicit mechanism for payment with the token we set 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): no Tier‑1 description of incentives/collateral/penalties at the protocol level was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without incentive/collateral mechanics we set 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): no Tier‑1 confirmation of governance via the token was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a description of governance, we set 0.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): per the Tier‑1 description, the token appears to be an access/privilege mechanism that could also be implemented without the token.
- Evidence: Tier‑1 — https://crypto-ai.io
- Why sufficient / why not (one line): Tier‑1 does not explain why access must be specifically via the token, so we set “replaceable”.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://crypto-ai.io | Official project positioning; intent regarding AI bots/tools; claims about the role of the token. |
| Tier‑1 | https://cryptoai.gitbook.io/cryptoai-whitepaper-v.1.0/ | Documentation/whitepaper (Tier‑1) as a source of claims about the product and token. |
| Tier‑1 | https://etherscan.io/token/0xf36c5f04127f7470834ed6f98bddc1be62aba48d | The network and token contract address (onchain fact). |
| Tier‑2 | https://www.coingecko.com/en/coins/cryptoai | Reference token profile (context). |
| Tier‑2 | https://coinmarketcap.com/currencies/cryptoai/ | Reference token profile (context). |
No comments to display
No comments to display