Skip to main content

MyShell

MyShell — 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).

MyShell — an AI/Agents | Consumer project on Ethereum (also BNB Chain), token (symbol: SHELL).

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/marketplace for creating, publishing and monetizing AI agents (AI applications) and for launching agent tokens via the Launchpad.
  • Who it’s for: AI agent creators, users (AI tools/entertainment), patrons/investors (support and tokenization of agents).
  • Why onchain/token: payments and rewards within the ecosystem and trading/launching agent tokens on the Launchpad.
  • What you can actually touch (Tier‑1): see links_* → App / Demo (Workshop/agents) and links_* → Launchpad (launching and actions with agent tokens).

How it works (very briefly)

  1. The user does: picks an agent and uses it, or creates/configures an agent (Classic / Pro Config / ShellAgent).
  2. The system does: runs LLM/multimodal “widgets” (models, API integrations), links the steps into a workflow/state machine, publishes the agent on MyShell.
  3. The user gets: the agent’s output (chat/voice/images/utilities) or a ready‑made agent that others can use.
  4. Where the blockchain is: onchain — the $SHELL token (Ethereum/BNB Chain) and Launchpad operations (tokenization of agents/trading of agent tokens, automatic launch on a DEX).
  5. Token role (if any): $SHELL — payments/rewards/participation in the Launchpad; there is also an offchain currency, Shell Coin, for early incentives (Reward Center).

Quick links: AI thesis fit

Project passport

Field Value
Project name MyShell
Also known as (aliases) MyShell AI; ShellAgent; Shell Launchpad
Logo (logo) ../assets/114_myshell_logo.svg
Token symbol (ticker) SHELL
Category AI/Agents | Consumer
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum); PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xf2c88757f8d03634671208935974B60a2a28Bdb3
Token model (token_type) utility (payments + rewards + launchpad)
Max supply cap 1,000,000,000 SHELL (per the docs); onchain max total supply: ~491.816M (ETH) / ~508.184M (BNB)
Issuance fixed (capped; 5‑year unlock)
Tokenomics (tokenomics, brief) Community Incentive 30%, Private Sale 29%, Team 12%; TGE unlock 27% in total (per the docs)
Governance company / offchain (onchain governance is not claimed in the docs)
Admins/keys —
Audit yes (Hashlock: penetration test 2024‑06; smart contract audit 2024‑07)
Bug bounty —
Team (team) MyShell Limited (BVI)
Funding (investors/funding) backed by (website): Binance Labs, Delphi Ventures, OKX, Maven11, Nascent, Bankless Ventures, Dragonfly, etc.
AI component (ai_component) marketplace + agentic framework (LLM widgets)
Use‑case (use_case) build/share/monetize AI agents
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 1 / 3
Last verified 2026-02-11

General project overview

MyShell is positioned as a “decentralized AI consumer layer”: it is a platform for AI agents, where:

  • users find and use ready‑made AI agents/AI tools (entertainment, productivity, learning, etc.),
  • creators publish and monetize their agents,
  • some economic operations (payments/rewards/Launchpad) are tied to the $SHELL token and onchain mechanics.

Per the docs, creators can build agents in several ways (Classic / Pro Config / ShellAgent) and use a library of “widgets” (models and external APIs), and then publish the agent on MyShell.

Features/modules

  • AI Agent Store / Workshop: a catalog of agents and tools where users interact with AI applications.
  • Creator tooling: Classic Mode, Pro Config Mode (widgets + logic), ShellAgent Mode (a no‑code multi‑agent framework).
  • Widgets/integrations: LLM, TTS, image/video and other modules (models/external APIs) for building agents.
  • Shell Launchpad: launching/tokenizing AI agents as agent tokens, trading agent tokens via $SHELL/$BNB.

Typical scenarios

  • Scenario 1 (user): opens an agent in app.myshell.ai → receives a response/content (chat/voice/images/utility).
  • Scenario 2 (creator): builds an agent in Classic/Pro Config/ShellAgent → publishes it in the Store → receives income/rewards when the agent is used.
  • Scenario 3 (Launchpad): a creator launches an agent token → users trade the agent token via $SHELL/$BNB, and when the bonding curve limit is reached the token automatically goes to a DEX (per the Launchpad description).

