Skip to main content

DrPepe.ai

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

DrPepe.ai — an AI/Agents | Infra project on the Solana network, token (symbol: BRYAN).

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 project/agent that, per the Tier‑1 documentation, is positioned as an AI agent on the topic of longevity/anti‑aging, relying on a research base.
  • Who it’s for: users who need a conversational agent and materials/links on the topic, as described in the project’s Tier‑1 documentation.
  • Why onchain/token: per the Tier‑1 docs, the $BRYAN token is positioned as a community token and a “key” to the closed beta; the onchain part is recorded via the SPL token.

How it works (very briefly)

  1. The user does: interacts with the agent/reads the project’s documentation and materials.
  2. The system does: per the Tier‑1 docs, the agent uses a research base and provides answers/recommendations within the described functions.
  3. The user gets: answers/information from the agent (per the project’s description).
  4. Where the blockchain is: the $BRYAN token exists as an SPL token on the Solana network.
  5. Token role: per the Tier‑1 docs — an early access mechanism (closed beta) and a community token; the role of “payment for the service” is not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name DrPepe.ai
Also known as (aliases) $BRYAN, DrPepe.ai Agent
Logo (logo) ../assets/617_drpepe-ai_logo.png
Token symbol (ticker) BRYAN
Category AI/Agents | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active
Token (standard) SPL
Token contract BrYANThKaAbjZZH5XWLrw26NzMbfUNmBwbZiMe4Fj5Mk
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Per the Tier‑1 docs: $BRYAN is a community token and a “key” to the closed beta; the details of “payment for the service” are not established.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) conversational agent for longevity (RAG/knowledge base)
Use‑case (use_case) Q&A/recommendations on longevity (info)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

DrPepe.ai, per the Tier‑1 GitBook, describes an AI agent that uses a base of materials on longevity/anti‑aging and provides answers in a conversational format. The documentation also mentions the components used (Eliza framework, “Gaia decentralized infrastructure”) and has sections on the ecosystem tokens.

Features/modules

  • Agent documentation: description of the purpose and architecture (Tier‑1 GitBook).
  • Knowledge base (claimed): a “peer‑reviewed database” as the source for the agent’s answers (the details of the base’s composition are a separate question).
  • Tokens/access: the Tokenomics section and a mention of closed beta access via tokens.

Typical scenarios

  • Scenario 1: a user reads the docs → understands the claimed functions and architecture of the agent.
  • Scenario 2: a user interacts with the agent (if available) → receives answers/information on the topic.

Getting started (wallet/network)

  • What you need: access to the website/documentation; for operations with the token — a Solana wallet.
  • Network/chain: Solana.
  • Fees: Solana network fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: the website/documentation (offchain) + the SPL token (onchain).
  • Where logic runs: the agent/inference — offchain (per the docs); token operations — onchain (Solana).
  • Dependencies: Solana infrastructure for the token; other dependencies — per the documentation (Eliza framework / Gaia are mentioned as components).

Token/economics (expanded, no forecasts)

  • $BRYAN token role: per the Tier‑1 docs — a community token and an access mechanism for the closed beta.
  • Payment for the service (not established): no Tier‑1 artifact was found that makes $BRYAN a mandatory payment token of the product.

Governance

  • Who makes decisions: — (no description of governance mechanics was found per Tier‑1 sources).

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.

Project status and timeline

  • Current status: the website and documentation are available; the token exists on the Solana network (see links_*).
  • Roadmap: https://docs.drpepe.ai/welcome/roadmap

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.

