Ozak AI
Ozak 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).
Ozak AI — an AI/Analytics project on Ethereum, token (symbol: OZ).
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 “predictive AI” platform for financial market analytics (as claimed in Tier‑1).
- Who it’s for: users and organizations that need AI insights/risk assessment and data streams (as claimed in Tier‑1).
- Why onchain/token: the $OZ token is claimed to be used for payment for platform features, staking/governance and ecosystem rewards.
- What you can actually touch (Tier‑1): EON early access — https://eon.ozak.ai
How it works (very briefly)
- The user does: connects to the platform/agents and selects the required analytical scenarios (claimed).
- The system does: collects and processes market data, runs models (for example, neural networks, ARIMA — claimed in Tier‑1).
- The user gets: AI insights/risk assessments (as claimed).
- Where the blockchain is: onchain is confirmed at the token/contract level; other protocol contracts are not established.
- Token role (if any): $OZ is claimed as a token for fees/staking/governance and rewards.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Ozak AI |
| Also known as (aliases) | OZ, $OZ |
| Logo (logo) | ../assets/896_ozak-ai_logo.svg |
| Token symbol (ticker) | OZ |
| Category | AI/Analytics | DeFi |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0xc73a02c63277fC12F28Ae6D78bD7E1B6b425911B |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | 10 000 000 000 OZ |
| Issuance | fixed supply: 10 000 000 000 OZ |
| Tokenomics (tokenomics, brief) | presale allocation 30%; token supply 10B; vesting (10% unlock at listing, 1 month cliff, then 6 months linear). |
| Governance | staking for governance (as claimed) |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | predictive ML models for market analytics |
| Use‑case (use_case) | AI insights + risk assessment |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 1 / token_score 3 / evidence_score 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://ozak.ai/ |
| Docs | https://go.ozak.ai/whitepaper |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://ozak.ai/whitepaper1.2.pdf |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/address/0xc73a02c63277fc12f28ae6d78bd7e1b6b425911b |
| App / Demo | https://eon.ozak.ai |
| X | https://twitter.com/OzakAGI |
| Discord | — |
| Telegram | https://t.me/OzakAGI |
| Medium | https://medium.com/@OzakAGI |
| Audit report(s) | https://docs.ozak.ai/Contract-Audits |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/ozak-ai/ |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ozak-ai/ |
General project overview
Ozak AI describes itself as a “predictive AI” platform for financial markets that combines data collection/streaming and a set of ML models to produce analytics and risk assessments. The documents also claim the use of decentralized infrastructure and onchain components for validation/execution; the contract address is confirmed as a verifiable onchain artifact (Etherscan).
Features/modules
- Data streams (OSN): data ingestion/streaming (claimed).
- Prediction agents: customizable prediction models/agents (claimed).
- UI/access: EON early access (see links_*).
- $OZ token: payment for features/staking/governance/rewards (claimed).
Typical scenarios
- Scenario 1: a user launches/uses “prediction agents” → receives analytical conclusions/risk assessment (as claimed).
- Scenario 2: a user gets access to premium data streams → uses them in applications/analytics (as claimed).
Getting started (wallet/network)
- What you need: access to the EON application (see links_*); for operations with the token — an EVM wallet.
- Network/chain: Ethereum (contract/address in links_*).
- Fees: Ethereum network fees for operations with the contract/token.
Architecture/tech (non‑AI)
- Components (per Tier‑1): data ingestion/streaming (OSN), storage (data vaults), prediction agents, execution layer/contracts (claimed).
- Where logic runs: ML inference/analytics — offchain; the onchain part is confirmed at the contract/token address level.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility (Tier‑1): pay platform fees; stake for governance; earn ecosystem rewards.
- Issuance: fixed supply 10B.
- Distribution: presale allocation 30%; liquidity/listings 10%; ecosystem/community 30%; team 10%; future reserve 20% (claimed).
- Vesting (claimed): 10% unlock at listing, 1 month cliff, then 6 months linear.
Governance
- Who makes decisions: not established in detail (Tier‑1); “stake for governance” is claimed.
- How protocol parameters change: —.
Security and incidents
- Audits: claimed (Certik, Sherlock) — see the links in
Audit report(s). - Bug bounty: not established.
- Incidents: not established.
- Threat model: typical risks of ML models + token/contract risks — without Tier‑1 details.
Project status and timeline
- Current status: active (based on the publication of docs/whitepaper and the presence of EON early access).
- Key documents: whitepaper v1.1 (July 2025) and the “Welcome” docs page.
Ecosystem/integrations
- Integrations: EigenLayer AVS and Arbitrum Orbit are mentioned in Tier‑1 as architectural elements.
- Partners: claimed on the website; a detailed Tier‑1 check of partnership verifiability was not conducted.
- Where it’s actually used: not established in the form of “production” cases per Tier‑1.
AI component of the project
- What is real AI here? Tier‑1 sources describe predictive ML models (neural networks, ARIMA and others) and “prediction agents” for market analytics.
- What is truly onchain? the contract/token address is confirmed; separate protocol addresses/contracts (other than the token) are not established.
- Why is a token needed? Tier‑1 claims: platform fees, staking for governance, ecosystem rewards.
- Red flags (based on the information found): absence of verifiable onchain artifacts of protocol logic other than the token; absence of Tier‑1 model quality metrics (AI_3=0).
DecAI Fit component summary
- DecAI Fit: 3/6 — medium 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 | 0 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described as a working part of the product (models/agents), rather than only as “intent”.
- Evidence: Tier‑1 — https://docs.ozak.ai/ ; https://go.ozak.ai/whitepaper
- Why sufficient / why not (one line): AI_0 is about “intent without implementation”; here Tier‑1 describes the AI product itself.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Predictive AI models and “prediction agents” produce market analytics/risk assessments (as claimed).
- Evidence: Tier‑1 — https://docs.ozak.ai/ ; https://go.ozak.ai/whitepaper
- Why sufficient / why not (one line): Tier‑1 describes AI applicability and lists models/approaches.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a public link to EON early access (product surface).
- Evidence: Tier‑1 — https://ozak.ai/ ; https://eon.ozak.ai
- Why sufficient / why not (one line): There is a “Try now / early access” link allowing the presence of the product to be verified.
- 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.ozak.ai/
- Why sufficient / why not (one line): No reproducible set of model/agent quality metrics was found in Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): The whitepaper describes the architecture (OSN, data vaults, prediction agents) and mathematical models (ARIMA, linear regression, neural networks).
- Evidence: Tier‑1 — https://go.ozak.ai/whitepaper ; https://docs.ozak.ai/
- Why sufficient / why not (one line): There is a tech description, including architectural blocks and models.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: 0xc73a02c63277fC12F28Ae6D78bD7E1B6b425911B
- Evidence: Tier‑1 — https://etherscan.io/address/0xc73a02c63277fc12f28ae6d78bd7e1b6b425911b
- Why sufficient / why not (one line): There is a verifiable onchain artifact (the contract address).
- 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 token/contract).
- Evidence: Tier‑1 — https://docs.ozak.ai/
- Why sufficient / why not (one line): Tier‑1 contains a description of “decentralized infrastructure”, but no specific addresses/contracts of protocol logic were found.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that a key property of the product breaks down without the blockchain.
- Evidence: Tier‑1 — https://docs.ozak.ai/
- Why sufficient / why not (one line): There is no Tier‑1 justification of “why onchain is critical” in a verifiable form.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a claimed token, $OZ (fixed supply 10B).
- Evidence: Tier‑1 — https://docs.ozak.ai/ ; https://ozak.ai/ ; https://go.ozak.ai/whitepaper
- Why sufficient / why not (one line): Tier‑1 sources explicitly describe the token and its parameters.
- 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): The $OZ token is claimed to be used for paying platform fees and accessing features/data streams.
- Evidence: Tier‑1 — https://docs.ozak.ai/
- Why sufficient / why not (one line): “Core utilities: Pay platform fees …” is given in Tier‑1.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): The $OZ token is claimed to be used for ecosystem rewards (ecosystem rewards).
- Evidence: Tier‑1 — https://docs.ozak.ai/
- Why sufficient / why not (one line): “Earn ecosystem rewards” is given in Tier‑1.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): The $OZ token is claimed to be used for staking for governance (governance).
- Evidence: Tier‑1 — https://docs.ozak.ai/
- Why sufficient / why not (one line): “Stake for governance” is given in Tier‑1.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token without loss of meaning is not established in Tier‑1.
- Evidence: Tier‑1 — https://docs.ozak.ai/
- Why sufficient / why not (one line): 1 requires an explicit statement/justification of replaceability.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.ozak.ai/ | Description of the platform and “$OZ token in one minute” (utilities: fees/staking/governance/rewards; fixed supply 10B; presale allocation 30% and vesting). |
| Tier‑1 | https://go.ozak.ai/whitepaper | Tech description of the architecture and models (ARIMA, neural networks and others), version 1.1 (July 2025). |
| Tier‑1 | https://eon.ozak.ai | Available product surface (EON early access) for checking the presence of an application/interface. |
| Tier‑1 | https://etherscan.io/address/0xc73a02c63277fc12f28ae6d78bd7e1b6b425911b | Onchain artifact: the contract/token address on Ethereum. |
| Tier‑1 | https://docs.ozak.ai/Contract-Audits | Claimed audits (Certik, Sherlock) — pages/links in Tier‑1. |
| Tier‑1 | — | No Tier‑1 source for claim “there is onchain protocol logic other than the token” was found. |
No comments to display
No comments to display