Skip to main content

Holoworld AI

Holoworld AI (HOLO) — 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).

Holoworld AI — an AI/Agents | SocialFi project: a consumer platform for creating and launching AI agents/characters (no‑code), with the products Ava Studio (agentic video production), Agent Market and an API. Token: HOLO (BEP‑20 on BNB Smart Chain; the Tier‑1 documentation also claims “verifiable on Solana blockchain” as part of the agent ownership model).

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 where AI agents/characters (personas, knowledge, voice/avatar) are created without code and used in products such as Ava Studio and Agent Market.
  • Who it’s for: content creators, communities/brands and developers (there is a Studio API).
  • Why onchain/token: HOLO is described in Tier‑1 as the base asset of the ecosystem (launches/liquidity/governance) and as the “network currency” for the Open MCP network; the onchain layer is claimed as part of the agent ownership/verification model.
  • What you can actually touch (Tier‑1): the Create AI guide (creating an agent) and Ava Studio — Getting Started (the first video), as well as the Studio API (endpoints and auth).

How it works (very briefly)

  1. The user does: creates an AI agent (card/persona/knowledge/voice/avatar) via the interface (no‑code) or prepares an agent for API use.
  2. The system does: uses the agent’s parameters (persona, knowledge base, voice/body) for dialogues and for content generation (for example, video rendering in Ava Studio).
  3. The user gets: an agent they can interact with, and the generation results (video/content), and for developers — the ability to launch render jobs via the API.
  4. Where the blockchain is: Tier‑1 describes that agents are “verifiable on the Solana blockchain” (an ownership/composability model); the HOLO token is represented onchain (the BSC contract is listed in the project card) (Tier‑1).
  5. Token role: HOLO is the base asset for launches/liquidity/governance and for staking/participation/incentives; it is also listed as the “network currency” for the Open MCP network (Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Holoworld AI
Also known as (aliases) Holoworld; Ava Studio; Agent Market
Logo (logo) ../assets/73_holoworld-ai_logo.svg
Token symbol (ticker) HOLO
Category AI/Agents | SocialFi
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 0x1a5D7E4c3A7F940B240b7357a4bFED30D17f9497
Token model (token_type) utility (payments + staking + governance)
Max supply 2,048,000,000
Issuance capped
Tokenomics (tokenomics, brief) total supply 2.048B; there is a distribution by allocations + vesting/lockup; initial circulating ~16.96% (~347M).
Governance DAO
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent creation + agentic video production
Use‑case (use_case) agent hub + agentic video studio
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

Holoworld AI describes the product as a platform that allows “creating intelligent virtual beings (AI agents)” without code and using them in various scenarios: dialogues, “agentic video production”, marketplace mechanics and API integrations.

The Tier‑1 documentation emphasizes the product interfaces (Create AI / Agent Market / Ava Studio) and integrations (Studio API). In the whitepaper, the product is additionally described as a “Web3 Native Consumer AI Hub” with economic layers: HoloLaunch (distribution/launches) and the Open MCP network economy (infrastructure and context for agents), which are tied to the $HOLO token.

Features/modules

  • Create AI / Agent creation: no‑code creation of an agent: persona/voice/knowledge base, visibility, testing in a playground (Tier‑1).
  • Agent Market: creating and configuring agents (card, personality, knowledge) (Tier‑1).
  • Ava Studio: agentic video production (script, scenes, characters, narration, sound, etc.) + “Getting Started” (Tier‑1).
  • Studio API: creating render jobs and checking their status (/api/studio/render, auth via an API key) (Tier‑1).

Typical scenarios

  • Scenario 1 (creator): creates an AI character (persona/knowledge/voice/avatar) → publishes it or keeps it private → gets an agent for dialogues/content (Tier‑1).
  • Scenario 2 (video content): in Ava Studio, sets a prompt/remixes a template → generates a video and exports the result (Tier‑1).
  • Scenario 3 (developer): obtains an API key → sends a render request (Studio API) → gets the status and result of the job (Tier‑1).

Getting started (wallet/network)

  • What you need: a Holoworld account; for the Studio API — an API key and an Agent ID (Tier‑1).
  • Network/chain: for the HOLO token, the card lists the BSC contract (Tier‑1 onchain link); the documentation also claims “verifiable on Solana blockchain” for agents (Tier‑1).
  • Fees: credits are used for Studio/rendering (described in Ava Studio Getting Started and the Studio API) (Tier‑1).

Architecture/tech (non‑AI)

  • Components (product): Create AI / Agent Market / Ava Studio; Studio API (Tier‑1).
  • Participant roles (per the whitepaper): users/creators; MCP host providers; delegators/stakers; governance (Tier‑1).
  • Where logic runs: AI generation/rendering — offchain services (Studio/API); “verification/ownership” of agents is claimed via a blockchain layer (Solana) (Tier‑1). The HOLO token is onchain (the BSC contract in the project card).
  • Dependencies: the app.holoworld.com web application, API keys, external models/render pipeline (Tier‑1 API docs + product guides).

Token/economics (expanded, no forecasts)

  • Token utility: in Tier‑1, $HOLO is described as the “base asset” and “base currency” for Holoworld (launches/liquidity/governance; MCP network currency) (Tier‑1).
  • Staking/participation: Tier‑1 lists “staking & participation” (staking, rewards, access to launches via Hololaunch) (Tier‑1).
  • Governance: Tier‑1 lists “foundation governance” and holder participation (propose/vote) (Tier‑1).
  • Issuance: total supply = 2,048,000,000 (Tier‑1 tokenomics).
  • Distribution/vesting: Tier‑1 provides the distribution by categories and schedules (cliff/linear; liquidity provisioning, etc.), as well as initial circulating ~16.96% (~347M) (Tier‑1).
  • Who pays fees: the Studio product uses credits (Tier‑1); separate $HOLO token flows are described as currency/staking/incentives and for the MCP network (Tier‑1).

Governance

  • Who makes decisions: governance is claimed in Tier‑1 as a function of $HOLO (“propose and vote… protocol evolution”) (Tier‑1).
  • How protocol parameters change: via governance processes (the details and governance contracts are not established per Tier‑1) (Tier‑1).
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: centralization risks of the product part (offchain rendering/credits/API keys); token economy/vesting risks; a separate check of the AI part is also required where the descriptions remain too high-level (whitepaper) without onchain addresses/metrics.

Project status and timeline

  • Current status: active (there are product guides and API docs, updated in 2024–2025 according to the docs pages) (Tier‑1).
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: the Studio API (app.holoworld.com/api/studio/...), Holoworld product interfaces (Tier‑1).
  • Partners: —.
  • Where it’s actually used: the Create AI / Agent Market / Ava Studio guides + the Studio API — as reproducible entrypoints (Tier‑1).

AI component of the project

  • What is real AI here? AI agents/characters + agentic video production (Ava Studio) and generation/rendering via the API (Tier‑1).
  • What is truly onchain? the HOLO token is onchain (the BSC contract in the project card); Tier‑1 also claims that agents are “verifiable on the Solana blockchain” (Tier‑1).
  • Why is a token needed? $HOLO is described in Tier‑1 as the base currency of the ecosystem (Hololaunch/MCP) and as a staking/participation and governance token (Tier‑1).
  • Red flags (based on the information found): the onchain part for “agents verifiable” is not disclosed with addresses/contracts per Tier‑1; the AI part is confirmed by the product documentation, but no quality metrics/benchmarks were found in Tier‑1.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity high 3
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 a current part of the product (AI agents / Ava Studio), not as a “future intent”.
  • Evidence: Tier‑1 — https://docs.holoworld.com/
  • Why sufficient / why not (one line): the intent flag is not needed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform allows creating AI agents/characters by setting a persona/knowledge base/voice/avatar, and using them for interactions and content generation.
  • Evidence: Tier‑1 — https://docs.holoworld.com/ , https://docs.holoworld.com/product-guide/create-ai
  • Why sufficient / why not (one line): Tier‑1 describes a specific AI workflow (creating an agent and its “brain”/knowledge).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there are step‑by‑step guides on creating an agent and on creating the first video in Ava Studio, as well as the Studio API specification.
  • Evidence: Tier‑1 — https://docs.holoworld.com/product-guide/create-ai , https://docs.holoworld.com/holoworld/ava-studio/getting-started , https://docs.holoworld.com/api-guide/studio-api
  • Why sufficient / why not (one line): these are reproducible product entrypoints/instructions.
  • 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.holoworld.com/
  • Why sufficient / why not (one line): no benchmarks/quality metrics for the models/agents/rendering were found in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the product components (Ava Studio/Agent Market) and the developer API (auth + endpoints) are described; the whitepaper has high‑level architectural blocks (HoloLaunch/MCP network).
  • Evidence: Tier‑1 — https://docs.holoworld.com/api-guide/studio-api , https://rolling-filters.s3.us-east-1.amazonaws.com/Holoworld+Whitepaper.pdf
  • Why sufficient / why not (one line): sufficient for a high‑level technical description and integration interfaces.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain.
  • Addresses/identifiers: HOLO (BEP‑20): 0x1a5D7E4c3A7F940B240b7357a4bFED30D17f9497.
  • Evidence: Tier‑1 — https://bscscan.com/address/0x1a5D7E4c3A7F940B240b7357a4bFED30D17f9497
  • Why sufficient / why not (one line): the onchain fact of the token and contract in the explorer (including the max supply parameters and the source code).
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: per Tier‑1, onchain facts were found for the token, but no addresses/contracts were found for the Agent Market/HoloLaunch/MCP economy.
  • Evidence: Tier‑1 — https://docs.holoworld.com/ , https://rolling-filters.s3.us-east-1.amazonaws.com/Holoworld+Whitepaper.pdf
  • Why sufficient / why not (one line): there are statements about a Web3 layer, but without addresses/contracts for useful logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core value of the product (creation/rendering/video/API) can also work as a regular Web2 service; the blockchain part is claimed for ownership/verification, but its criticality is not proven without contract details.
  • Evidence: Tier‑1 — https://docs.holoworld.com/ , https://docs.holoworld.com/api-guide/studio-api
  • Why sufficient / why not (one line): Tier‑1 confirms the product Web workflow, but does not prove that it breaks down without onchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, $HOLO.
  • Evidence: Tier‑1 — https://docs.holoworld.com/holoworld/usdholo
  • Why sufficient / why not (one line): Tier‑1 describes $HOLO as the native token.
  • 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): $HOLO is described as the “base currency” and “network currency” in the Holoworld ecosystem (Agentic dApp store / Open MCP network).
  • Evidence: Tier‑1 — https://docs.holoworld.com/holoworld/usdholo , https://docs.holoworld.com/holoworld/usdholo/token-utilities
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the currency/medium of exchange role.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): $HOLO is used for staking/participation and rewards (including access to the Hololaunch launch mechanics).
  • Evidence: Tier‑1 — https://docs.holoworld.com/holoworld/usdholo/token-utilities
  • Why sufficient / why not (one line): Tier‑1 directly lists staking/rewards and participation via staking.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): $HOLO holders participate in governance: propose/vote on programs/partnerships/protocol evolution.
  • Evidence: Tier‑1 — https://docs.holoworld.com/holoworld/usdholo/token-utilities
  • Why sufficient / why not (one line): listed in Tier‑1 as a function of the token.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): in Tier‑1, $HOLO is described as the base asset for launches/liquidity/governance and the currency of the MCP network; replacement with a stablecoin/subscription is not described.
  • Evidence: Tier‑1 — https://docs.holoworld.com/holoworld/usdholo
  • Why sufficient / why not (one line): the token’s role is claimed as a fundamental part of the economic design.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.holoworld.com/ that Holoworld allows creating AI agents without code; “verifiable on the Solana blockchain” is claimed.
