Skip to main content

Spectre AI

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

Spectre AI — an AI/Research project: a web platform for market analysis (sentiment/technical/on-chain) with an “AI Search Engine” and token gating; token: SPECTRE (Ethereum).

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 “one‑stop” research dashboard for the crypto market: sentiment, technical indicators and onchain insights.
  • Who it’s for: traders/investors who want to quickly gather signals and context on tokens.
  • Why onchain/token: the SPECTRE token is used for access gating (tiers) and for funding development via a tax mechanic; the service also claims a subscription option.
  • What you can actually touch (Tier‑1): the AI Search Engine DApp on the project website (see links_* → App / Demo).

How it works (very briefly)

  1. The user does: opens the “AI Search Engine” (dApp/web) and selects a market/token.
  2. The system does: aggregates data (prices/volume, onchain metrics, social discussions) and forms AI explanations/summaries (sentiment/TA/onchain).
  3. The user gets: a dashboard with metrics and AI summaries/hints.
  4. Where the blockchain is: onchain — mainly the SPECTRE token and its trading/tax mechanics; the product computations and the ML part are offchain.
  5. Token role (if any): holding SPECTRE unlocks access “tiers”; part of the token tax funds development/marketing/liquidity (per the whitepaper).

Quick links: AI thesis fit

Project passport

Field Value
Project name Spectre AI
Also known as (aliases) Spectre; SPECTRE; $SPECT
Logo (logo) ../assets/166_spectre-ai_logo.svg
Token symbol (ticker) SPECTRE
Category AI/Research | Analytics
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 0x9cf0ed013e67db12ca3af8e7506fe401aa14dad6
Token model (token_type) utility (fee-mechanism)
Max supply 10,000,000 SPECTRE
Issuance fixed (per max supply)
Tokenomics (tokenomics, brief) a 5% buy/sell tax is claimed; access levels (tiers) via holding SPECTRE; LP lock/renounce — as claims in the whitepaper
Governance —
Admins/keys the whitepaper claims “contract renounced”, but the contract contains Ownable logic (the current onchain owner requires separate verification)
Audit —
Bug bounty —
Team (team) — (roles/profiles are listed on the website)
Funding (investors/funding) —
AI component (ai_component) ML sentiment/TA/on-chain data analysis
Use‑case (use_case) AI crypto market research dashboard
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 2
Last verified 2026-02-11

General project overview

Spectre AI describes itself as an “AI‑powered on‑chain research platform” for crypto trading: a single web dashboard that combines sentiment analysis (X/social media), technical indicators and onchain data to provide the user with summaries and hints.

Important: “on‑chain” in this description refers mainly to the data being analyzed and to the SPECTRE token, not to the ML logic being executed on the blockchain.

Features/modules

  • AI Search Engine / Research Zone: onchain/sentiment/TA metrics for the selected token.
  • Sentiment Analysis: AI‑generated summaries of the activity/sentiment around a project (tiers).
  • Technical Analysis: a set of indicators and AI explanations.
  • Tier‑based access: some functions are unlocked when holding a certain amount of SPECTRE; the website also lists a subscription option.

Typical scenarios

  • Scenario 1 (token research): the user opens the platform → selects a token → receives an AI summary of sentiment/TA and onchain indicators.
  • Scenario 2 (trend monitoring): the user uses the landing/heatmap/screeners → tracks market changes.

Getting started (wallet/network)

  • What you need: access to the web app; for token gating — an EVM wallet and SPECTRE.
  • Network/chain: Ethereum (the SPECTRE token).
  • Fees: Ethereum gas when buying/transferring SPECTRE.

Architecture/tech (non‑AI)

  • Components: web client + backends/data providers (social/prices/onchain) + AI analysis; onchain — the ERC‑20 token.
  • Participant roles: platform users; token holders; the development team.
  • Where logic runs: ML/aggregation — offchain; onchain — the token and its trading/tax logic.
  • Dependencies: social media/market/explorer data; Ethereum.

Token/economics (expanded, no forecasts)

  • Token utility: the website lists tier‑based access based on holding SPECTRE; the whitepaper lists the purposes of distributing the tax proceeds (product dev/liquidity/marketing).
  • Protocol necessity drivers: the product can also work by subscription (claimed), so the token is not strictly necessary for access.
  • Who pays fees: Ethereum users when operating with the token; a 5% buy/sell tax is also claimed.
  • Where fees go: the whitepaper describes the distribution of the tax to development/liquidity/marketing (specific onchain addresses are not given).
  • Issuance/burn: max total supply 10,000,000 (per the explorer).
  • Security/incentive mechanisms: — (staking/slashing are not described as an active mechanic).
  • Distribution and token issuance schedule: — (not explicitly given).
  • Treasury: —.

Governance

  • Who makes decisions: the team/product operator (a DAO/governance process is not described in Tier‑1 sources).
  • How protocol parameters change: via product updates/access rules (tiers) and publications in the official channels; no formal onchain governance process was found.
  • Where decisions are discussed/made: X/Telegram/Medium (see links_*).
  • Keys/multisig: not established (the token contract has Ownable logic; the current owner/restrictions require separate onchain verification).

