OCADA
OCADA — 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).
OCADA — an AI/Agents | Infra project on the Solana network, token (symbol: —).
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 set of AI agents for tasks around blockchain/Web3 (for example, transaction risk assessment, alerts, etc.) — per the project’s description.
- Who it’s for: users who need an “agent” for analysis/action tasks in a blockchain environment, and integration developers.
- Why onchain/token: the onchain artifact of the token is confirmed (per the link to the Solana explorer); at the same time, critical onchain logic of the product, other than the token, is not established per Tier‑1.
How it works (very briefly)
- The user does: uses an agent scenario (analytics/alert/check).
- The system does: performs the analysis and returns a result (per the description in the documentation).
- The user gets: an output/recommended next step within the agent’s functionality (without financial advice).
- Where the blockchain is: the token on Solana is confirmed; the rest of the agent logic is offchain (details of the onchain part are not established per Tier‑1).
- Token role: the role of the token in the product/economy is not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | OCADA |
| Also known as (aliases) | Ocada.ai |
| Logo (logo) | ../assets/593_ocada-ai_logo.png |
| Token symbol (ticker) | — |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | SPL |
| Token contract | ocadaAXpD1haGy2JnjHbgUhczqtiMdYHzvnBihjJHg9 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | Tier‑1 docs: token migration BIRD → OCADA; 100% of the supply circulating at launch is claimed; distribution: Bird holders 40%, Team 20%, Development & ecosystem 10%, Community initiatives 10%, Strategic partnerships 10%, Liquidity 10%. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agents for Web3 |
| Use‑case (use_case) | analysis/alerts/help with blockchain operations |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://ocada.ai/ |
| Docs | https://ocada.gitbook.io/docs |
| GitHub | https://github.com/Ocada-ai |
| Releases / Changelog | https://github.com/Ocada-ai/agentx/commits |
| Whitepaper | https://www.ocada.ai/files/OCADA-Litepaper-v01-B.pdf |
| Roadmap | https://ocada.gitbook.io/docs/agent-development-roadmap |
| Security advisories | — |
| Explorer | https://solscan.io/token/ocadaAXpD1haGy2JnjHbgUhczqtiMdYHzvnBihjJHg9 |
| X | https://twitter.com/ocada_ai |
| Discord | — |
| Telegram | https://t.me/Ocada_AI |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/ocada-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ocada-ai/ |
General project overview
In Tier‑1 sources, OCADA describes a set of AI agents to help users with Web3 tasks (for example, transaction risk checks, alerts, etc.). In the documentation, the project also explains what the OCADA acronym stands for and its positioning associated with “Distributed Artificial Intelligence”.
As for the onchain part, this card confirms the token on Solana (the address in the explorer link). Additional onchain contracts/addresses that prove the operation of the product “on the blockchain” are not established per Tier‑1.
Features/modules
- Set of AI agents (claimed): scenarios listed on the website (risk assessment, airdrop alerts, etc.).
- Documentation: description of the project’s goals and terms (see links_*).
Typical scenarios
- Scenario 1: a user launches an agent scenario → receives an analysis/alert result.
- Scenario 2: a developer studies the documentation → plans an integration/use of the agents.
Getting started (wallet/network)
- What you need: access to the website/documentation.
- Network/chain: Solana (in terms of the token).
- Fees: Solana fees for operations with the SPL token (if performed).
Architecture/tech (non‑AI)
- Components: website/documentation; a public GitHub organization (repositories); the SPL token on Solana.
- Participant roles: users of the agents, developers/integrators.
- Where logic runs: the logic of the AI agents is offchain (no confirmation of onchain execution was found per Tier‑1).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1.
Governance
- Governance: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
Project status and timeline
- Current status: active (based on the presence of the website/documentation).
- Roadmap: see links_* (GitBook roadmap).
Ecosystem/integrations
- Integrations/partners: —.
AI component of the project
- What is real AI here? Tier‑1 sources describe AI agents as the basis of the product, but without metrics/architecture at a level sufficient for AI_3/AI_4.
- What is truly onchain? the token on Solana is confirmed; onchain logic of the product (other than the token) is not established.
- Why is a token needed? not established per Tier‑1.
- Red flags (based on the information found): wording about an “AI revolution/precision” without metrics; absence of verifiable onchain contracts of the product (other than the token).
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 | 0 |
| 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 the current essence of the product, not only an intent.
- Evidence: Tier‑1 — https://ocada.gitbook.io/docs ; https://ocada.ai/
- Why sufficient / why not (one line): We do not use AI_0 when there is already a description of the product’s function (AI_1=1).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The project claims AI agents for tasks in a blockchain environment (analytics, security, alerts, etc.).
- Evidence: Tier‑1 — https://ocada.ai/ ; https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): The Tier‑1 website and documentation describe the purpose of the AI agents and example scenarios.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): A public “touch surface” (app/demo) of the AI agent’s operation is not established per Tier‑1.
- Evidence: Tier‑1 — https://ocada.ai/ ; https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): AI_2=1 requires an explicit demo/app that can be launched.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): No quality metrics/benchmarks were found in Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture/versions of the AI component at a level sufficient for 1 are not established per Tier‑1.
- Evidence: Tier‑1 — https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): There are descriptions of the product and terms, but no formalized tech description/versioning was found.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: ocadaAXpD1haGy2JnjHbgUhczqtiMdYHzvnBihjJHg9
- Evidence: Tier‑1 — https://solscan.io/token/ocadaAXpD1haGy2JnjHbgUhczqtiMdYHzvnBihjJHg9
- Why sufficient / why not (one line): The link to the token page in the explorer confirms the onchain artifact and the 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).
- Evidence: Tier‑1 — https://ocada.ai/ ; https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): No addresses/contracts of onchain logic of the product, other than the token, were found (per Tier‑1).
- 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 (other than the token being off the network).
- Evidence: Tier‑1 — https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): OC_3=1 requires an explicit justification of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The link in links_* points to a token on Solana (SPL).
- Evidence: Tier‑1 — https://solscan.io/token/ocadaAXpD1haGy2JnjHbgUhczqtiMdYHzvnBihjJHg9
- Why sufficient / why not (one line): The Explorer link confirms the existence of the token and the address.
- 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): The payment role of the token in the product is not established per Tier‑1.
- Evidence: Tier‑1 — https://ocada.ai/ ; https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): No explicit statement “paying with the token for X service” was found in the available Tier‑1 sources.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Incentives/collateral/penalties requiring the token are not established per Tier‑1.
- Evidence: Tier‑1 — https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): No description of incentives/staking/slashing was found.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the token for governance is not established per Tier‑1.
- Evidence: Tier‑1 — https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): There is no explicit description of governance mechanics via the token.
- 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 — https://ocada.gitbook.io/docs
- Why sufficient / why not (one line): No comparison with an alternative (USDC/subscription) as a justification of replaceability was found in Tier‑1 sources.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://ocada.ai/ | Tier‑1 description of the AI agents and their tasks; links to the documentation/whitepaper. |
| Tier‑1 | https://ocada.gitbook.io/docs | Tier‑1 description of OCADA (what the acronym stands for, purpose, AI agent context). |
| Tier‑1 | https://solscan.io/token/ocadaAXpD1haGy2JnjHbgUhczqtiMdYHzvnBihjJHg9 | Onchain fact: the token on Solana (address). |
| Tier‑1 | https://github.com/Ocada-ai | Public GitHub organization and repository (confirmation of the existence of code/development). |
No comments to display
No comments to display