Skip to main content

Tell a Tale

Tell a Tale — 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).

Tell a Tale — a product that is described on the website as an AI agent for short video & film production; there is a web application (demo). The onchain part is confirmed by the existence of the TAT token on BNB Smart Chain.

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 web application for generating/creating stories/scripts (claimed as an “AI agent” for videos/films).
  • Who it’s for: content creators/authors and users who want to generate stories.
  • What you can actually touch (Tier‑1): https://app.tellatale.ai/
  • Why onchain/token: the TAT token on BNB Smart Chain is confirmed; the role of the token in the product is not established per Tier‑1.

How it works (very briefly)

  1. The user does: opens the web application and chooses a mode/story template.
  2. The system does: provides script templates and a creation interface (per the app).
  3. The user gets: the created story/content (details of how the AI part works are not disclosed by Tier‑1).
  4. Where the blockchain is: onchain — the TAT token on BNB Smart Chain.
  5. Token role: not established per Tier‑1 sources (a description of the utility/rules of token usage in the product is needed).

Quick links: AI thesis fit

Project passport

Field Value
Project name Tell a Tale
Also known as (aliases) TellATale, TAT
Logo (logo) ../assets/510_tell-a-tale_logo.svg
Token symbol (ticker) TAT
Category AI/Agents
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0x996D1b997203a024E205069a304161ba618d1c61
Token model (token_type) —
Max supply 1,000,000,000 TAT
Issuance fixed
Tokenomics (tokenomics, brief) Max total supply 1B (per the Explorer).
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent for story/script generation
Use‑case (use_case) story generation for short video/film
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 2
Last verified 2026-02-11

General project overview

Tell a Tale is a web product that is positioned on the website as an “AI agent for short video & film production”. The public application shows creation modes and a gallery/ranking, but no Tier‑1 technical documentation (model architecture, quality metrics) is listed in this card.

Features/modules

  • Create: the interface for creating/launching scripts (app).
  • Gallery: viewing the created content (app).
  • Ranking: ranking/popular items (app).

Typical scenarios

  • Scenario 1: the user chooses a story template → launches creation → receives a draft/result.
  • Scenario 2: the user browses the gallery/ranking → studies examples.

Getting started (wallet/network)

  • What you need: a browser and access to the web application (see links_* App / Demo).
  • Network/chain: BNB Smart Chain — for the TAT token (if interaction with the token is required).
  • Fees: BSC transaction fees for operations with the token; the role of the token in the application is not established.

Architecture/tech (non‑AI)

  • Components: web client/application + a BEP‑20 token on BNB Smart Chain.
  • Participant roles: application users; token holders (role not established).
  • Where logic runs: offchain — content generation/creation; onchain — the token.
  • Dependencies: BNB Smart Chain (EVM) for the token.

Token/economics (expanded, no forecasts)

  • Token role in the product: not established per Tier‑1 (the website has a “Buy $TAT” button, but a description of the utility is absent).
  • Max supply (Tier‑1): 1,000,000,000 TAT (BscScan).

Governance

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

Security and incidents

  • Audits: a CyberScope report is claimed (see links_* Audit report(s)).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of the token smart contract (admin functions/pause/fees — to be checked in the report and the contract), as well as risks of the closed offchain part of the AI application.

Project status and timeline

  • Current status: active (there is a website, an app and a token).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: the web application and public pages (links_*).

AI component of the project

  • What is real AI here? there is Tier‑1 positioning as an “AI agent” and an accessible web application; but there is no Tier‑1 tech description of the models and quality metrics.
  • What is truly onchain? the TAT token as a BEP‑20 on BNB Smart Chain.
  • Why is a token needed? not established per Tier‑1 (docs/a description of the utility are needed).
  • Red flags (based on the information found): AI‑washing risk (no tech docs/metrics), token‑washing (the role of the token is not described) — what to double‑check: docs/whitepaper/utility, the link between the token and the app functionality.

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 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is claimed as a working component (there is an app), so this is not only an “intent”.
  • Evidence: Tier‑1 — https://www.tellatale.ai/ ; https://app.tellatale.ai/
  • Why sufficient / why not (one line): AI_0 is used 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): The product is described as an AI agent for short video & film production (generation/creation of stories/scripts).
  • Evidence: Tier‑1 — https://www.tellatale.ai/
  • Why sufficient / why not (one line): There is a Tier‑1 description of the function of the AI part (at the level of “what it does”).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a web application with Create/Gallery/Ranking modes and script templates.
  • Evidence: Tier‑1 — https://app.tellatale.ai/
  • Why sufficient / why not (one line): The demo is publicly available and reproducible.
  • 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): Quality metrics/benchmarks were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): Technical documentation of the AI models/versions was not found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There are no docs/whitepaper with the model architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: 0x996D1b997203a024E205069a304161ba618d1c61 (BEP‑20)
  • Evidence: Tier‑1 — https://bscscan.com/token/0x996D1b997203a024E205069a304161ba618d1c61
  • Why sufficient / why not (one line): The explorer confirms the token/network/max supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established (other than the existence of the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 source about onchain logic beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the application works offchain; the criticality of the blockchain for the core function is not proven.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 “without the blockchain it 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, TAT.
  • Evidence: Tier‑1 — https://bscscan.com/token/0x996D1b997203a024E205069a304161ba618d1c61
  • Why sufficient / why not (one line): The Explorer confirms 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 (one line): Payment for services with the token is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The website has no description of the token utility for payments/access.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Token‑based incentives/collateral/penalties are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of incentives.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance.
  • 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 — —
  • Why sufficient / why not (one line): There is no Tier‑1 comparison of alternatives.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.tellatale.ai/ Tier‑1 positioning: “AI agent for short video & film production”, the token CA.
Tier‑1 https://app.tellatale.ai/ Demo: a public web application (Create/Gallery/Ranking, script templates).
Tier‑1 https://bscscan.com/token/0x996D1b997203a024E205069a304161ba618d1c61 The TAT token on BSC: contract/network/Max total supply 1B.
Tier‑2 https://www.cyberscope.io/audits/coin-tell-a-tale Automated audit/risk assessment of the contract (for reference).
Tier‑2 https://coinmarketcap.com/currencies/tell-a-tale/ Token profile/metadata (for reference).
Tier‑2 https://www.coingecko.com/en/coins/tell-a-tale Token profile/metadata (for reference).