Skip to main content

Cryptify AI

Cryptify AI (CRAI) — 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).

Cryptify AI positions itself as an AI/Big Data product for measuring the effectiveness of influencer marketing (KOL) and “causation analysis” between social media and onchain token metrics. Per Tier‑1 sources, there is a technical description of the approaches (causal inference, NLP/sentiment, topic modeling) and the $CRAI token utility is described.

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 analytics dashboard/platform for Web3/Web2 marketing to assess the impact of KOL posts on token metrics/price.
  • Who it’s for: teams/projects that spend budget on KOLs and want to measure the effect and ROI.
  • Why onchain/token: onchain data is used as measurable metrics; the $CRAI token — access/payment for packages, incentives and governance (per the whitepaper).

How it works (very briefly)

  1. The user does: selects a KOL/ticker/campaign and launches the analysis in the dashboard.
  2. The system does: collects social signals and onchain events/metrics and estimates the causal effect (causal inference) + adds ML/NLP analytics.
  3. The user gets: reports/scoring/insights for managing marketing and comparisons.
  4. Where the blockchain is: onchain metrics serve as observable data; the $CRAI token also exists on the blockchain.
  5. Token role (if any): the token is used for access/payment and participation in community governance and rewards.

Quick links: AI thesis fit

Project passport

Field Value
Project name Cryptify AI
Also known as (aliases) CRAI
Logo (logo) —
Token symbol (ticker) CRAI
Category AI/Other | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (based on the presence of the website/whitepaper/contract)
Token (standard) ERC-20
Token contract 0xDdbcDD8637d5CEDd15EeEe398108FCa05A71b32b
Token model (token_type) utility (access + payments + rewards + governance)
Max supply 1,000,000,000
Issuance fixed
Tokenomics (tokenomics, brief) access to the dashboard and paid packages; rewards and governance (per the whitepaper)
Governance company + token governance (per the whitepaper)
Admins/keys —
Audit — (in the whitepaper — a plan/intent of audits)
Bug bounty —
Team (team) —
Funding (investors/funding) project fully funded by founders (per the whitepaper)
AI component (ai_component) causal inference + NLP analytics
Use‑case (use_case) measuring impact of KOL campaigns
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 3 / 3
Last verified 2026-02-11

General project overview

Cryptify AI describes its product as a dashboard for Web3/Web2 companies that helps measure the effectiveness of influencer marketing not by indirect metrics (likes/reach), but through an attempt to show the causal relationship between social media activity and the token’s onchain indicators (price/volume/volatility, etc.). The whitepaper describes both the business positioning and the analytical methods used (causal inference + NLP, etc.).

Features/modules

  • KOL insights and analysis of activity/effect (per the product pages/whitepaper).
  • Causation analysis (counterfactual models/Bayesian uncertainty estimates; CRAI score — per the tech description).
  • NLP modules: sentiment analysis and topic modeling (BERTopic — per algorithms & analytics).
  • Token mechanics of access and paid “search packages” (per the token utility).

Typical scenarios

  • Scenario 1: a project team selects a KOL → views the estimate of the historical effect of posts on the token (by metrics).
  • Scenario 2: the team compares campaigns/competitors → adjusts budget/tactics based on causal impact data.

Getting started (wallet/network)

  • What you need: an account/access to the product (per the website) and an EVM wallet for interacting with the $CRAI token (if token gating/payment is used).
  • Network/chain: Ethereum (ERC‑20 token).
  • Fees: Ethereum gas for onchain operations with the token; the cost of packages/searches is paid/accounted in $CRAI (per the token utility).

Architecture/tech (non‑AI)

  • Components: web product (dashboard) + backend data collection/aggregation (social media and onchain) + analytical layer; ERC‑20 token.
  • Participant roles: users (marketing/teams), KOLs (as sources of events), data providers (social media/RPC/explorers).
  • Where logic runs: analytics/ML — offchain; onchain — the token and the metrics used (price/volume/transactions as data).
  • Dependencies: social data sources + onchain data sources (RPC/indexers), external exchange/price data (as input for the model; per the description).

Token/economics (expanded, no forecasts)

  • Token utility: access to dashboard features (token gating) and purchase of “search packages”; participation in governance; rewards/incentives (per the token utility).
  • Protocol necessity drivers: the token is used as an access/payment mechanism within the product (per the whitepaper).
  • Who pays fees: product users (Web3 projects/teams).
  • Where fees go: not established per Tier‑1 sources (the whitepaper describes the model, but not the cash flows in detail).
  • Issuance/burn: fixed supply 1B; the site mentions buyback&burn, but the parameters are not established per Tier‑1 sources.
  • Security/incentive mechanisms: rewards/incentive programs (per the token utility); staking is mentioned on the website.
  • Distribution and token issuance schedule: a distribution plan exists in the whitepaper (token distribution plan; without detailing here).
  • Treasury: — (not established per Tier‑1 sources).

Governance

  • Who makes decisions: the project’s company/team + participation of token holders in governance (per the token utility).
  • How protocol parameters change: via governance decisions and product updates (the procedure is not established in detail).
  • Where decisions are discussed/made: official channels (Docs/X/Telegram).
  • Keys/multisig: the whitepaper mentions the use of a Gnosis Safe multisig (without specifics of composition/thresholds).

Security and incidents

  • Audits: the whitepaper indicates a plan/intent of regular audits (without results/links to completed audits).
  • Bug bounty: — (not established per Tier‑1 sources).
  • Incidents: — (not established).
  • Threat model: data quality risks (social media/onchain), risks of errors in causal interpretation, risks of leaks/compromise of accounts/keys; for the token — typical ERC‑20 and management (multisig) risks.

