Skip to main content

Heurist

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

Heurist — an AI/Agents / Infra project (full‑stack infrastructure for AI agents and AI services), token (symbol: HEU).

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 ecosystem of products for AI agents: a marketplace/mesh of specialized agents, a crypto Q&A agent, and payment rails for micropayments.
  • Who it’s for: for developers and teams that need AI agents/tools and a payment model for AI services; for users who need a “research agent” for the crypto market.
  • Why onchain/token: the HEU token is claimed as a mechanism for paying for AI services, staking and governance; it is also claimed as the gas token for Heurist Chain.
  • What you can actually touch (Tier‑1): ask.heurist.ai (Ask Heurist) and/or mesh.heurist.ai (Heurist Mesh).

How it works (very briefly)

  1. The user does: chooses a product (Ask Heurist / Mesh / API) and submits a query or calls the API.
  2. The system does: gathers context (market/social media/onchain data, etc.) and processes the query through a multi‑agent architecture.
  3. The user gets: an answer/report/result of the AI agent’s work (fast or “deep” mode for Ask Heurist).
  4. Where the blockchain is: the onchain components are described as token/staking contracts and payment contracts (Base/other networks) + the claimed Heurist Chain.
  5. Token role (if any): HEU: payment for AI services (with a credit bonus), staking (stHEU) and voting in governance (as claimed in the docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name Heurist
Also known as (aliases) Heurist AI; HEU
Logo (logo) ../assets/449_heurist-ai_logo.png
Token symbol (ticker) HEU
Category AI/Agents | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum L1 / Base L2)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xec463D00aa4dA76fb112cD2e4AC1C6BeF02da6ea
Token model (token_type) utility (governance)
Max supply 1,000,000,000
Issuance fixed
Tokenomics (tokenomics, brief) HEU: max supply 1B; distribution and vesting are described in the docs
Governance governance via token voting (as claimed)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent marketplace + AI services
Use‑case (use_case) AI agents + micropayments
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 2 / 2
Last verified 2026-02-11

General project overview

Heurist positions itself as “full‑stack infrastructure for the AI economy”: from compute and agent infrastructure to payments and a (claimed) own L2 chain. The public documentation describes the key products:

  • Heurist Mesh — a marketplace of specialized AI agents/tools (including MCP compatibility).
  • Ask Heurist — an AI agent for questions/research on the crypto market with fast and “deep” modes.
  • HEU token and credits — an access/payment model for AI services: credits are purchased with crypto, and paying with HEU gives a credit bonus.

Features/modules

  • Ask Heurist: quick answers and long reports (Deep Mode) based on aggregated data.
  • Heurist Mesh: a set of agents/tools and integrations via API/MCP.
  • Credits/payment: purchase of credits, pay‑per‑use and a discount/bonus when paying with HEU (as claimed in the docs).
  • HEU staking: staking with the issuance of stHEU and auto‑compounding (as claimed in the docs).

Typical scenarios

  • Scenario 1 (user): asks a question in Ask Heurist → gets a brief answer or a detailed report with market/social/onchain context.
  • Scenario 2 (developer): integrates Mesh/API → uses specialized agents in an application or automates a workflow.
  • Scenario 3 (HEU holder): stakes HEU → receives stHEU and returns from emissions + protocol revenue (as claimed in the docs).

Getting started (wallet/network)

  • What you need: open ask.heurist.ai (web) and/or mesh.heurist.ai; for staking — a wallet on the Base network.
  • Network/chain: Base (stake portal) and Ethereum L1 (HEU contract) — per the docs.
  • Fees: network fees (L1/L2) for onchain operations; the cost of queries/credits is described in the docs.

Architecture/tech (non‑AI)

  • Components: web applications (Ask Heurist, Mesh), API/integration layers, HEU/staking/payment contracts (Base and other networks).
  • Participant roles: users of AI services, developer‑integrators, HEU holders/stakers.
  • Where logic runs: AI computation and data aggregation — offchain; token/staking/payment accounting — onchain (EVM networks).
  • Dependencies: external data sources (exchanges/DEX analytics/social media/onchain data — listed in the Ask Heurist docs).

