Skip to main content

Cora (MetaBotAI)

Cora (MetaBotAI) — 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).

Cora (MetaBotAI) — an AI/Agents project on the Base network, token (symbol: CORA).

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 agent (within MetaBotAI) that helps with chart analysis and checking/analyzing token contracts (as claimed in the Tier‑1 documentation).
  • Who it’s for: traders and users of MetaBotAI products.
  • Why onchain/token: the existence of an ERC‑20 token on Base is confirmed; the necessity of the token as a mandatory mechanism of the product is not established per Tier‑1.

How it works (very briefly)

  1. The user does: addresses Cora in the context of MetaBotAI (in the application/ecosystem).
  2. The system does: produces an analysis (per the description: charts, feedback on smart contracts, token contract analytics).
  3. The user gets: hints/analysis results for reference (without guarantees).
  4. Where the blockchain is: the project token exists on the Base network; other onchain logic is not established per Tier‑1.
  5. Token role (if any): Tier‑1 describes the supply and the buy&burn mechanic, but no Tier‑1 justification of “why the token is necessary for the product to work” was found.

Quick links: AI thesis fit

Project passport

Field Value
Project name Cora (MetaBotAI)
Also known as (aliases) CoraAI, CoraBot
Logo (logo) —
Token symbol (ticker) CORA
Category AI/Agents | DeFi
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) L2 (Optimistic Rollup, Base on Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x81cB4FDD3Edc6f5470b636D7e5914C3173110ca5
Token model (token_type) —
Max supply 1 000 000 000
Issuance burn (buy&burn claimed)
Tokenomics (tokenomics, brief) Claimed: initial LP burned; buy&burn funded by a portion of the fee until 500M burned.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent for chart + contract analysis
Use‑case (use_case) trader assistant + on-chain analytics
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 1
Last verified 2026-02-11

General project overview

Cora is described as an AI agent in the MetaBotAI ecosystem that is meant to help users with practical trading tasks: chart analysis, feedback on smart contracts, and token contract analytics. The verifiable onchain artifacts per Tier‑1 are an ERC‑20 token on Base; separate “protocol‑level” onchain logic is not established.

Features/modules

  • AI trading assistant: chart analysis and help with research are claimed.
  • Token contract analytics: checks/insights on contracts are claimed.
  • Communication via X: the agent has a public presence (Tier‑1).

Typical scenarios

  • Scenario 1: the user asks a question/requests an analysis → receives a response/hint from the AI agent (within MetaBotAI).
  • Scenario 2: the user requests feedback on a smart contract → receives comments/an assessment (claimed).

Getting started (wallet/network)

  • What you need: — (not found per Tier‑1; the description mentions the MetaBotAI app).
  • Network/chain: Base — for operations with the token.
  • Fees: Base fees arise for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: an offchain AI agent (in the application/ecosystem) + an onchain ERC‑20 token on Base.
  • Participant roles: users, the team/product operators.
  • Where logic runs: the AI part — offchain; onchain — the token.
  • Dependencies: Base as the L2 network; data/analytics sources are not established per Tier‑1.

Token/economics (expanded, no forecasts)

  • Token utility: the necessity of the token for access/payments/incentives is not established per Tier‑1.
  • Protocol necessity drivers: —.
  • Who pays fees: users for onchain operations with the token.
  • Where fees go: to the validators/sequencer of the Base network (per the network rules).
  • Issuance/burn: Tier‑1: buy&burn and the goal of “burn until 500M” are claimed; parameters/schedule — without a formal specification.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: the risk of relying on AI hints; risks of the token as a separate onchain asset; absence of public audits in the links_* sources.

Project status and timeline

  • Current status: active (there are public materials and a token on the Base network).
  • Key releases/milestones: —.
  • Roadmap: — (no Tier‑1 found; the row in links_* is left as —).

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1.

AI component of the project

  • What is real AI here? In the Tier‑1 documentation, Cora is described as an AI agent that helps with chart and smart contract analysis within MetaBotAI.
  • What is truly onchain? An ERC‑20 token on Base; no other onchain artifacts/contracts for the product were found in the sources.
  • Why is a token needed? Per Tier‑1, the supply and the burn mechanic are described; the utility/necessity of the token as a mandatory mechanism is not established per Tier‑1.
  • Red flags (based on the information found): absence of a Tier‑1 demo/product surface that can be reproduced; absence of specific quality metrics; tokenomics without a formal description of mechanisms and constraints.

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 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as a function/role of the agent, not as a “future plan without implementation”.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Tier‑1 describes “what Cora does”, so the intent flag is not used.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Cora helps with chart analysis, feedback on smart contracts, and token contract analytics (claimed).
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Tier‑1 contains an explicit description of the AI agent’s functions.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 “touchable” demo endpoint/application for reproduction was found.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): There is a description, but no unambiguous demo surface (app/demo link) in Tier‑1.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found in Tier‑1.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Tier‑1 has no reproducible quality metrics of the AI agent.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the model architecture/versions was not found per Tier‑1.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): There is a description of “what it does”, but no architecture/versions/technical details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: token contract 0x81cB4FDD3Edc6f5470b636D7e5914C3173110ca5
  • Evidence: Tier‑1 — https://basescan.org/token/0x81cB4FDD3Edc6f5470b636D7e5914C3173110ca5
  • Why sufficient / why not (one line): There is a verifiable onchain artifact (the token contract).
  • 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 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): OC_2 requires contracts/a description of useful onchain logic (access/accounting/rules); none was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of the criticality of the onchain component was found.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): An AI feature is described, but there is no statement “without the blockchain the product breaks down”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, CORA, on Base.
  • Evidence: Tier‑1 — https://basescan.org/token/0x81cB4FDD3Edc6f5470b636D7e5914C3173110ca5 ; https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Tier‑1 sources provide the contract address and the supply.
  • 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): Payment for the service with the token as a mandatory mechanism is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Tier‑1 has no description of a tariff/access where the token is needed for payment.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties requiring the token are not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Buy&burn is described, but this is not proof of the protocol‑level necessity of the token for incentives.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): Tier‑1 has no description of a DAO/voting with CORA.
  • 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 per Tier‑1.
  • Evidence: Tier‑1 — https://docs.metabotai.xyz/coraai-our-ai-agent
  • Why sufficient / why not (one line): A formal argument “what breaks down without the token” is needed; none was found in Tier‑1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.metabotai.xyz/coraai-our-ai-agent Description of Cora’s functions (AI agent) and basic information about the token (address, supply, buy&burn as a claim).
Tier‑1 https://basescan.org/token/0x81cB4FDD3Edc6f5470b636D7e5914C3173110ca5 Verifiable onchain artifact: an ERC‑20 token on Base (the contract).
Tier‑1 — No Tier‑1 source for claim “why the token is needed as a mandatory mechanism of the product” was found.

No comments to display

Back to top