Project status and timeline

  • Current status: active (based on the presence of the website/whitepaper/contract).
  • Key releases/milestones: roadmap 2024/2025 in the whitepaper (see links_*).
  • Roadmap: see links_*.

Ecosystem/integrations

  • Integrations: onchain data sources (tokens/transactions) + social data sources (X, etc.) per the description; the product is oriented toward Web3 teams.
  • Partners: — (not established per Tier‑1 sources).
  • Where it’s actually used: analysis of KOL campaigns and their impact on tokens (per the whitepaper).

AI component of the project

  • What is real AI here? the whitepaper describes ML/NLP components (sentiment analysis, topic modeling) and causal impact analytics (causal inference) as the basis of the product.
  • What is truly onchain? the ERC‑20 $CRAI token (contract on Etherscan) and the use of onchain metrics as input data for the analysis.
  • Why is a token needed? access to functionality and paid packages, rewards/incentives and governance (per the token utility).
  • Red flags (based on the information found): AI quality/accuracy strongly depends on the data and methodology; the whitepaper contains no reproducible quality metrics; the smart contract audit is claimed as a plan (not a fact of completion).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity high 3
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 part of the current product (not only “intent/roadmap”).
  • Evidence: Tier‑1 — https://docs.cryptify.ai/
  • Why sufficient / why not (one line): the AI positioning is accompanied by a tech description and token utility, so AI_0 is not used as “intent only”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): ML/NLP and causal inference are used to analyze sentiment/topics and estimate the causal effect of KOL posts on token metrics.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/technical-overview/algorithms-and-analytics
  • Why sufficient / why not (one line): Tier‑1 contains a description of specific algorithms/approaches and tasks.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a reproducible public demo/guide confirming the operation of the AI on data is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://cryptify.ai/product/
  • Why sufficient / why not (one line): the product page is descriptive; the result cannot be checked “hands‑on” within this card.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.cryptify.ai/technical-overview/technical-summary
  • Why sufficient / why not (one line): there is a tech description, but no reproducible metrics of the quality/accuracy of the “AI conclusions” with a methodology.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the methods (causal inference, EWMA/time windows, Bayesian modeling) and NLP modules are described.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/technical-overview/technical-summary ; https://docs.cryptify.ai/technical-overview/algorithms-and-analytics
  • Why sufficient / why not (one line): there is a tech description and a list of tools/approaches.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xDdbcDD8637d5CEDd15EeEe398108FCa05A71b32b (CRAI)
  • Evidence: Tier‑1 — https://docs.cryptify.ai/tokenomics/token-overview-and-contract ; https://etherscan.io/token/0xDdbcDD8637d5CEDd15EeEe398108FCa05A71b32b
  • Why sufficient / why not (one line): the Tier‑1 docs provide the contract, Etherscan confirms it onchain.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: other than the token, no confirmed onchain logic of the product is established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/
  • Why sufficient / why not (one line): the product is an analytics dashboard; onchain is used as a data source and the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without the blockchain, the onchain part of the measured metrics is lost, but the analytics product itself can exist without its own onchain protocol.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/
  • Why sufficient / why not (one line): onchain is important as a data source, but is not shown as a critical protocol component.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the $CRAI token exists as an ERC‑20.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/tokenomics/token-overview-and-contract
  • Why sufficient / why not (one line): the whitepaper specifies the contract and the network.
  • 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): payment for packages/searches and use of the dashboard can be made in $CRAI.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/tokenomics/token-utility-usdcrai
  • Why sufficient / why not (one line): the token utility directly describes the payment method and “search packages”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): rewards & incentive programs via the token (for contribution to the community/beta tests/content, etc.).
  • Evidence: Tier‑1 — https://docs.cryptify.ai/tokenomics/token-utility-usdcrai
  • Why sufficient / why not (one line): the token utility describes the reward mechanics and examples of activity.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): token holders participate in governance (voting/proposals on the product/resources/partnerships).
  • Evidence: Tier‑1 — https://docs.cryptify.ai/tokenomics/token-utility-usdcrai
  • Why sufficient / why not (one line): the governance section describes the areas of voting/proposals.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is embedded in the access/payment and governance mechanics per the whitepaper; replaceability has not been assessed.
  • Evidence: Tier‑1 — https://docs.cryptify.ai/tokenomics/token-utility-usdcrai
  • Why sufficient / why not (one line): Tier‑1 describes several functions of the token, but the replaceability test was not carried out.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.cryptify.ai/tokenomics/token-overview-and-contract the $CRAI token contract (address/network/parameters)
Tier‑1 https://docs.cryptify.ai/tokenomics/token-utility-usdcrai token utility (access/payments/governance/rewards)
Tier‑1 https://docs.cryptify.ai/technical-overview/technical-summary tech description of the causal inference approach (events/windows/counterfactual/Bayesian)
Tier‑1 https://docs.cryptify.ai/technical-overview/algorithms-and-analytics NLP/sentiment/topic modeling and tools (PyWhy/EconML/BERTopic)
Tier‑1 https://etherscan.io/token/0xDdbcDD8637d5CEDd15EeEe398108FCa05A71b32b onchain fact: the $CRAI token
Tier‑2 https://www.coingecko.com/en/coins/cryptify-ai aggregator (context/for reference)
Tier‑2 https://coinmarketcap.com/currencies/cryptify-ai-ethereum/ aggregator (context/for reference)

No comments to display

Back to top