Token/economics (expanded, no forecasts)

  • Token utility: HEU is claimed for paying for AI services, staking (with returns) and governance; it is also claimed as the gas token of Heurist Chain.
  • Protocol necessity drivers: some functions are tied to holding/staking (a credit bonus when paying with HEU; staking returns).
  • Who pays fees: users pay for credits/queries; onchain operations require network fees (for example, Base for staking).
  • Where fees/revenue go: dynamic staking rewards are claimed as a share of revenue from API credit purchases.
  • Issuance/burn: max supply 1B; distribution/vesting are given in the tokenomics docs; additional burn details are not established per Tier‑1.
  • Incentive mechanisms: HEU staking → stHEU, auto‑compounding; unstaking — a 30‑day lock‑up.
  • Distribution and token issuance schedule: given in the tokenomics docs (categories, TGE unlock, cliff, vesting).
  • Treasury: a Protocol Treasury is mentioned as a distribution category (governance terms are not established per Tier‑1).

Governance

  • Who makes decisions: governance via voting (HEU utility is claimed); the specific process/venues are not described in Tier‑1 at the level of “how exactly”.
  • How protocol parameters change: via protocol/service updates; onchain parameters — via governance (claimed).

Security and incidents

  • Audits: not established per Tier‑1.
  • Bug bounty: not established per Tier‑1.
  • Incidents: not established per Tier‑1.
  • Threat model: data/source quality risks, API/key security, smart contract risks (if staking/payments are used).

Project status and timeline

  • Current status: active (products available on the web).
  • Key milestones: the tokenomics include historical mining/airdrop “seasons” (in the docs).
  • Roadmap: not established per Tier‑1.

Ecosystem/integrations

  • Integrations: Mesh is MCP‑compatible; payments/credits — USDC on Base via x402 (in the docs).
  • Partners: not established per Tier‑1.
  • Where it’s actually used: Ask Heurist for token/market research; Mesh — for embedding agents into applications/automation.

AI component of the project

  • What is real AI here? Heurist offers AI products (Ask Heurist, Mesh/agents) and describes a multi‑agent architecture and data sources for generating answers/reports.
  • What is truly onchain? HEU contracts (and staking/payment contracts) on EVM networks; onchain is used for the token, staking and payment infrastructure (per the docs).
  • Why is a token needed? The docs list the HEU utilities: payment for AI services, staking for revenue/emissions, governance voting, gas for Heurist Chain.
  • Red flags (based on the information found): the onchain part may be auxiliary relative to the offchain AI services (onchain‑washing risk); what to double‑check: the actual role of Heurist Chain and whether HEU is necessary for payment (there are USDC/credit payment modes).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity medium 2
