Strawberry AI
Strawberry 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).
Strawberry AI — an AI/Other / Consumer project (a product suite around the “Agents Engine” for querying/acting on data and market/security insight), token (symbol: BERRY).
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 product suite whose key component is the Agents Engine, which “helps query and act on data” (including trends and smart contract risk analysis), as described in the docs.
- Who it’s for: users who need market insights and/or text‑based “agent interfaces” for analyzing tokens/contracts (per the docs).
- Why onchain/token: the BERRY token is claimed as the protocol currency for access to products/API/SDK and as a governance instrument; there is an onchain contract on Ethereum (and addresses on other networks are listed).
How it works (very briefly)
- The user does: submits queries and uses the features of the Strawberry AI products (Agents Engine and others).
- The system does: produces analytics/insights (including on trends and contract risks) and provides access to the product capabilities.
- The user gets: answers/signals/insights (as described in the docs).
- Where the blockchain is: the BERRY token and the claimed ecosystem (including BerryChain, where BERRY is used as gas — per the token utility).
- Token role: access/payments for services, governance, LP pairs, burn (per the token docs).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Strawberry AI |
| Also known as (aliases) | StrawberryAI, BERRY |
| Logo (logo) | ../assets/201_strawberry-ai_logo.svg |
| Token symbol (ticker) | BERRY |
| Category | AI/Other | Consumer |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | 2024-08-13 (fair launch; per the tokenomics) |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0xCb76314C2540199f4B844D4ebbC7998C604880cA (Ethereum) |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | 100,000,000 BERRY (capped; per the tokenomics) |
| Issuance | fixed (capped supply; per the tokenomics) |
| Tokenomics (tokenomics, brief) | fair launch (no pre‑mine / no early sale); allocation: 75% LP, 10% team, 5% CEX, 5% partners, 5% community; no taxes |
| Governance | governance token (per the token utility) |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | agents engine for market/security insights |
| Use‑case (use_case) | agentic market analytics |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 1 / 1 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://usestrawberry.ai |
| Docs | https://usestrawberry.gitbook.io/strawberryai |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | https://usestrawberry.gitbook.io/strawberryai/other/roadmap |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xCb76314C2540199f4B844D4ebbC7998C604880cA |
| X | https://twitter.com/StrawberryAI_5 |
| Discord | — |
| Telegram | https://t.me/strawberryai_X |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/strawberry-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/strawberry-ai/ |
General project overview
In the Tier‑1 docs, Strawberry AI describes the “Agents Engine” as the base component of the product suite: it is supposed to allow users to “query and act on data” and includes the claimed capabilities:
- Predicting Emerging Trends: analysis of real‑time sentiment/volume/search data for “rising tokens” and narrative trends.
- Smart Contract Audits (via the request interface): “What are the risks in $TOKENNAME?” → security analysis of the contract.
- Advanced Market Metrics: monitoring of whale movements, suspicious activity and market metrics.
At the same time, the Agents Engine page says “Description coming soon”, so the implementation details (architecture/model/metrics) in Tier‑1 are still limited.
Features/modules
- Agents Engine: the central layer for data/queries/analytics.
- Related products: 0xLuigi, BerrySwap, BerryChain (in the docs structure).
Typical scenarios
- Scenario 1: a user asks a question about a token/contract → receives a “security analysis” (per the feature description).
- Scenario 2: a user looks for trends/narratives → receives hints about rising tokens (per the feature description).
Getting started (wallet/network)
- What you need: access to the Strawberry AI products; for the onchain part — a wallet of the chosen network.
- Network/chain: Ethereum (the BERRY contract); Base and Solana addresses are also listed in the docs.
- Fees: network gas for onchain operations.
Architecture/tech (non‑AI)
- Components: the BERRY token, the “Agents Engine” product layer and the adjacent products from the docs.
- Where logic runs: analytics/insights — probably offchain; onchain — the token and potential chain components (BerryChain is claimed as a product).
Token/economics (expanded, no forecasts)
Per the Tier‑1 tokenomics:
- total supply capped at 100,000,000 (fair launch 2024‑08‑13, no pre‑mine, no early token sale)
- allocation: 75% LP, 10% team, 5% CEX, 5% partners, 5% community incentives
- “There are NO taxes”
Per the Tier‑1 token utility:
- BERRY — the primary protocol currency for product features, including access to Strawberry products, API, SDK.
- governance tool (holders direct protocol/development/outreach decisions)
- token burn, “used as gas on the BerryChain”, used in LP pairs.
Governance
- Who makes decisions: BERRY holders (governance is claimed in the token utility).
Security and incidents
- Audits/bug bounty: no public Tier‑1 links are recorded.
Project status and timeline
- Current status: the docs are available; the token exists on Ethereum and on the claimed networks.
AI component of the project
- What is real AI here? The docs claim an “Agents Engine” with trend prediction and contract risk analysis capabilities, but without metrics/architecture.
- What is truly onchain? The BERRY token (a contract on Ethereum; Base and Solana addresses are also listed).
- Why is a token needed? Per the docs: the protocol currency (access to products/API/SDK), governance, gas on BerryChain, burn.
- Red flags (based on the information found): “AI” is described at the level of product features without a demo, metrics or a technical description; BerryChain is mentioned, but the chain’s onchain artifacts are not confirmed by addresses in this card.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | low | 1 |
| Token necessity | low | 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): AI is described as an operating layer of the product (Agents Engine), not only as a roadmap intent.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine
- Why sufficient / why not (one line): specific functions of the engine are listed.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): the Agents Engine claims trend prediction and smart contract risk analysis via an “ask” interface.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine
- Why sufficient / why not (one line): functions associated with AI/analytics are listed (although the description of the implementation is limited).
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): no Tier‑1 web demo/reproducible tutorial to “touch” the Agents Engine is recorded.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine
- Why sufficient / why not (one line): the page says “Description coming soon”; there is no link to 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://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine
- Why sufficient / why not (one line): there are no metrics/benchmarks.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a technical description of the AI architecture is absent.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine
- Why sufficient / why not (one line): features are listed, but without architecture/versions.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum (Base and Solana are also listed)
- Addresses/identifiers: Ethereum BERRY
0xCb76314C2540199f4B844D4ebbC7998C604880cA - Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/other/contracts ; https://etherscan.io/token/0xCb76314C2540199f4B844D4ebbC7998C604880cA
- Why sufficient / why not (one line): the contracts page provides the addresses; the explorer allows verification.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: BerryChain and “BERRY as gas” are mentioned, but BerryChain addresses/contracts were not recorded in this card.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/tokenomics/token-utility
- Why sufficient / why not (one line): without addresses/artifacts of onchain logic, we set 0.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the analytical functions (Agents Engine) can work offchain; onchain criticality is not proven.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine
- Why sufficient / why not (one line): onchain is used as a token/access layer, but “breaks down without the blockchain” is not shown.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, BERRY.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/tokenomics/usdberry
- Why sufficient / why not (one line): the tokenomics describes the token and supply.
- 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): BERRY is required for payment services and for access to the API/market insights once the suite “becomes live”.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/tokenomics/usdberry ; https://usestrawberry.gitbook.io/strawberryai/tokenomics/token-utility
- Why sufficient / why not (one line): the tokenomics directly states “required for payment services … access to our API and market insights”.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): protocol collateral/slashing/security incentives are not described.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/tokenomics/token-utility
- Why sufficient / why not (one line): burn/gas/LP/access are described, but not slashing mechanics.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): BERRY acts as a governance tool for community‑driven decisions.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/tokenomics/token-utility
- Why sufficient / why not (one line): governance is described explicitly.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): no strict proof of the irreplaceability of the native token was found.
- Evidence: Tier‑1 — https://usestrawberry.gitbook.io/strawberryai/tokenomics/token-utility
- Why sufficient / why not (one line): the token’s role is described, but without a “no other way” argument.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://usestrawberry.gitbook.io/strawberryai/product-suite/agents-engine | claimed functions of the Agents Engine (trend prediction, contract risk analysis, market metrics) |
| Tier‑1 | https://usestrawberry.gitbook.io/strawberryai/tokenomics/usdberry | capped supply 100M, fair launch, allocation, “no taxes” |
| Tier‑1 | https://usestrawberry.gitbook.io/strawberryai/tokenomics/token-utility | token utility: protocol currency, governance, burn, “gas on BerryChain”, access to API/SDK/products |
| Tier‑1 | https://usestrawberry.gitbook.io/strawberryai/other/contracts | contract addresses (Ethereum/Solana/Base) |
| Tier‑1 | https://etherscan.io/token/0xCb76314C2540199f4B844D4ebbC7998C604880cA | onchain page of the BERRY token (Ethereum) |
| Tier‑2 | https://www.coingecko.com/en/coins/strawberry-ai | reference profile |
No comments to display
No comments to display