Skip to main content

IQ AI

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

IQ AI — an AI/Agents | DeFi | Infra project: the AI agent tokenization platform ATP (Agent Tokenization Platform) with a public agent catalog app; the ecosystem token IQ is used to pay platform fees, for staking and for governance (per Tier‑1).

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 platform where you can create and launch “agents” as onchain objects with their own tokens, and view/trade them in the app.
  • Who it’s for: developers and teams that want to issue “agent tokens”; users who interact with tokenized agents in the app.
  • Why onchain/token: agent tokenization and ownership/governance happen onchain, while platform fees are paid in IQ (Tier‑1), plus there is IQ staking for governance/rewards.
  • What you can actually touch (Tier‑1): the ATP app (app.iqai.com) + SDK/examples on GitHub (adk-ts).

How it works (very briefly)

  1. The user does: opens the ATP app, browses the list of agents or creates a new one.
  2. The system does: deploys the agent’s onchain contracts and issues the agent token (per the platform design; agent addresses are visible in the app).
  3. The user gets: access to the catalog of tokenized agents and their onchain parameters (address/chain/holders, etc.).
  4. Where the blockchain is: the addresses of agents and their tokens, ownership/trading and (as claimed) governance — onchain.
  5. Token role: the IQ token — the ATP fee token + staking (hiIQ) + governance (Tier‑1); each agent has its own token.

Quick links: AI thesis fit

Project passport

Field Value
Project name IQ AI
Also known as (aliases) IQ | Everipedia IQ | ATP (Agent Tokenization Platform)
Logo (logo) ../assets/57_iq_logo.png
Token symbol (ticker) IQ
Category AI/Agents | DeFi | Infra
Primary chain (chain) Fraxtal
Type EVM
Network status mainnet
Consensus (consensus) L2 (Optimistic Rollup, Fraxtal on Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract Ethereum: 0x579cea1889991f68acc35ff5c3dd0621ff29b0c9
Token model (token_type) utility (payments + staking + governance)
Max supply 21,213,133,840.98106 (Max Total Supply, Ethereum)
Issuance fixed cap
Tokenomics (tokenomics, brief) All ATP fees are paid in IQ; IQ staking (hiIQ) for governance/rewards; each agent token has a pair with IQ (Tier‑1).
Governance token governance (IQ stakers/holders; hiIQ)
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) tokenized AI agents + ADK agent framework
Use‑case (use_case) launch tokenized AI agents for on-chain services
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

IQ AI promotes ATP (Agent Tokenization Platform) — a platform where “agents” are represented as onchain entities with their own tokens. The user‑facing part looks like a public catalog app (app.iqai.com), where you can view an agent, its address and basic metrics (holders/volume/chain), as well as create an agent.

Per Tier‑1, the project is also developing the ADK‑TS SDK framework for building AI agents (multi‑provider LLMs, tools/memory/workflows), and positions it as the foundation for “tokenized agents”.

Features/modules

  • ATP app (catalog/creation): a public app with a table of agents and addresses.
  • Agent Development Kit (ADK‑TS): an SDK for building AI agents, including examples and multi‑LLM support.
  • Onchain platform contracts: components for issuing agent tokens and governance (covered by an audit; see Evidence).

Typical scenarios

  • Scenario 1 (user): open the app → select an agent → view the address/chain/holders → proceed to interacting with the agent/social integrations (if listed in the agent’s card).
  • Scenario 2 (developer/team): install ADK‑TS → build an agent in your own project → issue/tokenize the agent via ATP (per the claimed “Create Agent” flow in the app).

Getting started (wallet/network)

  • What you need: an EVM wallet (for “Create Agent” actions and other onchain operations, a login/wallet connection will be required).
  • Network/chain: Fraxtal (the “Fraxtal” network is visible in the app UI).
  • Fees: network gas for transactions + the platform fee, which per Tier‑1 is paid in the IQ token.

Architecture/tech (non‑AI)

  • Components: the ATP web app (catalog/creation) + onchain contracts for issuing and managing agents (the audit mentions AgentFactory, LiquidityManager, TokenGovernor, etc.).
  • Participant roles: the agent creator (deploy/launch), holders of the agent token (governance/ownership), IQ holders/stakers (platform governance).
  • Where logic runs: onchain — issuance of agent tokens/contracts and the associated rules; offchain — UI/integrations and running LLM agents as software.
  • Dependencies: an EVM network (Fraxtal), DEX/liquidity for pairs (the audit discusses Fraxswap), LLM providers/keys for the agents themselves (per the SDK).

