Skip to main content

Pundi AI

Pundi 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).

Pundi AI — an ecosystem for AI data (collection/labeling/marketplace) and onchain accounting/access (NFT control), plus the Pundi AIFX “omni layer” for cross‑chain execution; token: PUNDIAI (ERC‑20 + deployments on other networks).

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 platform where people/the community supply and label data for AI, and buyers get access to datasets.
  • Who it’s for: data creators/labelers, AI teams, dataset buyers, governance participants.
  • Why onchain/token: onchain is needed for transparent accounting of contributions/access (NFT) and dataset tokenization; PUNDIAI is used as the ecosystem’s utility+governance token.

How it works (very briefly)

  1. The user does: contributes/labels data or uploads a dataset to the marketplace; a buyer purchases access.
  2. The system does: records contributions/transactions on the blockchain, issues access NFTs (to the creator/buyer) and allows launching dataset tokens (DTOK).
  3. The user gets: a reward (for contributors), access to the dataset (for the buyer) and onchain artifacts of rights/access.
  4. Where the blockchain is: access NFTs and DTOK (BEP‑20) + onchain accounting of actions; cross‑chain execution is claimed via the Pundi AIFX omni layer.
  5. Token role (if any): PUNDIAI is the utility and governance token for the ecosystem components (Data Platform/Marketplace/AIFX/MM Agent).

Quick links: AI thesis fit

Project passport

Field Value
Project name Pundi AI
Also known as (aliases) PUNDIAI; Pundi AIFX; PURSE+
Logo (logo) ../assets/151_pundi-ai_logo.svg
Token symbol (ticker) PUNDIAI
Category AI/Data | Infra
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 Ethereum: 0x075F23b9CdfCE2cC0cA466F4eE6cb4bD29d83bef
Token model (token_type) utility (staking + governance)
Max supply 18,930,226 PUNDIAI (max)
Issuance max supply (per the docs)
Tokenomics (tokenomics, brief) TGE: 65% airdrop, 20% public treasury, 15% team; the token is deployed on Ethereum/BNB/Base + wrapped in Pundi AIFX.
Governance governance via $PUNDIAI (proposals) and staking/delegation (per the docs)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) data labeling + dataset market
Use‑case (use_case) decentralized AI data economy
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 3 / 2 / 3
Last verified 2026-02-11

General project overview

Pundi AI is a set of products whose goal is the “democratization of AI” via a data market and onchain accounting of contributions/access. The Tier‑1 documentation describes at least:

  • Pundi AI Data Platform: a decentralized system for contributing/labeling/exchanging AI data with rewards.
  • Pundi AI Data Marketplace: a dataset marketplace (the structure of sections/guides in the docs).
  • Tokenizing Datasets: a scheme for tokenizing datasets via access NFTs and “Dataset Tokens (DTOKs)”.
  • Pundi AIFX Omnilayer: an omnichain layer (Cosmos‑based, EVM‑compatible) for processing transactions/contracts and “presenting” services as native dApps of the target networks (with a focus on Base in 2025).

Note on networks (passport normalization): in the passport, the primary chain is specified as Ethereum (per the ERC‑20 token). The project’s materials also feature the Pundi AIFX Omnilayer (Cosmos‑based, EVM‑compatible) and mentions of additional deployments/wrappers of the token.

Altogether, this attempts to close the chain: data creation → access control/rights → (in the future) dataset trading → onchain artifacts that simplify integration into Web3 ecosystems.

Features/modules

  • Data Platform: data contribution/labeling (text/image/video) with transparent accounting and rewards.
  • Access NFTs: NFT access control and confirmation of dataset authorship (ownership access NFT) / buyer rights (buyer access NFT).
  • Dataset Tokens (DTOKs): BEP‑20 “collective/cultural” dataset tokens for visibility and community signaling (they grant no access and carry no revenue rights).
  • Omnilayer (Pundi AIFX): cross‑chain abstractions: execution on Pundi AIFX, use on the target network (claimed).
  • Governance & staking: proposals via PUNDIAI and delegation/staking (via the AIFX delegator mechanics).