Evidence Tier‑1 present (AI/OC/TK) 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): A separate roadmap about AI in the form of “plans” is not recorded by Tier‑1.
  • Evidence: Tier‑1 — https://docs.heurist.ai/introduction
  • Why sufficient / why not (one line): The documentation describes products and positioning, but not a formalized roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Ask Heurist/Heurist Mesh provide AI agents that answer queries and execute agentic workflows with external data sources.
  • Evidence: Tier‑1 — https://docs.heurist.ai/introduction; Tier‑1 — https://docs.heurist.ai/ask-heurist
  • Why sufficient / why not (one line): Tier‑1 describes the AI agent products and their functionality/data sources.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): Ask Heurist is available as a web application; Mesh is available as a web product for browsing agents and their tools.
  • Evidence: Tier‑1 — https://docs.heurist.ai/ask-heurist; Tier‑1 — https://docs.heurist.ai/introduction
  • Why sufficient / why not (one line): Tier‑1 has direct links to Ask Heurist and Mesh as available products.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.heurist.ai/ask-heurist
  • Why sufficient / why not (one line): Tier‑1 describes modes/data sources but does not publish formalized quality metrics/benchmarks.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The products (Mesh, Ask Heurist) and the general architecture/query processing layers and data sources are described.
  • Evidence: Tier‑1 — https://docs.heurist.ai/introduction; Tier‑1 — https://docs.heurist.ai/ask-heurist
  • Why sufficient / why not (one line): There is a sufficiently detailed Tier‑1 description of the components and layers.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum | Base | ZKsync Era (the docs also list payment contracts on other networks)
  • Addresses/identifiers: HEU token address (Ethereum) + staking/payment contracts (Base and others)
  • Evidence: Tier‑1 — https://docs.heurist.ai/protocol-overview/contract-addresses
  • Why sufficient / why not (one line): Tier‑1 publishes the list of contracts and the deployment networks.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: HEU staking (stHEU) and payment infrastructure/contracts for purchases/payment of credits (per the docs).
  • Evidence: Tier‑1 — https://docs.heurist.ai/protocol-overview/stake; Tier‑1 — https://docs.heurist.ai/protocol-overview/credits
  • Why sufficient / why not (one line): Tier‑1 describes the onchain logic of staking and payments (not reducible to “just a token”).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the AI services (Ask/Mesh) can work offchain; onchain in Tier‑1 is described as payments/staking/token, but criticality for the operation of the AI agents is not proven.
  • Evidence: Tier‑1 — https://docs.heurist.ai/ask-heurist; Tier‑1 — https://docs.heurist.ai/protocol-overview/contract-addresses
  • Why sufficient / why not (one line): There is no Tier‑1 “replaceability test” proving the necessity of onchain for the core AI functionality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, HEU.
  • Evidence: Tier‑1 — https://docs.heurist.ai/protocol-overview/tokenomics; Tier‑1 — https://docs.heurist.ai/protocol-overview/contract-addresses
  • Why sufficient / why not (one line): Tier‑1 describes HEU and publishes contract addresses, so “no token” is incorrect.
  • 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): HEU is used to pay for AI services (and gives a credit bonus when paying with HEU).
  • Evidence: Tier‑1 — https://docs.heurist.ai/protocol-overview/credits; Tier‑1 — https://docs.heurist.ai/protocol-overview/tokenomics
  • Why sufficient / why not (one line): Tier‑1 explicitly states “Pay for AI services” and a credit bonus when paying with HEU.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): HEU staking to “secure the network” and receive protocol rewards/revenue.
  • Evidence: Tier‑1 — https://docs.heurist.ai/protocol-overview/stake; Tier‑1 — https://docs.heurist.ai/protocol-overview/tokenomics
  • Why sufficient / why not (one line): Tier‑1 describes staking (stHEU), the lock‑up and the sources of rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): HEU is used for voting on governance decisions (as claimed in the docs).
  • Evidence: Tier‑1 — https://docs.heurist.ai/protocol-overview/tokenomics
  • Why sufficient / why not (one line): The Tier‑1 tokenomics list of utilities includes “Vote on governance decisions”.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): Part of the consumption can be paid not in HEU (for example, pay‑per‑use in USDC), so HEU is not the only payment path.
  • Evidence: Tier‑1 — https://docs.heurist.ai/ask-heurist; Tier‑1 — https://docs.heurist.ai/protocol-overview/credits
  • Why sufficient / why not (one line): Tier‑1 describes USDC payment on Base and a separate bonus when paying with HEU.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.heurist.ai/introduction Overview of the products and positioning (Mesh, Ask Heurist, Heurist Chain), description of the core components
Tier‑1 https://docs.heurist.ai/ask-heurist Ask Heurist as an available product + description of the modes and data sources (demo/usage example)
Tier‑1 https://docs.heurist.ai/protocol-overview/tokenomics HEU utility (pay, stake, governance, gas), max supply 1B and distribution
Tier‑1 https://docs.heurist.ai/protocol-overview/contract-addresses HEU contracts and related contracts by network (OC_1)
Tier‑1 https://docs.heurist.ai/protocol-overview/credits The credit system and payment (including the bonus when paying with HEU)
Tier‑1 https://docs.heurist.ai/protocol-overview/stake HEU staking → stHEU, sources of rewards and lock‑up (TK_2)
Tier‑2 https://www.coingecko.com/en/coins/heurist Context: reference listing
Tier‑2 https://coinmarketcap.com/currencies/heurist-ai/ Context: reference listing

No comments to display

Back to top