Tier‑1 https://docs.holoworld.com/product-guide/create-ai a step‑by‑step guide to creating an AI agent (persona/knowledge/voice/avatar) — a demo/guide for AI_2.
Tier‑1 https://docs.holoworld.com/holoworld/ava-studio/getting-started the step‑by‑step guide “Create Your First Video” in Ava Studio — a demo/guide for AI_2.
Tier‑1 https://docs.holoworld.com/api-guide/studio-api Studio API: API key, render/status endpoints, formats/parameters — dev access to the product.
Tier‑1 https://docs.holoworld.com/holoworld/usdholo the role of $HOLO as the base currency/asset for launches/liquidity/governance.
Tier‑1 https://docs.holoworld.com/holoworld/usdholo/tokenomics total supply 2.048B + distribution/vesting + initial circulating ~16.96%.
Tier‑1 https://docs.holoworld.com/holoworld/usdholo/token-utilities $HOLO utilities: staking/participation, foundation governance (propose/vote), creator rewards, network currency.
Tier‑1 https://rolling-filters.s3.us-east-1.amazonaws.com/Holoworld+Whitepaper.pdf high‑level architecture/economics: HoloLaunch + MCP Network economy; $HOLO as the foundation of the token utility.
Tier‑1 https://bscscan.com/address/0x1a5D7E4c3A7F940B240b7357a4bFED30D17f9497 the onchain fact of the HOLO token (BEP‑20, max supply 2.048B; BNB Smart Chain).

No comments to display

Back to top