How to read a project card

Every project on DecAIHub is described as a card — a structured page that answers three questions: what is genuinely AI here, what is genuinely onchain, and why is the token needed. This page explains the reading order and what to pay attention to.

In short: start with TL;DR and the Passport, then check DecAI Fit, then Evidence. Everything else is for a deeper dive.

Card structure

A project card consists of several sections. Here is the most convenient reading order.

1. Disclaimer

Every card opens with a disclaimer: the page is a reference analysis, not financial advice. DecAIHub does not evaluate price, returns, or entry/exit timing.

2. TL;DR

The "for those unfamiliar with AI" block. Three lines:

What it is — product type and purpose in plain language.
Who it is for — the primary user.
Why onchain/token — one sentence without technical jargon.

If the TL;DR still leaves the project unclear, move on to "How it works" and Evidence for details.

3. How it works

Five steps: what the user does, what the system does, what the user gets, where the blockchain is, and why the token is needed. This is the simplest way to understand the project's mechanics without diving into documentation.

4. Project Passport

A table of short facts: name, chain, category, token type, team, status, and so on. It contains no links — only values.

What to look at first:

Category — starts with AI/<subcategory> (e.g., AI/Compute, AI/Agents). If the AI subcategory is absent, the project may not be directly related to AI.
AI component — what exactly the AI does in the project (3–10 words).
Use case — what it is used for.
DecAI Fit — the overall alignment score with the Decentralized AI thesis.
Last verified — the date the card was last checked.

5. Links

A table of all official and navigational links: website, documentation, repository, social media, audits, aggregator profiles. This is the starting point for independent verification.

6. Project description

An expanded description: what the project is, what problem it solves, who it is for, modules and scenarios. Architecture, tokenomics, governance, security, and status are also covered here.

7. AI component and DecAI Fit

The most important section for understanding verifiability. It contains:

Three questions: what is genuinely AI here, what is genuinely onchain, why is the token needed.
Red flags: whether there are signs of AI-washing, onchain-washing, or token-washing.
DecAI Fit component breakdown: a table with scores across four axes (AI reality, Onchain necessity, Token necessity, Evidence).

Inside the expandable "Details" block, all 0/1 flags are disclosed with justifications: what claim was checked, which source was used, and why 1 or 0 was assigned.

8. Evidence (evidence table)

A table where each row is a single fact showing: the Tier (1/2/3), a link to the source, and a brief description of what exactly it proves.

If Tier-1 is not found for a key claim, this is explicitly recorded as a separate row: Tier‑1 | — | Tier‑1 source for claim X not found.

What to look for to avoid confusing marketing with evidence

Signal	What to do
DecAI Fit: 0/6	No AI component detected via Tier-1 sources as of the verification date
DecAI Fit: 1–2/6	Low alignment as of the verification date; check Evidence — what the conclusion is based on
AI component: `positioning only` or `unknown`	AI is claimed, but no Tier-1 confirmation found as of the verification date
Evidence contains only Tier-3 sources	All sources found are Tier-3 (low verifiability); no Tier-1/Tier-2 found; DecAI Fit capped at 2/6
Last verified > 550 days	The card is outdated; the assessment may have changed
No Tier-1 rows in Evidence	Conclusions are based on Tier-2 context; no Tier-1 confirmation found as of the verification date

Do not confuse with

A card is not a rating. DecAI Fit measures the verifiability of Decentralized AI claims, not the "investment quality."
The Passport is not a description. The Passport contains only short facts; descriptions are in the body of the page.