AI component of the project

  • What is real AI here? Per the Tier‑1 docs — a conversational AI agent; components (Eliza framework) and implementation sketches are described.
  • What is truly onchain? The $BRYAN SPL token on Solana; other onchain logic is not established per Tier‑1 sources.
  • Why is a token needed? Per the Tier‑1 docs, $BRYAN is used as early access to the closed beta; the necessity of the token for the operation of the agent as a service is not established.
  • Red flags (based on the information found): mixing “AI agent” with marketing promises; absence of public quality metrics; onchain is limited to the token.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium 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 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): The Tier‑1 docs describe a working agent and architecture, not just “intentions”.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/
  • Why sufficient / why not (one line): AI_0 is needed for “intent without a product”; here there is a description of functions/architecture.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Per the Tier‑1 docs, the AI agent uses a research base on longevity/anti‑aging and provides answers/recommendations.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/ ; https://docs.drpepe.ai/welcome/introduction
  • Why sufficient / why not (one line): The Tier‑1 documentation describes the purpose of the agent and its sources (base/docs).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A public demo of the agent/interaction interface is not established in Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.drpepe.ai ; https://docs.drpepe.ai/
  • Why sufficient / why not (one line): 1 requires a verifiable demo artifact; a description was found, but not a demo.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.drpepe.ai/
  • Why sufficient / why not (one line): No reproducible set of model/agent quality metrics was found per Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The Tier‑1 docs describe components/architectural elements (Eliza framework, Gaia) and contain draft code/integration sketches.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/ ; https://docs.drpepe.ai/ai-longevity-agents/elizaos-feature ; https://docs.drpepe.ai/ai-longevity-agents/gaia-decentralized-ai
  • Why sufficient / why not (one line): There is a tech context and implementation sketches, which are sufficient for AI_4.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: token mint BrYANThKaAbjZZH5XWLrw26NzMbfUNmBwbZiMe4Fj5Mk
  • Evidence: Tier‑1 — https://solscan.io/token/BrYANThKaAbjZZH5XWLrw26NzMbfUNmBwbZiMe4Fj5Mk
  • Why sufficient / why not (one line): The Explorer provides onchain observability of the token.
  • 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, only the token was found).
  • Evidence: Tier‑1 — https://docs.drpepe.ai/
  • Why sufficient / why not (one line): In the Tier‑1 docs, no addresses/description of onchain protocol logic were found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that the product breaks down without onchain; onchain manifests through the token.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/
  • Why sufficient / why not (one line): 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 (one line): The project has a token, $BRYAN (Solana SPL).
  • Evidence: Tier‑1 — https://solscan.io/token/BrYANThKaAbjZZH5XWLrw26NzMbfUNmBwbZiMe4Fj5Mk ; https://docs.drpepe.ai/tokenomics/bryan
  • Why sufficient / why not (one line): The Explorer + Tier‑1 docs confirm the token and its context.
  • 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): No Tier‑1 source was found confirming payment for the service with the $BRYAN token as a mandatory mechanism.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/tokenomics/bryan
  • Why sufficient / why not (one line): The Tier‑1 docs describe $BRYAN as a community/access token, not a payment mechanism.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Staking/penalties for $BRYAN are not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/tokenomics/bryan
  • Why sufficient / why not (one line): There is no description of incentive mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance mechanics via $BRYAN are not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/tokenomics/bryan
  • Why sufficient / why not (one line): There is no governance specification.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): No Tier‑1 argument about the (ir)replaceability of $BRYAN was found.
  • Evidence: Tier‑1 — https://docs.drpepe.ai/tokenomics/bryan
  • Why sufficient / why not (one line): Design justification is required; not established.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.drpepe.ai/ Tier‑1 description of the project and the claimed architecture/purpose of the AI agent.
Tier‑1 https://docs.drpepe.ai/ai-longevity-agents/elizaos-feature Tech context: Eliza framework and draft code (Tier‑1).
Tier‑1 https://docs.drpepe.ai/ai-longevity-agents/gaia-decentralized-ai Tech context: mention of Gaia and draft code (Tier‑1).
Tier‑1 https://docs.drpepe.ai/tokenomics/bryan Context of the $BRYAN token (community token + beta access per the Tier‑1 docs).
Tier‑1 https://solscan.io/token/BrYANThKaAbjZZH5XWLrw26NzMbfUNmBwbZiMe4Fj5Mk Onchain fact: the $BRYAN SPL token (mint address).