Getting started (wallet/network)

  • What you need: an account/access to app.myshell.ai; for the onchain part (interacting with the token/Launchpad operations) — an EVM wallet.
  • Network/chain: $SHELL exists as a token on Ethereum and BNB Chain; for the Launchpad, trading via $SHELL or $BNB is also mentioned.
  • Fees: network fees of the selected network (gas); the Launchpad claims a 1% transaction fee (in the Launchpad docs).

Architecture/tech (non‑AI)

  • Components: the web client (app), offchain infrastructure (execution of agents/widgets), the $SHELL token smart contracts and the agent token contracts/addresses (Launchpad).
  • Participant roles: users; agent creators; patrons/investors; platform operators.
  • Where logic runs: AI logic mostly offchain; onchain — settlements/accounting related to $SHELL and the Launchpad (agent token contracts and trading).
  • Dependencies: EVM networks (Ethereum/BNB), DEX infrastructure (agent tokens going to a DEX), external AI models/APIs as widgets.

Token/economics (expanded, no forecasts)

  • Token utility: $SHELL — payments for services/features, creator support (tipping), participation in ecosystem mechanics and trading/buying agent tokens (Launchpad).
  • Protocol necessity drivers: the token is embedded in the platform economy (payments/rewards) and is claimed as the Launchpad currency for trading agent tokens.
  • Who pays fees: users/Launchpad participants pay network fees; additionally, the Launchpad claims a 1% transaction fee.
  • Where fees go: — (not publicly detailed in the docs).
  • Issuance/burn: cap 1,000,000,000 (per the docs); no automatic supply‑adjustment mechanisms are claimed in the MiCA whitepaper.
  • Security/incentive mechanisms: incentives/rewards for contributions to the ecosystem are described in the tokenomics (create/collect/events/model contributors, etc.); the website mentions “$SHELL staked”, but no Tier‑1 description of the staking mechanics was found in the docs.
  • Distribution and token issuance schedule: Private Sale 29% (1y cliff + 3y linear), Team 12% (1y cliff + 4y linear), Community Incentive 30% (7% TGE unlock + 5y linear), etc.; 27% unlock at TGE in total.
  • Treasury: Ecosystem & Treasury 8.5% (2.5% TGE unlock + 5‑year linear vesting); control details — not found.

Governance

  • Who makes decisions: MyShell Limited / the team (the docs contain no explicit onchain DAO for $SHELL).
  • How protocol parameters change: via platform updates; the MiCA whitepaper notes that protocol rules may evolve through “community consensus upgrades”, but the specific process/artifacts are not described.
  • Where decisions are discussed/made: GitHub/social media/docs (no formal governance process found).
  • Keys/multisig: —.

Security and incidents

  • Audits: the MiCA whitepaper claims a penetration test (2024‑06) and a smart contract audit (2024‑07) with the status “Secure” (Hashlock is listed as the source of the results).
  • Bug bounty: — (not found).
  • Incidents: — (not found).
  • Threat model: typical risks: smart contract/bridging vulnerabilities, centralized parts of the platform (offchain execution), supply/vesting and concentration risks, risks of third‑party AI APIs and data.

Project status and timeline

  • Current status: the product is active; the $SHELL token is traded as ERC‑20/BEP‑20.
  • Key releases/milestones: a changelog is available in the docs (Pro Config Mode).
  • Roadmap: the 2025 roadmap includes development of the agent builder, agentic RL, a launching mechanism for the Launchpad and “AgentOS” (see the link in links_*).

Ecosystem/integrations

  • Integrations: EVM wallets (for $SHELL), DEXs (Uniswap/PancakeSwap — mentioned in the “How to Obtain $SHELL” docs), TradingView for Launchpad charts (in the docs).
  • Partners: investment/ecosystem (website): Binance Labs, Delphi Ventures, OKX, Maven11, Nascent, Bankless Ventures, Dragonfly, etc.
  • Where it’s actually used: the MyShell Workshop/Store (public agents) and the Launchpad (agent tokens) are available via app.myshell.ai and launch.myshell.ai.

