Skip to main content

Tagger

Tagger (TAG) — 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).

Tagger — an AI/Data | Infra project on the BNB Smart Chain: a platform for data collection/labeling/management and a dataset marketplace with an “AI Copilot” for tasks (Tier‑1 docs). Token: TAG.

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 crowdsourcing platform for data tasks (collection/cleaning/labeling) and a marketplace for buying/renting datasets.
  • Who it’s for: data workers (task performers) and AI teams/companies that need data/labeling.
  • Why onchain/token: the TAG token is used as the currency for paying for tasks/fees/datasets, for staking and as a governance token (Tier‑1 docs).

How it works (very briefly)

  1. The user does: a customer publishes a data task, paying for it in TAG; workers perform the tasks.
  2. The system does: the “AI Copilot” helps with labeling and (as claimed) standardizes the verification of results; the protocol records the authorization/authentication of data (Tier‑1).
  3. The user gets: the customer — a dataset/labeling; the worker — a reward in TAG.
  4. Where the blockchain is: the TAG token on the BNB Smart Chain is confirmed onchain; the details of the onchain logic of the authentication protocol/marketplace are not confirmed in the reviewed sources.
  5. Token role: payments/fees/rewards + staking and governance (Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Tagger
Also known as (aliases) TAG | $TAG | TaggerAI
Logo (logo) ../assets/54_tagger_logo.png
Token symbol (ticker) TAG
Category AI/Data | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) 2024
Project status (status) active
Token (standard) ERC-20
Token contract 0x208bf3e7da9639f1eaefa2de78c23396b0682025
Token model (token_type) utility (payments + staking + governance)
Max supply 405,380,800,000
Issuance PoHW rewards + halving coefficient
Tokenomics (tokenomics, brief) 74.00% PoHW (300B) + 21.06% Tag-to-Pump + 4.93% liquidity (Tier‑1)
Governance governance (as claimed)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI data labeling + model evaluation (human experts)
Use‑case (use_case) data labeling marketplace + dataset trading
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

Tagger positions itself as a “full‑stack AI data solutions platform”: a permissionless hub for collecting, labeling, managing and trading data, where payment for tasks and fees is made in the TAG token. The docs describe the roles (data workers, AI teams, dataset sellers/buyers), the PoHW (proof‑of‑human‑work) model and the reward calculation formulas, as well as the product roadmap.

Features/modules

  • AI Copilot for labeling: assistance to workers in performing labeling tasks and “AI‑driven standardized verification” of results (Tier‑1 docs).
  • Data tasks: publication of tasks for collection/cleaning/labeling with a platform fee (Tier‑1 docs).
  • Data marketplace: buying/renting datasets and usage rights + fees (Tier‑1 docs).
  • PoHW tokenomics: issuance/rewards for completed work + a halving coefficient (Tier‑1 tokenomics).

Typical scenarios

  • Scenario 1 (data customer): an AI team publishes a task, paying for it in TAG → receives a dataset/labeling and ownership rights via the authentication protocol (Tier‑1).
  • Scenario 2 (data worker): a worker performs labeling/cleaning/data collection with the help of the AI Copilot → receives a reward in TAG according to the formula (Tier‑1).
  • Scenario 3 (marketplace): a seller lists a dataset/labeling → the buyer pays TAG + a fee → receives ownership/usage rights (Tier‑1).

Getting started (wallet/network)

  • What you need: access to the Tagger platform/interfaces (the docs describe the product outline; a public Tier‑1 “app/login” was not found in the reviewed sources).
  • Network/chain: the TAG token is on the BNB Smart Chain.
  • Fees: the docs specify platform fees (e.g. 5% for listing data tasks; 1% for listing/deals on the marketplace; Tier‑1).

Architecture/tech (non‑AI)

  • Components: the web platform for tasks/the marketplace, the AI Copilot, the “data authentication protocol” (Tier‑1 docs), the TAG token on BSC (Tier‑1 explorer + tokenomics).
  • Participant roles: data workers; task customers (AI workers/companies); data sellers/buyers.
  • Where logic runs: offchain — task execution/the AI Copilot/verification; onchain — the token/payments and the (claimed) authentication/trading.
  • Dependencies: BNB Smart Chain; third‑party liquidity markets (PancakeSwap is mentioned; Tier‑1 token distribution).

Token/economics (expanded, no forecasts)

  • Token utility: payment for tasks/fees, purchase/use of/subscription to services, customization of AI models, staking; also described as a governance token (Tier‑1).
  • Protocol necessity drivers: the token is the “native currency” for the task/marketplace economy (Tier‑1).
  • Who pays fees: task customers and marketplace participants (listing/handling fees in TAG; Tier‑1).
  • Where fees go: the platform retains a percentage of the fees (5%/1% per the described flows); the specific distribution flow (treasury/burn) was not extracted.
  • Issuance/burn: total supply 405,380,800,000; PoHW issuance + halving events/coefficient (Tier‑1 token distribution + reward calc).
  • Security/incentive mechanisms: PoHW rewards + level/quality coefficients; AI standardization and human review are claimed as quality control (Tier‑1).
  • Distribution and token issuance schedule: there are allocations (PoHW/Tag-to-Pump/liquidity) and a halving rule (Tier‑1).
  • Treasury: — (not extracted).

Governance

  • Who makes decisions: the token is described as a governance token (Tier‑1 token distribution), but the process/venues are not described in the reviewed sources.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: the docs have a “Smart Contract and Audit” section, but no specific audit reports are presented (Tier‑1).
  • Bug bounty: — (not found).
  • Incidents: — (not established).
  • Threat model: centralization of task execution/verification (AI Copilot), data quality/quality assessment, smart‑contract and token risks, economic attacks on the reward mechanics.