Typical scenarios

  • Scenario 1 (dataset creator): uploads a dataset to the marketplace → receives an Ownership Access NFT → earns from dataset sales.
  • Scenario 2 (buyer): buys a dataset → receives a Buyer Access NFT → gets permissioned access to the data and the right to launch a DTOK via Data Pump.
  • Scenario 3 (community): launches/trades a DTOK for a dataset for the sake of visibility/cultural participation (without access/revenue rights).

Getting started (wallet/network)

  • What you need: an EVM wallet (Ethereum/BNB/Base) to interact with the token and onchain artifacts; access to the products — via the ecosystem interfaces.
  • Network/chain: Ethereum (the primary PUNDIAI ERC‑20 contract), as well as deployments on BNB Chain and Base; omni execution is claimed via Pundi AIFX.
  • Fees: network gas of the respective network + possible protocol fees (not detailed at the price level in the docs).

Architecture/tech (non‑AI)

  • Components: PUNDIAI token contracts (EVM), access NFTs/DTOK (BEP‑20) for datasets, the Pundi AIFX chain (Cosmos SDK + CometBFT; pBFT; EVM‑compat) and client applications/marketplaces.
  • Participant roles: data contributors/labelers, dataset creators, buyers, Pundi AIFX validators/delegators, governance participants.
  • Where logic runs: rights/access (NFT) and DTOK — onchain; part of the storage/exchange of datasets — offchain (marketplace), while actions/transactions are recorded onchain.
  • Dependencies: IPFS and “various blockchains” are mentioned for integrations; Base is declared as the 2025 focus for a “native experience”.

Token/economics (expanded, no forecasts)

  • PUNDIAI utility: specified in the docs as the utility+governance token for the Data Platform, Marketplace, AIFX Omni Layer and MM Agent.
  • Supply: max 18,930,226; the docs give minted/delegated values (as of Feb 2025).
  • TGE distribution: 65% airdrop, 20% public treasury, 15% team (total 3,786,055 at TGE).
  • Multi‑chain: a contract on Ethereum + deployments on BNB Chain/Base; wrapped PUNDIAI in Pundi AIFX.
  • Staking/governance: governance proposals via PUNDIAI; staking/delegation are described via the delegators/pundiscan page (Tier‑1 link in the docs).

Governance

  • Who makes decisions: governance via the PUNDIAI token (per the docs).
  • How protocol parameters change: via an onchain proposal/voting process (details — in the governance section).
  • Where decisions are discussed/made: — (no forum is explicitly specified in the current Tier‑1 set).
  • Keys/multisig: — (not confirmed).

Security and incidents

  • Audits: — (no Tier‑1 audit reports found).
  • Bug bounty: — (no Tier‑1 bug bounty found).
  • Incidents: — (no Tier‑1 postmortems/incidents found).
  • Threat model: risks of offchain storage/access to datasets, risks of rights/attribution and data substitution, risks of admin keys of the contracts/marketplace (not disclosed).

Project status and timeline

  • Current status: active (public website/docs + token on Ethereum).
  • Key releases/milestones: — (no Tier‑1 list of releases/milestones recorded).
  • Roadmap: see links_* → Roadmap.

Ecosystem/integrations

  • Integrations: Ethereum/BNB/Base deployments and a wrapped token in Pundi AIFX (per the docs); IPFS is mentioned as a dependency.
  • Partners: — (no Tier‑1 confirmed list of partners found).
  • Where it’s actually used: as an AI data platform/marketplace (per the description in the docs).

