Skip to main content

PEAR AI

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

PEAR AI — an AI/Agents project on the Ethereum network, token (symbol: PEAR).

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 set of “AI agents” for Web3 tasks (claimed: for traders, developers, marketing, design, etc.).
  • Who it’s for: Web3 users/teams who need automation and AI tools for the described scenarios.
  • Why onchain/token: onchain records the issuance/transfers of the token; the specific utility of the token in the product is not established per Tier‑1 sources.

How it works (very briefly)

  1. The user does: selects an agent/scenario and submits a request (the product surface/interface are not verified per Tier‑1 sources).
  2. The system does: generates a response/content/automation for the described scenario (model/architecture details are not disclosed in the available Tier‑1 sources).
  3. The user gets: a result in the form of text/content/suggestions/automated steps.
  4. Where the blockchain is: only the token (ERC‑20) is confirmed onchain in this card.
  5. Token role: not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name PEAR AI
Also known as (aliases) Pear AI, PEAR
Logo (logo) ../assets/827_pear-ai_logo.svg
Token symbol (ticker) PEAR
Category AI/Agents
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 0xfc40b76cdd4e62ef0c8273fdbdbc458253776015
Token model (token_type) —
Max supply 100,000,000 PEAR
Issuance fixed
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents for Web3 workflows
Use‑case (use_case) assistants for Web3
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

The project website describes PEAR AI as a set of specialized “AI agents” for different roles (claimed: traders, developers, designers, marketing, etc.). No tech description of the models/architecture was found per the available Tier‑1 sources, and the product “surfaces” (application/demo) are not verified. The onchain part in this card is confirmed as an ERC‑20 token.

Features/modules

  • AI agents (claimed): a set of agents for different scenarios (description on the website).
  • Task automation (claimed): generation/assistance with development/content tasks, etc.

Typical scenarios

  • Scenario 1: a user selects an agent for a task → receives a generated result (claimed).

Getting started (wallet/network)

  • What you need: — (not established per Tier‑1 sources).
  • Network/chain: Ethereum (token).
  • Fees: Ethereum fees apply to onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: website/interface (not verified in greater depth) + offchain AI processing (details not disclosed) + ERC‑20 token contract.
  • Participant roles: users (request a result), token holders (if the token is involved; not established).
  • Where logic runs: AI — offchain; the token — onchain (Ethereum).
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources.
  • Issuance: max total supply 100,000,000 PEAR (Tier‑1, explorer).

Governance

  • Who makes decisions: — (not established).

Security and incidents

  • Audits: not found per Tier‑1 sources.
  • Bug bounty: not found per Tier‑1 sources.
  • Incidents: not found per Tier‑1 sources.

Project status and timeline

  • Current status: active (there is a website and a token).
  • Roadmap: not found per Tier‑1 sources.

Ecosystem/integrations

  • Integrations: not verified per Tier‑1 sources.

AI component of the project

  • What is real AI here? A set of AI agents for different scenarios is claimed (Tier‑1, website).
  • What is truly onchain? The PEAR ERC‑20 token on Ethereum (Tier‑1, explorer).
  • Why is a token needed? Not established per Tier‑1 sources.
  • Red flags (based on the information found): there are no Tier‑1 AI quality metrics (AI_3=0) and no tech description of the AI part (AI_4=0) per the available Tier‑1 sources; the token utility is not confirmed by Tier‑1.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI intent is not singled out separately, because there is a direct Tier‑1 description of “AI agents” (AI_1).
  • Evidence: Tier‑1 — https://thepearai.com/
  • Why sufficient / why not (one line): we use AI_1 as the basis instead of intent.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI agents for Web3 tasks (different roles/scenarios) are claimed.
  • Evidence: Tier‑1 — https://thepearai.com/
  • Why sufficient / why not (one line): The Tier‑1 website describes AI agents and their scenarios.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): demos/examples of operation are not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 link to an app/demo in links_*.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: no Tier‑1 quality metrics/benchmarks were found.
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no published metrics per the SSOT definition.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the tech description/architecture/versions of the AI part were not found per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no technical docs/repository in links_*.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xfc40b76cdd4e62ef0c8273fdbdbc458253776015
  • Evidence: Tier‑1 — https://etherscan.io/token/0xfc40b76cdd4e62ef0c8273fdbdbc458253776015
  • Why sufficient / why not (one line): the onchain fact of the token contract 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: not established per Tier‑1 sources (other than the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description of useful onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): “criticality” is not proven.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, PEAR (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xfc40b76cdd4e62ef0c8273fdbdbc458253776015
  • Why sufficient / why not (one line): the onchain fact of the token is established per the explorer.
  • 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): it is not established that the token is used to pay for the service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No Tier‑1 description of the token utility was found per the available sources.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): the mechanics of incentives/collateral/penalties are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 justification.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://thepearai.com/ Tier‑1: “AI agents” and usage scenarios are described (at least as claims).
Tier‑1 https://etherscan.io/token/0xfc40b76cdd4e62ef0c8273fdbdbc458253776015 Onchain fact: the PEAR AI (PEAR) ERC‑20 token, max total supply 100,000,000 PEAR.
Tier‑1 — No Tier‑1 source for claim “why is a token needed (utility/role in the product)” was found per the available sources.

No comments to display

Back to top