Token/economics (expanded, no forecasts)

  • Token utility: per Tier‑1, all ATP fees are paid in IQ, and there is also IQ staking (hiIQ) and a governance role.
  • Protocol necessity drivers: the platform mandates fee payment in the IQ token and ties agent tokens to IQ pairs — this makes IQ the “system token” of the ecosystem.
  • Who pays fees: users/creators/participants who perform actions in ATP and interact with agents.
  • Where fees go: — (not extracted from Tier‑1).
  • Issuance/burn: the Max Total Supply is visible on Ethereum; the issuance/burn model was not extracted (apart from the cap).
  • Security/incentive mechanisms: IQ staking for governance/rewards (Tier‑1); for details of the risk model, see the primary source.
  • Distribution and token issuance schedule: — (not extracted).
  • Treasury: —.

Governance

  • Who makes decisions: per Tier‑1, IQ is used as a governance token, and participation in governance is tied to staking/hiIQ.
  • How protocol parameters change: via the token’s governance mechanisms (process details were not extracted).
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: there is a public Code4rena report on the IQ AI smart contracts (2025‑03‑19; the audit took place 2025‑01‑29…2025‑02‑07).
  • Bug bounty: — (there is no Tier‑1 program page in links_*).
  • Incidents: — (not found per Tier‑1).
  • Threat model: typical smart contract risks (governance attacks/DoS/liquidity migration errors), as reflected in the Code4rena findings.

Project status and timeline

  • Current status: the ATP app is publicly available; the network in the UI is Fraxtal.
  • Key releases/milestones: ADK‑TS releases are maintained in GitHub Releases; individual infrastructure elements (for example, the MCP docs server) are mentioned in the changelog/release notes.
  • Roadmap: — (links_* shows —).

Ecosystem/integrations

  • Integrations: integrations/partnerships are claimed per the whitepaper (for example, Fraxtal as a launch partner; a mention of integration with NEAR as a future direction).
  • Partners: Fraxtal (claimed as a strategic launch partner in the whitepaper).
  • Where it’s actually used: tokenized agents (for example, “Sophia”) are published in the app, with onchain addresses and metrics.

AI component of the project

  • What is real AI here? the ADK‑TS SDK and the “AI agents” model (multi‑LLM + tools + workflows) + the agent catalog in ATP.
  • What is truly onchain? agent tokenization (agent tokens), their addresses/metrics in the app, the IQ contract (ERC‑20) and the claimed governance role of IQ.
  • Why is a token needed? per Tier‑1, ATP fees are paid in IQ, and IQ is also the governance and staking token (hiIQ) + IQ‑agent token pairs.
  • Red flags (based on the information found): AI‑washing — low risk (there is an SDK and an app), but “autonomously manages assets” is better re‑checked against the agent’s demo/docs; onchain‑washing — re‑check which operations are actually onchain vs UI metrics; token‑washing — re‑check the fee/distribution economics (where the fees go).