AI component of the project

  • What is real AI here? The project does not “do ML inference” by itself, but builds infrastructure for AI data: collection/labeling/sale of datasets for training models.
  • What is truly onchain? Accounting of contributions/access via NFTs, “DTOK” tokenization, and cross‑chain execution via the Pundi AIFX Omni layer (claimed).
  • Why is a token needed? PUNDIAI is the ecosystem’s governance/utility token; it is also used in delegation/staking (per the docs).
  • Red flags (based on the information found): AI‑washing — low/medium risk (AI here is a “data economy”); what to double‑check: what exactly the “MM Agent” does and whether there are real demos/metrics of agentic AI (if claimed).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): — (there is AI_1: work with AI data and labeling is described).
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi
  • Why sufficient / why not (one line): AI_0 applies only if AI_1..AI_4 = 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The platform is intended for contributing/labeling/exchanging AI data (for training models); “agentic AI agents” are mentioned as a future module.
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/pundi-aidata ; https://pundi.gitbook.io/pundi
  • Why sufficient / why not (one line): Tier‑1 describes AI data/labeling as the core of the product.
  • Conflict note (if any): The actual operation of “agentic AI agents” is not confirmed (AI_2=0).

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Tier‑1 contains no reproducible demo of labeling/AI agent quality; there is a description of modules and processes.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Descriptions without a demonstration of results/metrics.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Quantitative quality metrics (accuracy/quality) are not given in the docs reviewed.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): There is no technical description of AI models/versions (the focus is the data economy).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The documentation describes the data platform and the onchain mechanics, not an AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (PUNDIAI ERC‑20)
  • Addresses/identifiers: PUNDIAI 0x075F23b9CdfCE2cC0cA466F4eE6cb4bD29d83bef
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/token-economy-of-pundi-x-pundi-ai-and-pundi-aifx ; https://etherscan.io/address/0x075F23b9CdfCE2cC0cA466F4eE6cb4bD29d83bef
  • Why sufficient / why not (one line): The contract is specified in the official documentation and confirmed by the explorer.
  • Conflict note (if any): There are deployments on BNB/Base and a wrapped version in Pundi AIFX (see the token overview).

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

  • OC_2 (decision): 1
  • What useful logic is onchain: access NFTs (authorship/access) and DTOK (BEP‑20) for datasets; onchain accounting of contributions/transactions in the data platform.
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/tokenizing-datasets-on-pundi-ai ; https://pundi.gitbook.io/pundi/pundi-aidata
  • Why sufficient / why not (one line): The onchain logic of access control/tokenization is described, not reducible to “just the project token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the transparent/tamper‑proof accounting of contributions and the transferable access/authorship control (NFT), which is part of the product design, disappear.
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/pundi-aidata ; https://pundi.gitbook.io/pundi/tokenizing-datasets-on-pundi-ai
  • Why sufficient / why not (one line): These pages directly tie the system to onchain accounting and NFT access.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The ecosystem has a token, PUNDIAI (utility+governance).
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/token-economy-of-pundi-x-pundi-ai-and-pundi-aifx
  • Why sufficient / why not (one line): The token overview directly specifies the token’s role.
  • 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): A mandatory “payment for services in PUNDIAI” is not confirmed in the Tier‑1 reviewed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The documents confirm utility/governance, but do not describe “pay in PUNDIAI” pricing.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Staking/delegation using PUNDIAI is mentioned (via delegators/the chain).
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/governance ; https://pundi.gitbook.io/pundi/pundi-aifx/delegators
  • Why sufficient / why not (one line): The governance page points to PUNDIAI staking via delegators.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Governance proposals are made using $PUNDIAI.
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/governance
  • Why sufficient / why not (one line): A direct statement on the governance page.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The token is used for governance and staking in the ecosystem; replacing it requires a redesign.
  • Evidence: Tier‑1 — https://pundi.gitbook.io/pundi/governance
  • Why sufficient / why not (one line): Governance properties usually require a “native” token, not a subscription.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://pundi.gitbook.io/pundi Ecosystem overview (Data Platform/Marketplace/AIFX/PURSE+, etc.).
Tier‑1 https://pundi.gitbook.io/pundi/pundi-aidata Description of the Data Platform (contribution/labeling/exchange of AI data, onchain accounting).
Tier‑1 https://pundi.gitbook.io/pundi/tokenizing-datasets-on-pundi-ai Dataset tokenization model: access NFTs + DTOK.
Tier‑1 https://pundi.gitbook.io/pundi/pundi-aifx Pundi AIFX Omnilayer: an omni chain for processing txs/contracts, pBFT+EVM‑compat.
Tier‑1 https://pundi.gitbook.io/pundi/token-economy-of-pundi-x-pundi-ai-and-pundi-aifx PUNDIAI token overview: roles, supply, contracts on different networks.
Tier‑1 https://pundi.gitbook.io/pundi/governance Governance using PUNDIAI and a link to staking/delegation.
Tier‑1 https://github.com/PundiAI/fx-core Pundi AIFX as a Cosmos SDK chain (README).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top