AI9000
AI9000 — 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).
AI9000 — a token (ERC‑20) on the Avalanche network. Per Tier‑1 sources, it is linked to the Delaunch platform for creating/training/deploying AI agents (no claims about returns/price).
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 platform (Delaunch) + the linked AI9000 token on the Avalanche network.
- Who it’s for: users who create/train/deploy AI agents via the platform.
- Why onchain/token: onchain confirms the existence of the token; the necessity of the token in the platform mechanics is not established per Tier‑1 sources.
- What you can actually touch (Tier‑1): the web interface for launching/creating an agent (
Launch) on the Delaunch website.
How it works (very briefly)
- The user does: creates/configures an AI agent in the platform interface.
- The system does: allows training and deploying the agent (implementation details and data sources require separate verification).
- The user gets: a running AI agent and the infrastructure for its operation.
- Where the blockchain is: the AI9000 token and operations with it are recorded onchain (Avalanche).
- Token role: per Tier‑1, it is not established whether the token is a mandatory part of the protocol (payments/incentives/governance) or an auxiliary asset.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AI9000 |
| Also known as (aliases) | Delaunch AI9000 |
| Logo (logo) | ../assets/605_ai9000_logo.png |
| Token symbol (ticker) | AI9000 |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Avalanche |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Avalanche) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x79Ea4E536f598dCd67C76Ee3829f84AB9E72A558 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | Per Tier‑1 sources, no description of the role of the AI9000 token in the protocol (payments/incentives/governance) was found. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | Delaunch.ai |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agent creation/training/deployment platform |
| Use‑case (use_case) | AI agent creation + deployment |
| DecAI Fit — AI thesis fit | 2/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.delaunch.ai/ |
| Docs | https://docs.delaunch.ai |
| GitHub | https://github.com/delaunch-avax |
| Releases / Changelog | — |
| Whitepaper | https://delaunch.ai/whitepaper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://snowscan.xyz/token/0x79Ea4E536f598dCd67C76Ee3829f84AB9E72A558 |
| App / Demo | https://www.delaunch.ai/launch |
| X | https://twitter.com/delaunch |
| Discord | — |
| Telegram | https://t.me/KaizenDL |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/ai9000 |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ai9000/ |
General project overview
Delaunch is a platform that allows users to create, train and deploy AI agents (including without programming skills), positioned as “community‑driven infrastructure”. The AI9000 token exists on the Avalanche network; at the same time, the necessity of the token as a mandatory mechanism of the platform is not confirmed per Tier‑1 sources.
Features/modules
- Creating AI agents: configuring the agent’s parameters/goals via the interface (Tier‑1 docs).
- Training and deployment: claimed as part of the platform (Tier‑1 docs).
- Launch web interface: an entry point that can be checked hands‑on (Tier‑1).
Typical scenarios
- Scenario 1: a user creates an agent in the interface → gets a configured/running agent (as claimed in the docs).
- Scenario 2: a user reads the documentation → understands how the platform is structured and which steps are needed to create/train/deploy.
Getting started (wallet/network)
- What you need: access to the web interface; for interacting with the token — an EVM wallet.
- Network/chain: Avalanche (for the onchain part of the token).
- Fees: EVM (Avalanche) network fees for onchain operations.
Architecture/tech (non‑AI)
- Components: the platform web interface; documentation; the onchain token contract (Avalanche).
- Participant roles: platform users; token holders; participants of the Avalanche network infrastructure.
- Where logic runs: the platform’s AI logic — mostly offchain; the token and its operations — onchain.
- Dependencies: EVM RPC/indexers (for displaying onchain data), the platform’s web infrastructure.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 sources.
- Protocol necessity drivers: not established per Tier‑1 sources.
- Who pays fees: users of the Avalanche network for onchain operations.
- Where fees go: to Avalanche network validators (at the network level).
- Issuance/burn: not found per Tier‑1 sources.
- Security/incentive mechanisms: not found per Tier‑1 sources.
- Distribution and token issuance schedule: not found per Tier‑1 sources.
- Treasury: not found per Tier‑1 sources.
Governance
- Who makes decisions: not established per Tier‑1 sources.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: typical risks of platforms/wallets/contracts; specifics require a Tier‑1 security section/audits.
Project status and timeline
- Current status: active (the platform is available; the token is deployed).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: EVM wallets (Avalanche) and the platform web interface.
- Partners: —.
- Where it’s actually used: the demo surface and documentation are publicly available (see
links_*).
AI component of the project
- What is real AI here? Per Tier‑1 docs, the platform is oriented toward creating/training/deploying AI agents; there is a public demo surface (Launch).
- What is truly onchain? The AI9000 token contract and operations with it on the Avalanche network.
- Why is a token needed? Per Tier‑1 sources, no description of a mandatory role of the token in the protocol (payments/incentives/governance) was found.
- Red flags (based on the information found): absence of a Tier‑1 description of the token’s role in the mechanics; absence of AI quality metrics (benchmarks) at the product level; “AI‑agent” without reproducible examples/logs of the agent’s operation.
DecAI Fit component summary
- DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 0 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): Per Tier‑1, the project describes AI agents as a current product/platform, not only as an “intention”.
- Evidence: Tier‑1 — https://docs.delaunch.ai
- Why sufficient / why not (one line): This “intent” flag adds no signal when Tier‑1 already describes the product.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The platform allows creating, training and deploying AI agents.
- Evidence: Tier‑1 — https://docs.delaunch.ai
- Why sufficient / why not (one line): The Tier‑1 documentation directly describes the platform’s functions with respect to AI agents.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a public web interface,
Launch, through which one can start creating/launching an agent. - Evidence: Tier‑1 — https://www.delaunch.ai/launch
- Why sufficient / why not (one line): The existence of an accessible demo surface confirms that the product can be “touched”; this does not replace quality metrics (AI_3).
- 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.delaunch.ai
- Why sufficient / why not (one line): No single reproducible set of AI agent quality metrics/benchmarks was found per Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A high‑level architecture of the platform is shown in the docs, but a detailed tech description/model versions are not established per Tier‑1 sources.
- Evidence: Tier‑1 — https://docs.delaunch.ai
- Why sufficient / why not (one line): 1 requires a more specific technical context (components/versions/how training/deployment works); per Tier‑1 sources — 0 (conservatively).
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Avalanche
- Addresses/identifiers: ERC‑20: 0x79Ea4E536f598dCd67C76Ee3829f84AB9E72A558
- Evidence: Tier‑1 — https://snowscan.xyz/token/0x79Ea4E536f598dCd67C76Ee3829f84AB9E72A558
- Why sufficient / why not (one line): The onchain artifact (token contract) is observable via the network explorer.
- 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 (other than the existence of the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): The existence of a token does not prove protocol onchain logic.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: no property of the platform that breaks down without the blockchain (other than the existence of the token) was found per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no proof of “onchain criticality” per Tier‑1.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, AI9000 (ERC‑20), on the Avalanche network.
- Evidence: Tier‑1 — https://snowscan.xyz/token/0x79Ea4E536f598dCd67C76Ee3829f84AB9E72A558
- Why sufficient / why not (one line): The onchain token contract confirms the existence of 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): A mechanism of payment for the service with the token is not confirmed by Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of “payment for the service” for AI9000.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Mechanics of token‑based incentives/collateral/penalties are not confirmed by Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There are no Tier‑1 artifacts of token incentive mechanics.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the token in governance is not confirmed by Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): 1 requires a Tier‑1 governance section/mechanics.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability/irreplaceability of the token is not established per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a description of a mandatory role of the token in the protocol, we do not draw a conclusion about replaceability (conservatively).
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.delaunch.ai | What the “AI” does in the project: a platform for creating/training/deploying AI agents. |
| Tier‑1 | https://www.delaunch.ai/launch | Demo surface: one can start creating/launching an agent (AI_2). |
| Tier‑1 | https://snowscan.xyz/token/0x79Ea4E536f598dCd67C76Ee3829f84AB9E72A558 | Onchain fact of the existence of the AI9000 token on the Avalanche network. |
| Tier‑1 | — | No Tier‑1 source for claim “the AI9000 token is needed for payments/incentives/governance in the protocol” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “there is useful onchain logic other than the token” was found. |
| Tier‑2 | https://www.coingecko.com/en/coins/ai9000 | Reference aggregator card (context; not proof). |
| Tier‑2 | https://coinmarketcap.com/currencies/ai9000/ | Reference aggregator card (context; not proof). |
No comments to display
No comments to display