Skip to main content

KanzzAI

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

KanzzAI — an AI/Agents project on Ethereum, token (symbol: KAAI).

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 that, per Tier‑1 documentation, describes a set of AI tools/bots (Telegram agents, AI agents for X) and an “AI Terminal” for managing them.
  • Who it’s for: users/communities who want to create and manage chatbots/agents (per Tier‑1 docs).
  • Why onchain/token: the KAAI ERC‑20 token is confirmed onchain; staking and revenue sharing are claimed in Tier‑1 docs (mechanics details require additional verification).
  • What you can actually touch (Tier‑1): Kanzz AI Terminal (see links_*).

How it works (very briefly)

  1. The user does: configures an agent (prompt/parameters) and connects it to Telegram or X (per Tier‑1 docs).
  2. The system does: runs the agent and enables interaction with users/the audience (implementation details are not established per Tier‑1).
  3. The user gets: a working bot/agent for communications/automation.
  4. Where the blockchain is: Ethereum is used as the network of the KAAI token; separate onchain logic of the product (other than the token) is not established per Tier‑1.
  5. Token role: staking and revenue sharing are claimed per Tier‑1 docs; the role of the token as mandatory payment/governance is not confirmed by Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name KanzzAI
Also known as (aliases) KAAI
Logo (logo) —
Token symbol (ticker) KAAI
Category AI/Agents | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0xa7d48da33cf6ac74ed2ba71b7e33005dc51adbb7
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) AI bots/agents for Telegram/X
Use‑case (use_case) AI agent/bot creation + management
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Per Tier‑1 documentation, KanzzAI is positioned as a set of AI tools for creating and managing agents/bots: Telegram agents, AI agents for X, as well as an “AI Terminal” as the central management interface. The existence of an ERC‑20 token is confirmed per Tier‑1 sources; onchain logic of the product, other than the token, is not confirmed by Tier‑1 sources.

Features/modules

  • AI Terminal: a unified interface for managing tools/agents (per Tier‑1 docs).
  • Telegram Agents: creation/configuration of AI agents for specified prompts and deployment on Telegram (per Tier‑1 docs).
  • AI Agents Service for X: automation of posting/replies (per Tier‑1 docs).
  • GPU marketplace (claimed): mentioned in Tier‑1 docs as an ecosystem module.

Typical scenarios

  • Scenario 1: a user creates and configures a Telegram agent → receives a bot for communication/moderation/content.
  • Scenario 2: a user creates an agent for X → receives automation of audience interaction (per the docs).

Getting started (wallet/network)

  • What you need: access to the “AI Terminal”/project services (the exact onboarding depends on the product; see Tier‑1 docs).
  • Network/chain: Ethereum (for operations with the KAAI token).
  • Fees: Ethereum network fees for transactions with the token; service fee/subscription parameters are not confirmed by Tier‑1 sources.

Architecture/tech (non‑AI)

  • Components: offchain services/interfaces for managing agents (per the docs), the KAAI ERC‑20 token on Ethereum.
  • Participant roles: users/agent creators, Telegram/X users, Ethereum infrastructure providers.
  • Where logic runs: the AI part, judging by the available descriptions, runs offchain; only the token (and its transactions) is confirmed onchain.
  • Dependencies: Ethereum L1 (token), external platforms Telegram/X.

Token/economics (expanded, no forecasts)

  • Token utility: Tier‑1 docs claim that the ecosystem is centered around $KAAI and that staking and revenue sharing are available via the Terminal (mechanics details require additional verification).
  • Who pays fees: users (gas in ETH) for transactions with the token.
  • Where fees go: to Ethereum network validators/stakers (within the network mechanics).
  • Issuance/burn: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: standard risks of ERC‑20 tokens (contract/liquidity) and offchain service risks (access/accounts); without a Tier‑1 audit, conclusions are limited.

Project status and timeline

  • Current status: onchain token on Ethereum mainnet; the status of the products/terminal is not confirmed by Tier‑1 sources.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: Telegram and X (as platforms for agents, per the docs); Ethereum (as the token network).
  • Partners: —.
  • Where it’s actually used: onchain activity of the token contract is observable via Etherscan (see links_*).

