Skip to main content

Purple AI

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

Purple AI — an AI project on the Ethereum network (ERC‑20), token (symbol: PAI).

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 AI platform for image generation and creation of “custom” AI bots for projects (per the project’s claim).
  • Who it’s for: teams/content creators and communities that need custom AI bots and visual content generation (per the project’s claim).
  • Why onchain/token: the token is used in the claimed reward/tax mechanics and “token system” for transactions and rewards (per the project’s claim).
  • What you can actually touch (Tier‑1): a Telegram bot for creating custom AI bots: https://t.me/PAICreator_Bot

How it works (very briefly)

  1. The user does: creates/configures an AI bot or uses image generation tools (per the project’s claim).
  2. The system does: generates visual content and (per the project’s claim) supports customization/training for a project.
  3. The user gets: images/a bot for use in content/community tasks.
  4. Where the blockchain is: onchain — the ERC‑20 token and related public contract data.
  5. Token role: tax/buyback/reward mechanics and participation in the ecosystem are claimed.

Quick links: AI thesis fit

Project passport

Field Value
Project name Purple AI
Also known as (aliases) PAI
Logo (logo) —
Token symbol (ticker) PAI
Category AI/Other
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 0xa0cc4428fbb652c396f28dce8868b8743742a71c
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) A tax of 4% and rewards/a buyback fund are claimed (more details — Tier‑1 on the website).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI bot customization + image generation
Use‑case (use_case) visual content generation
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Purple AI is positioned as an AI ecosystem for custom image generation and creation of AI bots “for a project”. The Tier‑1 description also claims additional tools and use cases (content/marketing/communities), but the degree of “onchain necessity” and the role of the token in the product require careful verification.

Features/modules

  • Image generation (per the project’s claim).
  • Creation of custom AI bots via a Telegram tool (per the project’s claim).
  • A set of AI tools/“Apps/Tools” pages on the project website.

Typical scenarios

  • Scenario 1: a team creates a custom AI bot for a community and uses it to generate images/responses (per the project’s claim).
  • Scenario 2: a user generates visual content for design/content tasks (per the project’s claim).

Getting started (wallet/network)

  • What you need: access to the website/Telegram bot; a wallet — if required for interacting with the token.
  • Network/chain: Ethereum (ERC‑20).
  • Fees: onchain Ethereum fees; product fees/limitations — not established (no Tier‑1 confirmation found).

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract; website; Telegram bot (per the project’s claim).
  • Participant roles: users/project teams.
  • Where logic runs: onchain — the token; AI tools/bot — not established (probably offchain, requires re‑checking).
  • Dependencies: Telegram, web interface, Ethereum RPC.

Token/economics (expanded, no forecasts)

  • Token utility: “transactions and rewards” and participation in the ecosystem are claimed (requirements/the mandatory nature of the token require clarification per Tier‑1).
  • Protocol necessity drivers: not established; where the token is mandatory and where it is not needs to be double‑checked.
  • Who pays fees: not established (no Tier‑1 confirmation found).
  • Where fees go: a tax and distribution mechanism is claimed (per the project’s claim).
  • Issuance/burn: not found (no Tier‑1 confirmation identified).
  • Security/incentive mechanisms: rewards/a buyback fund are claimed (per the project’s claim).
  • Distribution and token issuance schedule: not found (no Tier‑1 confirmation identified).
  • Treasury: not found (no Tier‑1 confirmation identified).

Governance

  • Who makes decisions: not found (no Tier‑1 confirmation identified).
  • How protocol parameters change: not found (no Tier‑1 confirmation identified).
  • Where decisions are discussed/made: not found (no Tier‑1 confirmation identified).
  • Keys/multisig: not found (no Tier‑1 confirmation identified).

Security and incidents

  • Audits: not found (no Tier‑1 confirmation identified).
  • Bug bounty: not found (no Tier‑1 confirmation identified).
  • Incidents: not found (no Tier‑1 confirmation identified).
  • Threat model: not established; for a product with AI bots, it is important to double‑check data storage/access policy and actual limitations/cost.

Project status and timeline

  • Current status: the service is available via the website/Telegram bot (Tier‑1 links).
  • Key releases/milestones: not found (no Tier‑1 confirmation identified).
  • Roadmap: the website describes phases/plans; exact task statuses require re‑checking.