DecAI Fit component summary

  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
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): intent is not needed: there are Tier‑1 artifacts of a working AI stack (AI_1/AI_2/AI_4 = 1).
  • Evidence: Tier‑1 — https://github.com/IQAIcom/adk-ts, https://app.iqai.com/
  • Why sufficient / why not (one line): AI_0 is used when there is only a roadmap without working artifacts; here there is an SDK + an app.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the project provides an SDK for building AI agents (multi‑LLM, tools, memory, workflows) and promotes tokenized agents.
  • Evidence: Tier‑1 — https://github.com/IQAIcom/adk-ts, https://iqai.com/whitepaper.pdf
  • Why sufficient / why not (one line): the Tier‑1 README/whitepaper describe the functionality and purpose of the AI agents.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a reproducible catalog of tokenized agents (the ATP app) and examples/a quickstart in ADK‑TS.
  • Evidence: Tier‑1 — https://app.iqai.com/, https://github.com/IQAIcom/adk-ts
  • Why sufficient / why not (one line): a public app + a repository with example code provide verifiable “what you can touch” artifacts.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf, https://github.com/IQAIcom/adk-ts
  • Why sufficient / why not (one line): no explicit benchmarks/quality metrics/model comparisons were found in the available Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): ADK‑TS documents the SDK’s architecture/modules (agent builder, tools, workflows, models), and there are releases/a changelog.
  • Evidence: Tier‑1 — https://github.com/IQAIcom/adk-ts, https://github.com/IQAIcom/adk-ts/releases
  • Why sufficient / why not (one line): the Tier‑1 repository has a technical description, a package structure and versioning.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Fraxtal (ATP app) + Ethereum (the IQ ERC‑20 contract)
  • Addresses/identifiers: IQ token (Ethereum): 0x579cea1889991f68acc35ff5c3dd0621ff29b0c9; agents have onchain addresses in the catalog (example: Sophia 0x4dBcC239b265295500D2Fe2d0900629BDcBBD0fB).
  • Evidence: Tier‑1 — https://app.iqai.com/, https://etherscan.io/token/0x579cea1889991f68acc35ff5c3dd0621ff29b0c9
  • Why sufficient / why not (one line): there are specific addresses and a contract explorer + a UI with agent addresses.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: issuance/life cycle of agent tokens and the associated platform contracts (factory/governor/liquidity management); the app shows onchain “agent” entities with addresses.
  • Evidence: Tier‑1 — https://app.iqai.com/, https://code4rena.com/reports/2025-01-iq-ai
  • Why sufficient / why not (one line): the existence of a separate contract system for agents (not just the IQ token) confirms the onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the key part of “tokenized agents” breaks down: issuance/ownership/trading/addresses of agents and the governance mechanics of the tokens.
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf, https://app.iqai.com/
  • Why sufficient / why not (one line): the whitepaper describes tokenization as the foundation of the platform; the app relies on onchain addresses.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, IQ.
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf, https://etherscan.io/token/0x579cea1889991f68acc35ff5c3dd0621ff29b0c9
  • Why sufficient / why not (one line): the token and its contract are confirmed by Tier‑1.
  • 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): “All ATP fees are paid in IQ” (fees for using the platform are paid in IQ).
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf
  • Why sufficient / why not (one line): this is a direct statement in the Tier‑1 whitepaper about payments in the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the whitepaper describes IQ staking (hiIQ) for governance and for receiving rewards.
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf
  • Why sufficient / why not (one line): staking mechanics = incentives/a participation mechanism (stake → rewards/voice).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): IQ is the governance token of the ATP ecosystem (participation via hiIQ/staking).
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf
  • Why sufficient / why not (one line): Tier‑1 explicitly formulates the governance role of IQ.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): per Tier‑1, the token is built into the fee mechanics + staking + governance; we do not draw a strict conclusion about replaceability.
  • Evidence: Tier‑1 — https://iqai.com/whitepaper.pdf
  • Why sufficient / why not (one line): given explicit token roles and the absence of a comparison of alternatives, we record 0 (conservatively).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://iqai.com/whitepaper.pdf Tier‑1: description of ATP (Agent Tokenization Platform) and EOAI; the role of IQ (fees paid in IQ, governance token, staking/hiIQ), the principle “every tokenized agent has an IQ pair”, launch partner Fraxtal.
Tier‑1 https://app.iqai.com/ Tier‑1: public demo artifact of ATP (agent catalog, chain Fraxtal, agent addresses such as Sophia).
Tier‑1 https://github.com/IQAIcom/adk-ts Tier‑1: SDK for building AI agents (multi‑LLM, tools, workflows) + code examples.
Tier‑1 https://github.com/IQAIcom/adk-ts/releases Tier‑1: SDK versioning/releases; the release notes mention new components (for example, the MCP docs server).
Tier‑1 https://github.com/IQAIcom/adk-ts/security/advisories Tier‑1: the repository’s security advisories.
Tier‑1 https://etherscan.io/token/0x579cea1889991f68acc35ff5c3dd0621ff29b0c9 Tier‑1: the onchain fact of IQ ERC‑20 (address, max total supply).
Tier‑1 https://code4rena.com/reports/2025-01-iq-ai Tier‑1: audit of the IQ AI smart contract system (scope/findings/mitigation review).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top