AI component of the project

  • What is real AI here? Per Tier‑1 docs, the project describes the creation/management of AI agents (Telegram/X) as its main product.
  • What is truly onchain? The KAAI ERC‑20 token on the Ethereum network is confirmed onchain; separate onchain logic of the product (other than the token) is not confirmed by Tier‑1 sources.
  • Why is a token needed? Tier‑1 docs claim staking and revenue sharing, as well as an “AI Terminal” as a center for managing tools; at the same time, mechanics of payment/governance with the token are not confirmed by Tier‑1 sources.
  • Red flags (based on the information found): absence of public audits/bug bounty; absence of a Tier‑1 specification of onchain logic of the product (other than the token); absence of reproducible quality metrics (AI_3=0).

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 low 1
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Per Tier‑1 docs, AI is described as operating product functionality, not a “plan/intent”.
  • Evidence: Tier‑1 — https://docs.kanzzai.com/
  • Why sufficient / why not (one line): AI_0 adds no signal when Tier‑1 already describes working AI features (AI_1=1).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The docs describe AI agents/bots for Telegram and AI agents for X (creation, prompt configuration, management).
  • Evidence: Tier‑1 — https://docs.kanzzai.com/
  • Why sufficient / why not (one line): Tier‑1 documentation describes exactly what the AI agents do and how to use them.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a Tier‑1 public “surface” of AI Terminal on the project’s domain.
  • Evidence: Tier‑1 — https://terminal.kanzzai.com/
  • Why sufficient / why not (one line): We record the presence of a direct link to the Terminal as a demo surface; access/tariff details are not verified.
  • 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.kanzzai.com/
  • Why sufficient / why not (one line): No reproducible set of quality metrics/benchmarks was found per Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): Detailed architecture/model versions are not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.kanzzai.com/
  • Why sufficient / why not (one line): The documentation describes product features but does not provide a technical specification at the architecture/version level.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xa7d48da33cf6ac74ed2ba71b7e33005dc51adbb7 (ERC‑20 token contract)
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa7d48da33cF6AC74Ed2Ba71b7E33005DC51ADbB7
  • Why sufficient / why not (one line): The token contract and its onchain activity are observable in 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 confirmed by Tier‑1 sources (other than the fact of the ERC‑20 token’s existence).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa7d48da33cF6AC74Ed2Ba71b7E33005DC51ADbB7 ; https://docs.kanzzai.com/
  • Why sufficient / why not (one line): There is no confirmation of onchain logic of the product 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 per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no proof per Tier‑1 that the product requires the trustless properties of the blockchain (other than the token).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, KAAI (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa7d48da33cF6AC74Ed2Ba71b7E33005DC51ADbB7 ; https://docs.kanzzai.com/
  • Why sufficient / why not (one line): The existence of the token is confirmed onchain; $KAAI is mentioned in the docs.
  • 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): The use of the token as mandatory payment for the service is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.kanzzai.com/
  • Why sufficient / why not (one line): The available Tier‑1 sources contain no description of the mechanics of “payment in KAAI for a specific service”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Staking and revenue sharing are claimed in Tier‑1 docs as parts of the ecosystem/Terminal.
  • Evidence: Tier‑1 — https://docs.kanzzai.com/
  • Why sufficient / why not (one line): This provides sufficient Tier‑1 grounds for the token being claimed as part of incentives/returns; details of the onchain mechanics are not verified.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.kanzzai.com/
  • Why sufficient / why not (one line): There is no Tier‑1 description of a governance process with a role for KAAI.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without confirmed utility, replaceability cannot be correctly assessed.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.kanzzai.com/ Tier‑1 description of AI agents/bots and the product composition (AI Terminal, Telegram/X agents).
Tier‑1 https://terminal.kanzzai.com/ Tier‑1 demo surface: Kanzz AI Terminal (mentioned as a center for managing tools; access/UX require additional verification).
Tier‑1 https://etherscan.io/token/0xa7d48da33cF6AC74Ed2Ba71b7E33005DC51ADbB7 The KAAI ERC‑20 token contract and onchain facts (address, network, transactions).
Tier‑1 https://docs.kanzzai.com/ Tier‑1: staking and revenue sharing are claimed in the docs as parts of the ecosystem/Terminal.
Tier‑2 https://coinmarketcap.com/currencies/kanzzai/ Token profile (for reference).
Tier‑2 https://www.coingecko.com/en/coins/kanzzai Token profile (for reference).

No comments to display

Back to top