AIXBT
AIXBT (AIXBT) — 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).
AIXBT — an AI/Agents | DeFi | Infra project: a real‑time market intelligence platform (terminal + chat), plus the “AIXBT Agent” (an autonomous account on X) that publishes insights and replies to mentions. Token: AIXBT (ERC‑20, Ethereum; addresses on Base and Solana are also claimed).
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 terminal/service that collects market and social signals and gives the trader a “summary/signals” via chat and dashboards.
- Who it’s for: traders/analysts who need “quick reconnaissance” on narratives and what is happening in crypto social media.
- Why onchain/token: the AIXBT token (ERC‑20) is confirmed onchain; as described, token holders get access to the platform/plans (utility access).
- What you can actually touch (Tier‑1): the chat page
aixbt.tech/chat+ documentation with example queries.
How it works (very briefly)
- The user does: opens the terminal and asks a question in the chat about “what is heating up right now/which topics/which tokens”.
- The system does: aggregates data (social signals, market indicators, news feeds, blockchain analytics, etc.) and returns an answer/summary; there are different model modes (Base/Indigo).
- The user gets: a list of trends/narratives, a brief analysis and “signals worth tracking”.
- Where the blockchain is: the AIXBT token exists onchain (Ethereum; addresses on Base/Solana are also claimed).
- Token role: per the token pages, holding/staking AIXBT is used as the access criterion for the “Ultimate plan” and analytics features.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AIXBT |
| Also known as (aliases) | AIXBT Agent | AIXBT Terminal | AIXBT Indigo |
| Logo (logo) | ../assets/69_aixbt_logo.svg |
| Token symbol (ticker) | AIXBT |
| Category | AI/Agents | DeFi | Infra |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2 |
| Token model (token_type) | utility (access + upgrades) |
| Max supply | 6,112,053.53 |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | max total supply ~6.112M (Etherscan); access to Ultimate by holding/staking AIXBT; there are addresses on Base/Solana. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | semantic LLM + analytics for crypto intelligence |
| Use‑case (use_case) | market intelligence terminal + AI agent |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 1 / token_score 1 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://aixbt.tech |
| Docs | https://aixbt-labs.gitbook.io/v1 |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2 |
| App / Demo | https://aixbt.tech/chat |
| X | https://twitter.com/aixbt_agent |
| Discord | — |
| Telegram | https://t.me/aixbtportal |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/aixbt |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/aixbt/ |
General project overview
AIXBT positions itself as a real‑time market intelligence platform that “detects emerging trends” and gives the user signals/insights based on a set of sources (social media, market indicators, news, onchain analytics and proprietary datasets). The documentation describes two parts: AIXBT Agent (the @aixbt_agent account on X, which publishes and replies) and AIXBT Terminal (the interface for the trader).
From the verifiability standpoint, Tier‑1 confirms: the existence of the terminal, the chat modes (Base/Indigo) and the MCP integration; onchain, the AIXBT token (ERC‑20) and the max supply on Etherscan are confirmed. The token documentation describes that access to the Ultimate plan may depend on the amount of AIXBT held/staked.
Features/modules
- Chat (Base/Indigo): a chat interface for narrative questions (example prompts in the docs).
- Terminal: a list of projects, momentum/scoring, daily reports, etc. (Tier‑1 overview/features).
- MCP Server: integration into Claude Desktop via MCP (Tier‑1 MCP setup).
- AIXBT Agent (X): an autonomous account that publishes and replies to mentions (Tier‑1 overview).
Typical scenarios
- Scenario 1 (trader): asks in the chat “what is heating up right now?” → receives the top topics/narratives and “plays worth tracking”.
- Scenario 2 (analyst): uses the terminal and daily reports → receives regular summaries (Tier‑1 features).
- Scenario 3 (power user): connects MCP to Claude Desktop → asks questions via the MCP server and receives answers from AIXBT (Tier‑1).
Getting started (wallet/network)
- What you need: web access to
aixbt.techfor the terminal/chat; for MCP — Claude Desktop and an API key (Tier‑1). - Network/chain: the AIXBT token is on Ethereum; the docs also list addresses for Base and Solana.
- Fees: network fees arise only for onchain operations with the token; use of the terminal — per the terms of the subscription/plans (Tier‑1 features).
Architecture/tech (non‑AI)
- Components: web terminal + chat; the “agent” on X; the MCP server for Claude Desktop.
- Participant roles: terminal users, power users (MCP), token holders (access gating).
- Where logic runs: analytics/inference — offchain; onchain — the token contracts (Tier‑1 token page).
- Dependencies: external data providers (e.g., Coingecko/DefiLlama are mentioned), social media/news, blockchain analytics.
Token/economics (expanded, no forecasts)
- Token utility: Etherscan states that token holders gain access to the analytics platform; the docs describe eligibility for the Ultimate plan by holding/staking.
- Protocol necessity drivers: Tier‑1 describes that access to Ultimate may require 600k AIXBT (hold) or 500k AIXBT (stake) (Tier‑1).
- Who pays fees: token users (gas for onchain operations).
- Where fees go: — (not described).
- Issuance/burn: the max total supply is stated on Etherscan (Tier‑1).
- Security/incentive mechanisms: stake on Virtuals for access to the plan (Tier‑1).
- Distribution and token issuance schedule: — (not confirmed by Tier‑1).
- Treasury: —.
Governance
- Who makes decisions: — (no Tier‑1 governance found).
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: — (no Tier‑1 audit reports were found in the current set of links).
- Bug bounty: —.
- Incidents: —.
- Threat model: per the materials found, the AI claims are not accompanied by verifiable benchmarks; the risks of centralized logic and non‑transparent datasets also remain, and whether the token is mandatory for access requires separate verification.
Project status and timeline
- Current status: active (the website/terminal and docs are available).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: MCP Server for Claude Desktop; data provider partners are mentioned (e.g., Coingecko and DefiLlama) (Tier‑1).
- Partners: —.
- Where it’s actually used: the web terminal and the X agent (Tier‑1).
AI component of the project
- What is real AI here? a chat agent and an analytics engine for detecting trends/narratives based on multiple sources (Tier‑1 docs).
- What is truly onchain? the AIXBT token (ERC‑20) on Ethereum; the docs also list contract addresses for Base and Solana (Tier‑1).
- Why is a token needed? access gating: eligibility for the “Ultimate plan” by holding/staking; on Etherscan — “token holders gain access to analytics platform” (Tier‑1).
- Red flags (based on the information found): AI‑washing (no quality metrics); token‑washing (verify how mandatory the token actually is vs a subscription).
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| 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): AI is described as a current part of the product, not as an “intent”.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1
- Why sufficient / why not (one line): the intent flag is not needed.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AIXBT provides real‑time trend detection and narrative analytics via the chat and the terminal.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1 , https://aixbt-labs.gitbook.io/v1/overview/chat
- Why sufficient / why not (one line): Tier‑1 describes the purpose and the data sources (high‑level).
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): there is a public chat page + docs with example prompts for working with the agent.
- Evidence: Tier‑1 — https://aixbt.tech/chat , https://aixbt-labs.gitbook.io/v1/overview/chat
- Why sufficient / why not (one line): this is a reproducible “what you can touch” (the chat and example queries).
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1
- Why sufficient / why not (one line): there are no reproducible quality metrics/benchmarks in Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the terminal modules (chat/reports/scoring) and the MCP integration are described.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1/overview/features , https://aixbt-labs.gitbook.io/v1/sdk-docs/mcp-setup
- Why sufficient / why not (one line): this is a sufficient high‑level technical description layer for 1.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum.
- Addresses/identifiers: the AIXBT token (ERC‑20)
0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2. - Evidence: Tier‑1 — https://etherscan.io/token/0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2 , https://aixbt-labs.gitbook.io/v1/aixbt-token
- Why sufficient / why not (one line): the explorer and the docs confirm the address and the multi‑chain addresses.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: Tier‑1 does not confirm protocol contracts/mechanics other than the token.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1
- Why sufficient / why not (one line): the product is described as an offchain platform.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the terminal/chat could exist without a blockchain; onchain is mostly the access token.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1
- Why sufficient / why not (one line): there is no Tier‑1 proof of a critical dependency on onchain.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, AIXBT (ERC‑20), and it is used as an access criterion.
- Evidence: Tier‑1 — https://etherscan.io/token/0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2 , https://aixbt-labs.gitbook.io/v1/aixbt-token
- Why sufficient / why not (one line): the onchain fact of the token is confirmed.
- 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 token is used as access gating (the Ultimate plan by hold/stake of AIXBT).
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1/aixbt-token , https://etherscan.io/token/0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2
- Why sufficient / why not (one line): Tier‑1 explicitly links token holdings to “access to the analytics/plan”.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentive/slashing/collateral mechanics are not described in Tier‑1.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1
- Why sufficient / why not (one line): we keep 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance via the token is not described in Tier‑1.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1
- Why sufficient / why not (one line): no mechanics.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): the replaceability of the token with an alternative access mechanism is not proven by Tier‑1.
- Evidence: Tier‑1 — https://aixbt-labs.gitbook.io/v1/aixbt-token
- Why sufficient / why not (one line): without Tier‑1 — we keep 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://aixbt-labs.gitbook.io/v1 | description of the product and the data sources; AIXBT Agent + Terminal. |
| Tier‑1 | https://aixbt-labs.gitbook.io/v1/overview/chat | AI_2 demo/guide: description of the chat, the Base/Indigo modes and example prompts. |
| Tier‑1 | https://aixbt-labs.gitbook.io/v1/overview/features | features and plans (chat, reports, MCP server). |
| Tier‑1 | https://aixbt.tech/chat | the public chat page of the terminal (touchable demo). |
| Tier‑1 | https://aixbt-labs.gitbook.io/v1/sdk-docs/mcp-setup | MCP setup: npx @aixbt/mcp-server and an API key for Claude Desktop. |
| Tier‑1 | https://aixbt-labs.gitbook.io/v1/aixbt-token | multi‑chain addresses of the token (Ethereum/Base/Solana) and the Ultimate plan criterion. |
| Tier‑1 | https://etherscan.io/token/0x0D37aF9D8AE74F35F3A38bD2a08FcB29890Ca6d2 | the onchain fact of the AIXBT token (ERC‑20), max total supply and “access to analytics platform”. |
No comments to display
No comments to display