Security and incidents

  • Audits: no public Tier‑1 audit reports found.
  • Bug bounty: —.
  • Incidents: — (not recorded in Tier‑1 sources).
  • Threat model: the risk of “AI output” without public metrics/benchmarks; dependence on offchain data providers; token risks (tax model/admin functions, if ownership is not renounced).

Project status and timeline

  • Current status: active (a web product and a token on Ethereum mainnet per links_*).
  • Key releases/milestones: —.
  • Roadmap: https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap

Ecosystem/integrations

  • Integrations: Ethereum (token), market/social/onchain data providers (offchain).
  • Partners: — (not listed in the reviewed Tier‑1 sources).
  • Where it’s actually used: as a research dashboard/AI search over the market (see Website/Whitepaper in links_*).

AI component of the project

  • What is real AI here? The Tier‑1 whitepaper describes an ML pipeline (data collection/feature engineering/modeling) and product AI modules (sentiment/TA assistants).
  • What is truly onchain? The SPECTRE ERC‑20 token on Ethereum; the onchain part of the product mainly boils down to the token.
  • Why is a token needed? holding SPECTRE is used as access to tiers; the tax mechanic funds development/liquidity/marketing (per the whitepaper).
  • Red flags (based on the information found): onchain‑washing (the word “on‑chain” may create the impression that the logic/AI runs on the blockchain); AI‑washing — medium (the algorithms are “confidential”, few technical details/benchmarks).

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 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): the AI part is described as working product modules, so the intent flag is not used.
  • Evidence: Tier‑1 — https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md
  • Why sufficient / why not (one line): the whitepaper describes AI functions and the product, not only plans.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): ML modules form insights from sentiment/technical/onchain data and deliver “actionable” summaries.
  • Evidence: Tier‑1 — https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md ; https://spectreai.io/
  • Why sufficient / why not (one line): Tier‑1 describes the purpose of the AI analytics as part of the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the website provides access to the “AI Search Engine DApp” and a description of the modules (Sentiment/TA/Monarch, etc.).
  • Evidence: Tier‑1 — https://spectreai.io/ (the “AI Search Engine DApp” button and the product descriptions)
  • Why sufficient / why not (one line): this is a public product interface/demo of access to the platform.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md
  • Why sufficient / why not (one line): model quality metrics/benchmarks are not published.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the whitepaper gives a high‑level pipeline, but the specific algorithms/versions are declared confidential.
  • Evidence: Tier‑1 — https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md
  • Why sufficient / why not (one line): insufficient technical details for a reproducible/verifiable description of the model.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: SPECTRE token: 0x9cf0ed013e67db12ca3af8e7506fe401aa14dad6
  • Evidence: Tier‑1 — https://etherscan.io/token/0x9cf0ed013e67db12ca3af8e7506fe401aa14dad6
  • Why sufficient / why not (one line): the token contract is verified and contains a max total supply of 10M.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: in the confirmed sources, onchain logic other than the token is not identified by addresses/contracts.
  • Evidence: Tier‑1 — https://spectreai.io/ ; https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md
  • Why sufficient / why not (one line): the product logic (analysis/AI) is described as an offchain service.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the research platform could exist as a Web2 service; the blockchain is not a critical component for performing the AI analytics.
  • Evidence: Tier‑1 — https://spectreai.io/
  • Why sufficient / why not (one line): “onchain” refers to the data/context of the analysis, not to the necessity of a blockchain for the service to operate.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, SPECTRE, on Ethereum.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x9cf0ed013e67db12ca3af8e7506fe401aa14dad6
  • Why sufficient / why not (one line): the token is confirmed by the explorer and listed on the website.
  • 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 token is used as access (holding tiers), but an explicit “payment for the service with the token” model is not described in Tier‑1.
  • Evidence: Tier‑1 — https://spectreai.io/
  • Why sufficient / why not (one line): gating ≠ payment; the website separately lists a subscription option.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): staking/slashing mechanics are not described as active.
  • Evidence: Tier‑1 — https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md
  • Why sufficient / why not (one line): tax flows are described, but not protocol collateral/penalties.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance mechanics via the token are not described.
  • Evidence: Tier‑1 — https://spectreai.io/ ; https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md
  • Why sufficient / why not (one line): there is no description of voting/a DAO.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): access to functions can be provided via a subscription; token gating is a replaceable access model.
  • Evidence: Tier‑1 — https://spectreai.io/ (the “hold tokens or subscribe” description)
  • Why sufficient / why not (one line): the existence of an alternative (subscription) makes the token not strictly necessary.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://spectreai.io/ The product and modules (AI Search Engine, sentiment/TA/onchain), the existence of public access/demo and token gating/subscription
Tier‑1 https://spectre-ai-prediction-bot.gitbook.io/spectre-roadmap/spectre-ai-ai-powered-on-chain-search-engine-the-whitepaper.md The AI pipeline and tokenomics claims (5% buy/sell tax, supply 10M, utility)
Tier‑1 https://etherscan.io/token/0x9cf0ed013e67db12ca3af8e7506fe401aa14dad6 The SPECTRE token contract and max total supply 10,000,000

No comments to display

Back to top