Skip to main content

TypeAI

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

TypeAI is positioned as an AI assistant/bot that translates the user’s text commands into DeFi actions (swap/transfer, etc.) and works via Telegram and a web interface.

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 “type to DeFi” AI interface (chat/bot) that helps form onchain actions from text.
  • Who it’s for: DeFi users who need a simpler UI for basic operations.
  • Why onchain/token: onchain is mandatory for executing DeFi transactions; the TYPE token is described as an economic/marketing asset (taxes, revenue‑sharing), but the card’s Tier‑1 sources do not prove that it is needed for the “bot” to work.

How it works (very briefly)

  1. The user enters a command (example: swap/transfer) in the interface.
  2. The AI layer interprets the intent and parameters.
  3. The system forms/initiates an onchain transaction in the selected network/DEX.

Quick links: AI thesis fit

Project passport

Field Value
Project name TypeAI
Also known as (aliases) TYPE; Type AI
Logo (logo) —
Token symbol (ticker) TYPE
Category AI/Agents | Tooling
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (website + docs + token)
Token (standard) ERC-20
Token contract 0x443459d45c30a03f90037d011cbe22e2183d3b12
Token model (token_type) utility (revenue-sharing + taxes)
Max supply 10,000,000 TYPE (Etherscan Max Total Supply)
Issuance fixed max total supply (per Etherscan)
Tokenomics (tokenomics, brief) the contract includes tax mechanics and conversion of taxes (visible in the source code in the explorer)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) NLP command interpretation → DeFi actions
Use‑case (use_case) chat interface for DeFi
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 3
Last verified 2026-02-11

General project overview

According to the product description in the docs and the comments in the contract source code (Etherscan), TypeAI is an “AI crypto companion / bot” that helps the user perform DeFi actions via text, and also includes functionality around swap/bridge/portfolio. Within this card, the existence of the TYPE token (ERC‑20) and of the claimed AI interface is confirmed, but the necessity of the token for the AI function to work is not confirmed.

AI component of the project

  • AI reality: there is a Tier‑1 description of the AI assistant’s features (what it does), but the card’s sources contain no quality metrics/model architecture.
  • Onchain necessity: the result of its operation is onchain transactions (DeFi); but TypeAI’s own protocol onchain logic beyond the token is not identified in the card’s sources.
  • Token necessity: TYPE is described as a token with taxes/revenue‑sharing; without proof that the bot does not work without TYPE.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
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): 0
  • Claim (one line): the intent flag was not applied, since Tier‑1 describes the AI features as the current product.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): AI_0 is needed when AI is only plans without a working component.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The Tier‑1 docs describe an AI assistant that interprets commands and helps perform actions in DeFi.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): There is a description of the “AI crypto companion / bot” features and of the user workflow.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demos/reproducible examples of the AI assistant in operation were found.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): The page describes the product but does not provide a verifiable “demo surface” (app/guide/launch example).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): Quality metrics of the AI part are not published.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is technical context at the level of the smart contract and the product description (without the ML architecture of the model).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x443459d45c30a03f90037d011cbe22e2183d3b12 ; https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): Tier‑1 shows the onchain part and basic technical context; there are no details of the model/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: TYPE (ERC‑20) — 0x443459d45c30a03f90037d011cbe22e2183d3b12
  • Evidence: Tier‑1 — https://etherscan.io/token/0x443459d45c30a03f90037d011cbe22e2183d3b12
  • Why sufficient / why not (one line): The token contract 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: TypeAI’s protocol onchain logic beyond the token is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): The sources describe the product/bot but do not provide addresses/contracts of the protocol logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the criticality of onchain beyond the fact of “DeFi transactions onchain” is not substantiated per Tier‑1.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): It is not shown that without the blockchain the core property of the product breaks down.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, TYPE.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x443459d45c30a03f90037d011cbe22e2183d3b12
  • Why sufficient / why not (one line): The token 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): Mandatory payment for the bot/access with the TYPE token is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): There is no clear paywall scheme “pay TYPE → get access”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): A staking/incentive layer necessary for the protocol is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): There are mentions of taxes/revenue‑sharing, but these are not protocol collateral/penalties.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): There is no description of a DAO/voting process.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): The utility looks replaceable (fees/revenue share), without a protocol necessity of the token.
  • Evidence: Tier‑1 — https://type-ai.gitbook.io/type-ai/
  • Why sufficient / why not (one line): It is not shown that the functions cannot be implemented without TYPE (for example, via a subscription/stablecoin).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://type-ai.gitbook.io/type-ai/ Description of the product and of the AI assistant’s features.
Tier‑1 https://etherscan.io/token/0x443459d45c30a03f90037d011cbe22e2183d3b12 The TYPE contract and max total supply 10,000,000.

No comments to display

Back to top