Project status and timeline

  • Current status: the token on BSC is active; the docs/roadmap are published; the project claims a “platform launch” in 2024 Q3 (Tier‑1).
  • Key releases/milestones: AI Copilot tooling and the marketplace/protocols (roadmap 2024).
  • Roadmap: published (Tier‑1).

Ecosystem/integrations

  • Integrations: PancakeSwap liquidity (Tier‑1 token distribution); a hardware direction and DePIN in the roadmap (Tier‑1).
  • Partners: — (not verified).
  • Where it’s actually used: as a market for labeling/data tasks and a dataset marketplace (Tier‑1).

AI component of the project

  • What is real AI here? Tier‑1 describes an AI Copilot for data annotation and AI‑driven verification/standardization of results (without technical metrics/model architecture).
  • What is truly onchain? The TAG token (BEP‑20) on the BNB Smart Chain; the onchain logic of the authentication protocol/marketplace is claimed, but not disclosed at the contract level in the current Tier‑1 artifacts.
  • Why is a token needed? Payments/fees for tasks and datasets, PoHW rewards, staking and governance (Tier‑1).
  • Red flags (based on the information found): AI‑washing (no technical details of the AI Copilot/verification), onchain‑washing (the smart contract section is “coming soon”), token‑washing (it needs to be re‑checked whether TAG is mandatory in the product and what the actual fee flows are), what to double‑check: the actual dApp/interface, the protocol/marketplace smart contracts and the audit reports.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): The presence of AI is confirmed by the product description (AI Copilot) and the economics of data tasks, not by roadmap intentions.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/usdtag
  • Why sufficient / why not (one line): the intent flag is not needed, since the AI part is described as platform functionality.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the AI Copilot helps workers perform labeling/tasks and participates in the standardized verification of results (as claimed).
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/usdtag
  • Why sufficient / why not (one line): Tier‑1 describes the AI Copilot as a component of task execution.
  • Conflict note (if any): no technical details of the models/inference.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no public Tier‑1 interface/demo of the “AI Copilot” and of the task execution flow was found in the current check.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation
  • Why sufficient / why not (one line): there are descriptions, but no reproducible demo artifact.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation
  • Why sufficient / why not (one line): Tier‑1 has no quality metrics for the AI Copilot/verification.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there are product descriptions and task tokenomics, but no technical description of the AI Copilot (models/architecture/versions).
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/usdtag
  • Why sufficient / why not (one line): without technical details we set 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: TAG (BEP‑20): 0x208bf3e7da9639f1eaefa2de78c23396b0682025
  • Evidence: Tier‑1 — https://bscscan.com/token/0x208bf3e7da9639f1eaefa2de78c23396b0682025
  • Why sufficient / why not (one line): the onchain fact of the token is confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: a data authentication/marketplace protocol is claimed, but the smart contract section in the docs contains “coming soon” without contracts (Tier‑1).
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/smart-contract-and-audit/token-smart-contract
  • Why sufficient / why not (one line): without verifiable onchain logic other than the token we set 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core logic of tasks/verification can be implemented offchain; onchain criticality is not proven by Tier‑1.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation
  • Why sufficient / why not (one line): onchain criticality is not confirmed.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, TAG, on the BNB Smart Chain.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/token-distribution
  • Why sufficient / why not (one line): Tier‑1 records the total supply and the purpose of the token.
  • 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): TAG is used for publishing tasks, buying/renting datasets and paying fees/subscriptions.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/usdtag
  • Why sufficient / why not (one line): Tier‑1 lists the token’s payment use cases.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): TAG is distributed as a PoHW reward for completed tasks; reward formulas and halving are described.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/token-distribution, https://tagger.gitbook.io/tagger-documentation/tokenomics/task-reward-calculation
  • Why sufficient / why not (one line): Tier‑1 describes the issuance/distribution and the reward formulas.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): in Tier‑1 the token is described as a governance token.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/token-distribution
  • Why sufficient / why not (one line): the governance wording is present in Tier‑1.
  • Conflict note (if any): the governance process is not described.

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established as a strict conclusion per Tier‑1.
  • Evidence: Tier‑1 — https://tagger.gitbook.io/tagger-documentation/tokenomics/usdtag
  • Why sufficient / why not (one line): Tier‑1 lists the utility but does not prove that “the same is possible without the token”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.tagger.pro Tier‑1: positioning as an AI data solutions platform + data authentication protocol.
Tier‑1 https://tagger.gitbook.io/tagger-documentation Tier‑1: the product description (data collection/labeling/management/trading, PoHW, AI Copilot).
Tier‑1 https://tagger.gitbook.io/tagger-documentation/tokenomics/usdtag Tier‑1: the token’s utility (task posting, staking, purchase/use of datasets, subscriptions/AI services) and fees (5%/1%).
Tier‑1 https://tagger.gitbook.io/tagger-documentation/tokenomics/token-distribution Tier‑1: total supply 405,380,800,000 and allocations (PoHW/Tag-to-Pump/liquidity) + the halving rule.
Tier‑1 https://tagger.gitbook.io/tagger-documentation/tokenomics/task-reward-calculation Tier‑1: the reward calculation formulas and the quality/level coefficients.
Tier‑1 https://tagger.gitbook.io/tagger-documentation/roadmap Tier‑1: the roadmap (2023–2025).
Tier‑1 https://bscscan.com/token/0x208bf3e7da9639f1eaefa2de78c23396b0682025 Tier‑1: the onchain fact of the TAG token on the BNB Smart Chain.
Tier‑1 — No Tier‑1 audit report / bug bounty / public demo of the AI Copilot was found (not confirmed by Tier‑1).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top