Ecosystem/integrations

  • Integrations: Telegram bot (builder) and “Apps/Tools” web pages.
  • Partners: not found (no Tier‑1 confirmation identified).
  • Where it’s actually used: not established; production use requires separate verification.

AI component of the project

  • What is real AI here? Per the Tier‑1 claim, the project provides image generation tools and creation of custom AI bots (demo via the Telegram builder).
  • What is truly onchain? The ERC‑20 token and its contract are confirmed onchain.
  • Why is a token needed? Per the Tier‑1 claim, the token participates in reward/tax mechanics and in the “token system” for transactions and rewards; the mandatory nature of the token for access to the product requires re‑checking.
  • Red flags (based on the information found): absence of public metrics/benchmarks and technical AI architecture; which parts of the product run offchain and which rights/payments are actually tied to the token need to be double‑checked.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity low 1
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 project has a Tier‑1 description of working AI tools (this is more than intent).
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): AI_0 is used as “intent only”; here there is a product description and a demo entry point (builder).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The project claims image generation and creation of custom AI bots for projects.
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): The website provides a description of features (image generation + custom bots).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The Tier‑1 source gives a Telegram builder for creating AI bots.
  • Evidence: Tier‑1 — https://purplesquare.ai/ ; https://t.me/PAICreator_Bot
  • Why sufficient / why not (one line): There is an “entry point” that can be used as a demo (builder).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0 Metrics: not found (no Tier‑1 confirmation identified). Context (version/date/how measured): not found (no Tier‑1 confirmation identified).
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): There are no verifiable quantitative quality metrics/benchmarks.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0 Claim (one line): A technical description of AI architecture/versions was not found in Tier‑1 sources.
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): 1 requires technical details (architecture/versions/boundaries), which are absent in the available Tier‑1.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xa0cc4428fbb652c396f28dce8868b8743742a71c
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa0cc4428fbb652c396f28dce8868b8743742a71c ; https://purplesquare.ai/
  • Why sufficient / why not (one line): The contract address is verifiable via an onchain explorer; a link to the contract is also present on the project website.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0 What useful logic is onchain: No confirmation of onchain logic of the product (Tier‑1), other than the token, was found.
  • Evidence: Tier‑1 — https://purplesquare.ai/ ; https://etherscan.io/token/0xa0cc4428fbb652c396f28dce8868b8743742a71c
  • Why sufficient / why not (one line): 1 requires described/observable onchain logic (access/accounting/rules), which was not found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0 “Replace the blockchain” test: no proof (Tier‑1) was found that the product breaks down without the blockchain.
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): 1 requires an explicit argument for onchain criticality, which is absent.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a claimed token, PAI (ERC‑20).
  • Evidence: Tier‑1 — https://purplesquare.ai/ ; https://etherscan.io/token/0xa0cc4428fbb652c396f28dce8868b8743742a71c
  • Why sufficient / why not (one line): The project website contains mentions of $PAI and links to the contract.
  • 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): Mandatory payment with the token for access to AI features is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): 1 requires explicit “payment for the service with the token” as a mandatory access mechanism.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Rewards for holders and the mechanics of a buyback fund fed by tax/revenue are claimed (incentives).
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): The website describes taxes and allocation to rewards/buyback.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0 Claim (one line): Governance use of the token is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): 1 requires a description of the voting/governance process.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0 Claim (one line): The replaceability of the token without loss of the product’s meaning is not established (no Tier‑1 confirmation identified).
  • Evidence: Tier‑1 — https://purplesquare.ai/
  • Why sufficient / why not (one line): 1 requires an explicit design argument that the token is secondary and replaceable.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://purplesquare.ai/ Tier‑1 description of features (image generation, custom AI bots), “token system”, basic tokenomics claims (tax/buyback/rewards), and links to the demo entry point.
Tier‑1 https://t.me/PAICreator_Bot Demo entry point: a Telegram builder for creating AI bots (as “what you can touch”).
Tier‑1 https://etherscan.io/token/0xa0cc4428fbb652c396f28dce8868b8743742a71c Onchain fact of the ERC‑20 contract of the PAI token on the Ethereum network.

No comments to display

Back to top