Skip to main content

WELL3 / WELLAIOS

WELL3 / WELLAIOS — 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).

WELL3 describes a wellness platform integrated with a web3 community and early access/mission mechanics. Separately, WELLAIOS is promoted as an “AI Operating System”/ecosystem of AI agents with a public beta link. The WELL token is confirmed as an ERC‑20 on the Ethereum network.

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 wellness platform with tasks/missions and a related AI part (AIOS/agents) for users and the community.
  • Who it’s for: users of wellness activities and community members; potentially — users/creators of AI agents in WELLAIOS.
  • Why onchain/token: the ERC‑20 token WELL is confirmed; a Tier‑1 description of mandatory onchain logic of the product (other than the existence of the token) is not established.
  • What you can actually touch (Tier‑1): the WELLAIOS beta link https://app.wellaios.ai/ (given on the WELLAIOS website).

How it works (very briefly)

  1. The user does: completes activities/missions and interacts with the product (early access / missions).
  2. The system does: awards EXP/levels and ties this to the claim/token mechanics (per the website description).
  3. The user gets: progress/access/the ability to claim the token (per the description).
  4. Where the blockchain is: the WELL token exists on the Ethereum network; individual interactions may be offchain (X login/missions) and onchain (claim/token).
  5. Token role (if any): No Tier‑1 source for claim “the token is necessary for payment for/access to the AIOS/service” was found.

Quick links: AI thesis fit

Project passport

Field Value
Project name WELL3 / WELLAIOS
Also known as (aliases) Well3; WELL AIOS; YogaPetz (community)
Logo (logo) ../assets/397_well3_logo.png
Token symbol (ticker) WELL
Category AI/Agents | Consumer
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (website/documentation available)
Token (standard) ERC-20
Token contract 0x63696fc66795b51d02c1590b536484a41fbddf9a
Token model (token_type) utility (rewards)
Max supply 42,000,000,000
Issuance —
Tokenomics (tokenomics, brief) max supply is given in the explorer; the details of utility/distribution require Tier‑1 confirmation
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AIOS + AI agents
Use‑case (use_case) wellness missions + AI agents
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 1
Last verified 2026-02-11

General project overview

Per the Tier‑1 documentation, Well3 is described as a wellness platform integrated with a web3 community and farming/mission mechanics (EXP/levels). A separate WELLAIOS website describes a “Decentralized AIOS” — an ecosystem for creating/deploying/managing AI agents “without code”.

The WELL token is confirmed as an ERC‑20 on Ethereum. Tier‑1 rules that would formally prove the necessity of the token for access to/payment for the AIOS part are not established.

Features/modules

  • Well3 wellness missions: early access, activities/missions, EXP and levels (per the description on the website/docs).
  • Claim/token: a claim/purchase page for WELL (web interfaces).
  • WELLAIOS: creating/deploying/managing AI agents without code (per the website description).
  • Integrations: the WELLAIOS website lists integrations (without a full list).

Typical scenarios

  • Scenario 1: a user participates in missions → gets EXP/a level → uses the claim mechanics (per the description).
  • Scenario 2: a user opens the WELLAIOS beta → interacts with AI agents/configuration.
  • Scenario 3: the community invites friends via referral → participates in the leaderboard (per the description).

Getting started (wallet/network)

  • What you need: an account/access (well3.com mentions X login), and for the token — an EVM wallet.
  • Network/chain: Ethereum (the WELL token).
  • Fees: Ethereum fees for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: websites/documentation, the ERC‑20 token; the WELLAIOS beta application (link on the website).
  • Where logic runs: the AI part (agents/AIOS) looks like an offchain service; onchain — the token and operations around it.

Token/economics (expanded, no forecasts)

  • Onchain fact: the WELL token is an ERC‑20; max total supply is given in the explorer.
  • Token utility: a formal Tier‑1 description of the token utility in the AIOS/product is not established.

Governance

  • Who makes decisions: — (not established per Tier‑1 sources).

Security and incidents

  • Audits / bug bounty: — (not established per Tier‑1 sources).
  • Incidents: — (not established per Tier‑1 sources).

Project status and timeline

  • Current status: the website/documentation are available; the WELLAIOS website has a “Try Beta Now” link.
  • Roadmap: — (not found per Tier‑1 sources).

Ecosystem/integrations

  • Integrations: the WELLAIOS website lists integrations (Twitch/Google/Telegram and others, judging by the icons; the details require separate verification).

AI component of the project

  • What is real AI here? AIOS/agents as claimed functionality (creating/deploying/managing AI agents without code).
  • What is truly onchain? the WELL token on Ethereum.
  • Why is a token needed? a Tier‑1 source on the necessity of the token specifically for the AIOS mechanics is not confirmed.
  • Red flags (based on the information found): mixing of wellness missions, web logins and AIOS with the token without a transparent Tier‑1 “token ↔ mandatory function” link.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim: AI is described as a current component of the product (AIOS/agents), not only as a plan.
  • Evidence: Tier‑1 — https://wellaios.ai/
  • Why sufficient / why not: the intent flag applies when there are only plans without a described product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim: AIOS makes it possible to create/deploy/manage AI agents, including “no‑code” scenarios (per the website description).
  • Evidence: Tier‑1 — https://wellaios.ai/
  • Why sufficient / why not: the Tier‑1 description records the purpose of the AI part and its key functions.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim: the WELLAIOS website has a link to the beta application (“Try Beta Now”).
  • Evidence: Tier‑1 — https://wellaios.ai/ (link to https://app.wellaios.ai/)
  • Why sufficient / why not: there is a Tier‑1 pointer to an accessible interface.
  • 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: the Tier‑1 sources do not record reproducible quality metrics of the AI component.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim: no Tier‑1 tech description of the architecture/versions of the models/agents was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the public pages describe the product at the level of concept and functions, without engineering details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x63696fc66795b51d02c1590b536484a41fbddf9a
  • Evidence: Tier‑1 — https://etherscan.io/token/0x63696fc66795b51d02c1590b536484a41fbddf9a
  • Why sufficient / why not: the explorer confirms the existence of the token and the contract address.
  • 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 (other than the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the existence of the token does not prove onchain logic of the product.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that a key property of the AIOS/product breaks down without the blockchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim: the project has a token, WELL (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x63696fc66795b51d02c1590b536484a41fbddf9a
  • Why sufficient / why not: the explorer shows the name/symbol and the parameters of the token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim: No Tier‑1 source for claim “payment for the service/AIOS with the token” was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there are no Tier‑1 rules for paying for services with the token.
  • Conflict note (if any): —

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

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

TK_3 — governance (1/0)

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

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim: a conclusion about the replaceability of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without a confirmed utility of the token, no strict conclusion can be drawn.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.well3.com/ description of Well3 as a wellness platform integrated with a web3 community
Tier‑1 https://wellaios.ai/ description of the AIOS/agents and a link to the beta application
Tier‑1 https://app.wellaios.ai/ public beta page/interface of WELLAIOS (demo)
Tier‑1 https://etherscan.io/token/0x63696fc66795b51d02c1590b536484a41fbddf9a the WELL token (ERC‑20): address and max total supply
Tier‑1 — No Tier‑1 source for claim “the WELL token is mandatory for payment for/access to the AIOS/service” was found.
Tier‑2 https://www.coingecko.com/en/coins/well3 reference profile of the token/project
Tier‑2 https://coinmarketcap.com/currencies/well3/ reference profile of the token/project

No comments to display

Back to top