Skip to main content

Aitra

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

Aitra — an AI platform for crypto market tracking/analytics (Tier‑1 docs); the onchain part and token utility are not established 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: an AI platform for crypto market tracking and analysis (whale wallets, “VIP calls”, DCA orders).
  • Who it’s for: traders and investors who need alerts/insights on market activity.
  • Why onchain/token: the role of onchain and the token utility are not established per Tier‑1 sources.

How it works (very briefly)

  1. The user does: configures tracking/alerts and consumes analytics.
  2. The system does: aggregates and analyzes data (including movements of “whale” wallets, “VIP calls”, DCA orders) and generates signals/observations.
  3. The user gets: notifications and conclusions that help navigate the market.
  4. Where the blockchain is: it is not established per Tier‑1 sources which part of the product runs onchain.
  5. Token role (if any): not described per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Aitra
Also known as (aliases) —
Logo (logo) ../assets/717_aitra_logo.svg
Token symbol (ticker) —
Category AI/Analytics | Trading tools
Primary chain (chain) —
Type —
Network status —
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) —
Token (standard) —
Token contract —
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 market analytics + tracking (whale wallets + "VIP calls" + DCA tracking)
Use‑case (use_case) market insights + alerts (traders + investors)
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 0 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Tier‑1 documentation describes Aitra as an AI platform for crypto market tracking and analysis (whale wallets, “VIP calls”, DCA tracking) and separately — an “AITR trading bot”.

The following are not established in the current set of Tier‑1 sources: the target network/token standard, onchain logic (if it exists) and the token utility. Potentially inconsistent artifacts also remain in this card (for example, a separate explorer URL and a code repository resembling blockchain client code) — additional cross‑checking of the correspondence “docs ↔ network/token ↔ code” is required.

Features/modules

  • Whale wallet tracking: tracking large wallets.
  • VIP group call tracking: analysis of “VIP calls” signals.
  • DCA order tracking: tracking DCA strategies/orders.

Typical scenarios

  • Scenario 1: a user configures tracking of whale wallets/“VIP calls”/DCA → receives alerts/analytics.
  • Scenario 2: a user reads the documentation → understands which data and modules are available.
  • Scenario 3: a developer studies the repository → gets access to the source code (if applicable).

Getting started (wallet/network)

  • What you need: not established per Tier‑1 sources.
  • Network/chain: not established.
  • Fees: not established.

Architecture/tech (non‑AI)

  • Components: product documentation (GitBook), a (possible) web application/bot (the demo URL is not confirmed by Tier‑1), a code repository, a separate explorer URL (the network requires clarification).
  • Participant roles: users (consume analytics), developers, token holders (if the token is used).
  • Where logic runs: not established.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not described per Tier‑1 sources.
  • Protocol necessity drivers: —.
  • Who pays fees: —.
  • Where fees go: —.
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

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

Security and incidents

  • Audits: No Tier‑1 audit report(s) found.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: —.

Project status and timeline

  • Current status: not established.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? Tier‑1 docs describe AI analytics/tracking (whale wallets, “VIP calls”, DCA tracking) and a separate “AITR trading bot”.
  • What is truly onchain? It is not established per Tier‑1 sources which part of the product runs onchain and on which network; a separate explorer URL is given in this card, but the network/addresses/contracts are not recorded.
  • Why is a token needed? Per Tier‑1 sources, the token utility is not described.
  • Red flags (based on the information found): mixing of sources/artifacts (docs about an AI platform vs separate links to an explorer/code) — verification of correspondence is required; there is no Tier‑1 description of onchain logic and the token utility.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 0
Token necessity low 0
Evidence Tier‑1 partially present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): A roadmap/declaration of AI plans (as intent) is not identified per Tier‑1.
  • Evidence: Tier‑1 — https://aitra.gitbook.io/aitra
  • Why sufficient / why not (one line): There is a Tier‑1 description of AI features, but no separate Tier‑1 roadmap/plan, and AI intent is not set when AI reality is present.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The project describes an AI platform for market tracking/analysis (whale wallets, “VIP calls”, DCA tracking) and an AI trading bot (AITR).
  • Evidence: Tier‑1 — https://aitra.gitbook.io/aitra, https://aitr-bot.gitbook.io/token
  • Why sufficient / why not (one line): Tier‑1 documentation directly describes the functions of the AI component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Demos/examples of the AI component in operation are not established.
  • Evidence: Tier‑1 — https://aitra.gitbook.io/aitra, https://aitr-bot.gitbook.io/token
  • Why sufficient / why not (one line): There is no verifiable link to a demo/application with reproducible examples in Tier‑1 sources.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://aitra.gitbook.io/aitra
  • Why sufficient / why not (one line): Metrics/benchmarks were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the AI part is not established.
  • Evidence: Tier‑1 — https://aitr-bot.gitbook.io/token
  • Why sufficient / why not (one line): There is no Tier‑1 documentation with model architecture/versions (there is only a high‑level description).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 0
  • Chain: —
  • Addresses/identifiers: —
  • Evidence: Tier‑1 — https://explorer.aitra.io/
  • Why sufficient / why not (one line): The network/addresses/contracts are not recorded and not confirmed per Tier‑1 sources within this card.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no confirmed onchain logic of the product in the available sources.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no justification of onchain criticality per Tier‑1/2.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a claimed token, but the token parameters are not established per Tier‑1 sources.
  • Evidence: Tier‑2 — https://coinmarketcap.com/currencies/aitra/
  • Why sufficient / why not (one line): There is a token profile (Tier‑2), but it does not replace a Tier‑1 specification/contract.
  • 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): It is not established that the token is used to pay for the service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 source with a description of payment utility.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties using the token are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of the incentive mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): It is not established that the token is used for governance.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics with the token.
  • 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 established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no data to justify replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://aitra.gitbook.io/aitra Description of the AI platform and claimed features (whale wallets, “VIP calls”, DCA tracking).
Tier‑1 https://aitr-bot.gitbook.io/token Description of the “AITR trading bot” and the claimed use of AI (high‑level).
Tier‑1 https://aitrasolana.com/ The official website given in the Tier‑1 documentation.
Tier‑1 https://github.com/aitracoinofficial/AITRA Public code repository (development artifact).
Tier‑1 https://explorer.aitra.io/ A separate explorer URL is given (the network/addresses/contracts require verification).
Tier‑2 https://coinmarketcap.com/currencies/aitra/ Token profile (for reference; not proof of technology/utility).

No comments to display

Back to top