Skip to main content

DexCheck AI

DexCheck AI (DCK) — 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).

DexCheck AI — an AI/Analytics / DeFAI / InfoFi platform: a terminal for onchain analytics and an “AI assistant for the investor” (sentiment/narratives/Smart Money, etc., per their docs). The DCK token is used for access to PRO features (via staking), API payments and some access programs (e.g., the IPSO tier).

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 web terminal and API for crypto analytics and market research.
  • Who it’s for: traders/investors/researchers; developers who need a blockchain data API.
  • Why onchain/token: the DCK token is needed as an access key (staking → PRO), as the currency for paying for the API and as a rewards mechanism in the staking programs.
  • What you can actually touch (Tier‑1): the DexCheck web terminal (app) + the product documentation.

How it works (very briefly)

  1. The user does: opens the terminal/dashboards or connects the API.
  2. The system does: aggregates onchain data across networks and (per the docs) uses AI modules to derive insights (e.g., sentiment/narratives/Smart Money).
  3. The user gets: analytics panels/alerts/insights; for developers — API access.
  4. Where the blockchain is: the DCK token lives onchain (BSC; an address on Ethereum is also listed on the website); part of the access/staking is tied to the token.
  5. Token role (if any): DCK staking for PRO; API payments; access to the IPSO tier (per the docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name DexCheck AI
Also known as (aliases) DexCheck, DCK, dexcheck.ai
Logo (logo) ../assets/265_dexcheck_logo.svg
Token symbol (ticker) DCK
Category AI/Analytics | DeFAI | InfoFi
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 0x16faf9daa401aa42506af503aa3d80b871c467a3
Token model (token_type) utility (governance)
Max supply 1,000,000,000 DCK
Issuance fixed (minted at deploy, per the contract)
Tokenomics (tokenomics, brief) staking → PRO access; API payments in DCK (per the docs)
Governance — (no specific mechanism in the extracted Tier‑1; “governance” is claimed in the docs)
Admins/keys — (per the token code there is an owner(), the owner status is not confirmed in this card)
Audit yes (CertiK, link in Evidence)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI analytics + investor assistant
Use‑case (use_case) crypto analytics + data API
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 2 / 3
Last verified 2026-02-11

General project overview

DexCheck is an analytics terminal and a set of services (including an API) that aggregate onchain data and add an AI interpretation layer (per their documentation: DeFAI/InfoFi/analytics, sentiment, “Smart Money”). Per their FAQ, the product is aimed at investors/traders and teams building Web3 applications on data.

Features/modules

  • Analytics & Insights: token/market dashboards, Smart Money tracking, wallet profiler, whale insights (website).
  • AI/InfoFi: AI narrative & trend detection, sentiment on X, InsightsGPT/assistants (website + docs).
  • DexCheck API: REST/Websocket/Webhooks for blockchain data (website + docs).

Typical scenarios

  • Scenario 1: a trader looks at Smart Money/whale activity → makes a decision about risks/entry (per the descriptions on the website/in the docs).
  • Scenario 2: a user analyzes narratives/sentiment → tracks trends (per the website).
  • Scenario 3: a developer pays for the API → integrates the data into their own application (per the website).

Getting started (wallet/network)

  • What you need: an account/access to the web application; for the token — an EVM wallet.
  • Network/chain: DCK on BNB Smart Chain (BEP‑20); an address on Ethereum is also listed on the website (not verified in this card).
  • Fees: BSC network gas for onchain operations with the token; API fees/payments depend on the plan.

Architecture/tech (non‑AI)

  • Components: web terminal + data engine/API; the DCK token (BEP‑20).
  • Participant roles: terminal users; API developers; DCK stakers.
  • Where logic runs: analytics/AI — offchain; onchain — the token and the (claimed) staking mechanics/token‑based access.
  • Dependencies: BNB Smart Chain (for the token); onchain data sources across many networks (per the docs).

Token/economics (expanded, no forecasts)

  • Token utility: access to DexCheck PRO via staking, API payments, participation in the IPSO tiers (per the docs).
  • Protocol necessity drivers: the token is the key to premium features and the currency for paying for some services.
  • Who pays fees: gas on BSC for onchain operations; internal payments/staking — per the platform’s rules.
  • Where fees go: onchain gas — to the BSC validators; the distribution of platform fees is not detailed in the extracted Tier‑1.
  • Issuance/burn: the supply is fixed (mint in the token contract on BSC).
  • Security/incentive mechanisms: DCK staking and rewards (per the docs).
  • Distribution and token issuance schedule: described on the Token Allocation & Distribution page (without numbers in the extracted fragment).
  • Treasury: —.

Governance

  • Who makes decisions: — (the docs claim that the token makes it possible to participate in governance, but the specific mechanism was not extracted).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: a CertiK audit report is listed on BscScan for the DCK token.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: the AI features are described, but without quality metrics and a description of the models; in addition, onchain logic beyond the token is not confirmed by contract addresses.

Project status and timeline

  • Current status: the product is active (website + docs).
  • Key releases/milestones: see the GitHub releases for the DCK token; product updates — in the docs.
  • Roadmap: https://docs.dexcheck.ai/future-expansion-plans

Ecosystem/integrations

  • Integrations: web terminal; API for developers; network integrations are listed in the docs.
  • Partners: —.
  • Where it’s actually used: — (the extracted Tier‑1 contains no list of production integrations).

AI component of the project

  • What is real AI here? the docs/website describe AI features: AI‑augmented analytics, sentiment/narratives, an “investment assistant”, as well as the DexCheck Agent product (in the platform description).
  • What is truly onchain? the DCK token is confirmed onchain (BSC); the rest of the analytics/AI works offchain.
  • Why is a token needed? access to PRO via staking, API payments, participation in some access programs (IPSO tier) and staking rewards (docs).
  • Red flags (based on the information found): no technical details of the models and no public quality metrics; without staking contract addresses, the onchain component mostly boils down to the token; access/subscription is potentially replaceable without the token.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
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): not applicable: AI is described as working functions/modules (AI_1/AI_2).
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/
  • Why sufficient / why not (one line): AI_0 is used only in the absence of AI_1..AI_4.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): DexCheck describes AI modules for analytics/inference (DeFAI/InfoFi), including sentiment/narratives and assistants (docs + website).
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/ ; https://dexcheck.ai/
  • Why sufficient / why not (one line): Tier‑1 describes specific AI functions and what they give the user.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the website provides access to the application (“Launch App”) and examples of the interface/screenshots; the docs describe how to use the features.
  • Evidence: Tier‑1 — https://dexcheck.ai/ ; https://docs.dexcheck.ai/
  • Why sufficient / why not (one line): there is a public product interface and documentation on the features.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: — (there are no public quality metrics for the AI models/benchmarks in the extracted Tier‑1).
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/
  • Why sufficient / why not (one line): the absence of numbers/context → AI_3 remains 0.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the extracted Tier‑1 contains no technical description of the architecture/model versions (which LLMs, how they are trained, how quality is measured).
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/
  • Why sufficient / why not (one line): no description at the level of “which models/versions/architecture” was found.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: DCK token (BEP‑20): 0x16faf9daa401aa42506af503aa3d80b871c467a3
  • Evidence: Tier‑1 — https://bscscan.com/token/0x16faf9daa401aa42506af503aa3d80b871c467a3 ; https://dexcheck.ai/
  • Why sufficient / why not (one line): the onchain token and its address are confirmed by BscScan; the website also publishes the address.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: the extracted Tier‑1 contains no addresses/contracts that confirm onchain access/staking logic beyond the token itself.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/ ; https://bscscan.com/token/0x16faf9daa401aa42506af503aa3d80b871c467a3
  • Why sufficient / why not (one line): without specific contracts/addresses, we consider “onchain = the token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: if the blockchain is replaced with an ordinary DB, the core product (analytics/dashboards/API) remains; only the token layer breaks.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/ ; https://dexcheck.ai/
  • Why sufficient / why not (one line): Tier‑1 does not show that without onchain the product loses a key property.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, DCK.
  • Evidence: Tier‑1 — https://bscscan.com/token/0x16faf9daa401aa42506af503aa3d80b871c467a3
  • Why sufficient / why not (one line): the token exists onchain.
  • 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 docs state that DCK is the “main currency for paying” for the DexCheck proprietary APIs.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/dexcheck-token/dexcheck-dck-token-utility
  • Why sufficient / why not (one line): there is a direct description of payment in the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the docs describe DCK staking for rewards and for access to PRO/tiers.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/dexcheck-token/dexcheck-dck-token-utility
  • Why sufficient / why not (one line): the staking mechanics and incentives are described in the Tier‑1 docs.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the docs say that the token makes it possible to participate in the platform’s governance.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/dexcheck-token/dexcheck-dck-token-utility
  • Why sufficient / why not (one line): there is an explicit statement about governance utility (although without details of the mechanism).
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): access/subscriptions and API payments can also be implemented without DCK (e.g., via USDC/fiat/a subscription), preserving the product value.
  • Evidence: Tier‑1 — https://docs.dexcheck.ai/ ; https://dexcheck.ai/
  • Why sufficient / why not (one line): the token’s utility is mainly about “access/payment”, which is usually replaceable by other schemes.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.dexcheck.ai/ Tier‑1 description of the product and the AI/analytics modules
Tier‑1 https://bscscan.com/token/0x16faf9daa401aa42506af503aa3d80b871c467a3 the onchain address and parameters of the DCK token (max total supply 1B)
Tier‑1 https://docs.dexcheck.ai/dexcheck-token/dexcheck-dck-token-utility token utility: PRO unlock, API access, staking, IPSO tier, governance (as a claim)
Tier‑1 https://skynet.certik.com/projects/dexcheck/security-score audit report on the token contract (link listed on BscScan)

No comments to display

Back to top