AI component of the project

  • What is real AI here? AI agents (LLM/multimodal “widgets”), tooling for building agents (Classic/Pro Config/ShellAgent) and a set of open/published AI technologies (ShellAgent, OpenVoice, MeloTTS, JetMoE, AIlice — per the docs/repositories).
  • What is truly onchain? the $SHELL token as ERC‑20/BEP‑20 and the Launchpad mechanics of tokenizing/trading agent tokens (agent token contracts, going to a DEX when the bonding curve is reached).
  • Why is a token needed? payments/rewards within the platform and the currency for the Launchpad (buying/trading agent tokens); at the same time, the docs acknowledge an offchain currency, Shell Coin, for early incentives.
  • Red flags (based on the information found): possible onchain‑washing (the main AI logic is offchain), possible token‑washing (some functions could work with stablecoins/a subscription; the token’s “irreplaceability” is not proven), a conflict/fragmentation of supply between the cap (1B) and the onchain max supply on individual networks; check: the public addresses/contracts of the Launchpad and the “$SHELL staked” mechanics.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity low/medium 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): there is a roadmap with AI milestones, but AI is already confirmed (see AI_1/AI_2/AI_4), so AI_0 as “intent only” does not apply
  • Evidence: Tier‑1 — https://docs.myshell.ai/tokenomics/roadmap
  • Why sufficient / why not (one line): by the operational definition, AI_0=1 is set only when AI_1..AI_4 = 0
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): a platform for creating/publishing AI agents and AI applications (models + external APIs + workflow)
  • Evidence: Tier‑1 — https://docs.myshell.ai/about/what-is-myshell, https://docs.myshell.ai/about/quickstart
  • Why sufficient / why not (one line): the docs describe the roles (creators/consumers) and the functions of AI agents/tools
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a public Workshop/Store for using agents and the Launchpad interface
  • Evidence: Tier‑1 — https://app.myshell.ai/, https://launch.myshell.ai/
  • Why sufficient / why not (one line): there is “something to touch” (public product interfaces)
  • 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): no reproducible quality metrics/benchmarks were found in the Tier‑1 sources
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the key AI components/framework (ShellAgent) and a set of technologies/models (OpenVoice, etc.) are described
  • Evidence: Tier‑1 — https://docs.myshell.ai/technology, https://github.com/myshell-ai
  • Why sufficient / why not (one line): there is a technical description and public repositories with artifacts
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum mainnet; BNB Chain mainnet
  • Addresses/identifiers: $SHELL 0xf2c88757f8d03634671208935974B60a2a28Bdb3 (ETH/BSC)
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf2c88757f8d03634671208935974B60a2a28Bdb3, https://bscscan.com/token/0xf2c88757f8d03634671208935974B60a2a28Bdb3, https://docs.myshell.ai/tokenomics/shell-basics
  • Why sufficient / why not (one line): there are onchain contracts and they are confirmed in the official docs
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the Launchpad tokenizes AI agents (agent tokens), uses a bonding curve and takes the token to a DEX; there are contract addresses for agent tokens
  • Evidence: Tier‑1 — https://docs.myshell.ai/launchpad, https://docs.myshell.ai/launchpad/trade-agent-tokens, https://docs.myshell.ai/launchpad/how-to-launch-a-token
  • Why sufficient / why not (one line): an onchain mechanism is described (not just “there is a token”, but tokenization/trading)
  • Conflict note (if any): no public list/registry of Launchpad contracts was found in the docs (addresses are visible in the UI for specific agent tokens)

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the basic marketplace/agent execution does not require a blockchain; onchain matters for the Launchpad/token economy, but “criticality for the whole product” is not proven
  • Evidence: Tier‑1 — https://docs.myshell.ai/about/what-is-myshell, https://docs.myshell.ai/launchpad
  • Why sufficient / why not (one line): Tier‑1 does not state that the platform “breaks” without the blockchain (rather, it adds a layer of economics/tokenization)
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, $SHELL
  • Evidence: Tier‑1 — https://docs.myshell.ai/tokenomics/shell-basics, https://etherscan.io/token/0xf2c88757f8d03634671208935974B60a2a28Bdb3
  • Why sufficient / why not (one line): the token is described in the docs and exists onchain
  • 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): $SHELL is used as the currency for payments/access to the platform’s services and features
  • Evidence: Tier‑1 — https://docs.myshell.ai/tokenomics/shell-basics, https://2975681513-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDtmZwLatyyBFLUK6P6Pj%2Fuploads%2FIz7YYjfnZYpEHr2Q5lU3%2FMiCA%20Whitepaper%20-%20MyShell%20-%20SHELL%20-%20062025.pdf?alt=media&token=8f2ee366-d9ce-46f1-acf0-30df417fb2fc
  • Why sufficient / why not (one line): Tier‑1 describes the token as the “native currency” and a means of access/payments
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): participants are rewarded with the token for contributions to the ecosystem (create/collect/events/model contributors, etc.)
  • Evidence: Tier‑1 — https://docs.myshell.ai/tokenomics/how-to-obtain-shell, https://docs.myshell.ai/tokenomics/shell-basics
  • Why sufficient / why not (one line): the docs directly describe receiving $SHELL as rewards for contributions/activities
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): onchain governance via the token is not described in the docs
  • Evidence: Tier‑1 — https://2975681513-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDtmZwLatyyBFLUK6P6Pj%2Fuploads%2FIz7YYjfnZYpEHr2Q5lU3%2FMiCA%20Whitepaper%20-%20MyShell%20-%20SHELL%20-%20062025.pdf?alt=media&token=8f2ee366-d9ce-46f1-acf0-30df417fb2fc
  • Why sufficient / why not (one line): the MiCA whitepaper states that the token does not grant corporate voting rights; no explicit governance mechanism is provided
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): a significant part of the utility looks replaceable (stablecoins/a subscription) without loss of the basic AI function
  • Evidence: Tier‑1 — https://docs.myshell.ai/about/what-is-myshell, https://docs.myshell.ai/tokenomics/shell-basics
  • Why sufficient / why not (one line): Tier‑1 describes the token as the “ecosystem currency” but does not prove that the product is impossible without its own token
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.myshell.ai/about/what-is-myshell what MyShell is, the roles (consumers/creators), the claimed “decentralized AI consumer layer” model
Tier‑1 https://docs.myshell.ai/about/quickstart how to use/create agents (an overview of the modes and the token economy)
Tier‑1 https://docs.myshell.ai/technology a description of the key AI technologies/framework (ShellAgent/OpenVoice/MeloTTS/JetMoE/AIlice)
Tier‑1 https://app.myshell.ai/ the public product interface (Workshop/Store) — a demo of existing agents
Tier‑1 https://docs.myshell.ai/tokenomics/shell-basics cap 1B, distribution/vesting, the $SHELL contract, the distinction between $SHELL vs Shell Coin
Tier‑1 https://docs.myshell.ai/tokenomics/how-to-obtain-shell the mechanics of receiving $SHELL for contributions/activities, the list of CEXs/DEXs for the token
Tier‑1 https://docs.myshell.ai/launchpad the purpose of the Launchpad and trading of agent tokens via $SHELL/$BNB
Tier‑1 https://docs.myshell.ai/launchpad/how-to-launch-a-token the process of tokenizing an agent and the automatic move of the agent token to a DEX when the limit is reached
Tier‑1 https://docs.myshell.ai/launchpad/trade-agent-tokens the existence of contract addresses for agent tokens and trading via the Launchpad
Tier‑1 https://etherscan.io/token/0xf2c88757f8d03634671208935974B60a2a28Bdb3 the onchain $SHELL contract on Ethereum and the supply parameters per the explorer
Tier‑1 https://bscscan.com/token/0xf2c88757f8d03634671208935974B60a2a28Bdb3 the onchain $SHELL contract on BNB Chain and the supply parameters per the explorer
Tier‑1 https://2975681513-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDtmZwLatyyBFLUK6P6Pj%2Fuploads%2FIz7YYjfnZYpEHr2Q5lU3%2FMiCA%20Whitepaper%20-%20MyShell%20-%20SHELL%20-%20062025.pdf?alt=media&token=8f2ee366-d9ce-46f1-acf0-30df417fb2fc MiCA whitepaper: the token’s role, network(s), risks, information about the company MyShell Limited
Tier‑1 https://myshell.ai/ product presentation + confirmation of “backed by” (the list of investors on the website)
Tier‑1 https://hashlock.com/audits/myshell the claimed audits/pentest (2024‑06/2024‑07) and the final status “Secure”
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top