Cortex Protocol
Cortex Protocol — 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).
Cortex Protocol — an AI/Agents | Infra project on the Ethereum network, token (symbol: CX).
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/application for crypto users (questions/search/wallet data) and an interface for actions such as perp trading (claimed on the official website).
- Who it’s for: users who need an “agent UI” for reading data and performing actions in DeFi/perp products.
- Why onchain/token: the product performs onchain actions (user transactions) on networks/protocols; the CX token is described in Tier‑1 documentation as a governance token and a gated‑access mechanism (agent fees in CX are claimed as a future feature).
- What you can actually touch (Tier‑1): a web application/AI agent on the official website + official user guides with examples of queries/actions.
How it works (very briefly)
- The user does: connects a wallet and asks the agent questions or opens the required “capability” (balances/perps/research).
- The system does: collects data (claimed: real‑time data) and generates a response/action interface; onchain records token operations and user onchain actions in protocols.
- The user gets: a response/hint and the ability to perform an action through the interface.
- Where the blockchain is: the onchain part includes token operations and transactions on the networks/protocols the user works with.
- Token role (if any): in Tier‑1 documentation, the CX token is described as a governance token and as part of a staged rollout (gated‑access); “agent gas/fees in CX” are claimed as a future feature.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Cortex Protocol |
| Also known as (aliases) | Cortex |
| Logo (logo) | ../assets/880_cortex-protocol_logo.png |
| Token symbol (ticker) | CX |
| Category | AI/Agents | Infra |
| 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 | 0x000000000000012def132e61759048be5b5c6033 |
| Token model (token_type) | utility (access + governance) |
| Max supply | 1 646 590 000 CX (total supply; per the docs) |
| Issuance | vesting of part of the supply increase (per the docs; details — in Evidence) |
| Tokenomics (tokenomics, brief) | SYN→CX conversion 1:5.5; supply increase and distribution are described in the official documentation. |
| Governance | governance via CX (per the docs) |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agent for Web3 questions + actions |
| Use‑case (use_case) | unified wallet + agent interface |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 1 / token_score 2 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://cortexprotocol.com/ |
| Docs | https://docs.cortexprotocol.com/ |
| GitHub | https://github.com/cortexprotocol/ |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x000000000000012DeF132E61759048bE5b5C6033 |
| App / Demo | https://cortexprotocol.com/ |
| X | https://twitter.com/Cortex_Protocol |
| Discord | https://discord.gg/cortexprotocol |
| Telegram | https://t.me/cortexprotocolofficial |
| Medium | https://medium.com/cortex-protocol |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/cortex-2/ |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cortex-protocol/ |
General project overview
Cortex is described in the Tier‑1 source (official website) as “Crypto's AI Agent” with features such as: viewing balances/positions, answering questions, and an interface for perp trading. The Tier‑1 links also include documentation and a GitHub organization.
Features/modules
- Ask Cortex: an AI agent for answering questions with “real‑time data” (claimed on the website).
- Wallet / balances: viewing cross‑chain balances and DeFi positions (claimed on the website).
- Perpetual trading UI: an interface for actions with perp positions (claimed on the website).
Typical scenarios
- Scenario 1: a user asks the agent a question → receives an answer (claimed on the website).
- Scenario 2: a user connects a wallet → sees balances/positions (claimed on the website).
- Scenario 3: a user opens/manages a perp position via the UI → actions take place in the corresponding protocols (specific protocols/integrations are not recorded in this card per Tier‑1 sources).
Getting started (wallet/network)
- What you need: a web3 wallet (for actions/viewing), access to the Cortex application/website.
- Network/chain: depends on the assets/protocols the user interacts with; the minimum is Ethereum (for the token).
- Fees: fees of the corresponding networks and protocols for onchain actions.
Architecture/tech (non‑AI)
- Components: a web application/interface, integrations with wallets and external protocols (details — in the project docs); the token (ERC‑20) on the Ethereum network.
- Participant roles: application/agent users.
- Where logic runs: onchain — operations with the token and actions in protocols; offchain — the agent/interface and data aggregation.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility (Tier‑1): governance + gated‑access; “agent gas/fees in CX” are claimed as a future feature (see Evidence).
- Issuance/burn: total supply/vesting parameters are described in Tier‑1 documentation (see Evidence).
Governance
- Who makes decisions: governance via the CX token (per Tier‑1 documentation).
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
Project status and timeline
- Current status: the product is available via the official website (per Tier‑1); the rest — not established.
- Roadmap: —.
Ecosystem/integrations
- Integrations: — (not recorded in this card per Tier‑1).
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? In Tier‑1 (official website + docs), an AI agent is claimed that answers questions and helps perform actions; Tier‑1 quality metrics and a tech description of the model (model/versions) are not recorded.
- What is truly onchain? There is a token on the Ethereum network (the contract is observable in the explorer).
- Why is a token needed? Per Tier‑1 documentation: governance + gated‑access; a future role of “agent gas/fees” is also claimed.
- Red flags (based on the information found): an “AI agent” without technical artifacts (metrics/architecture/releases); onchain boils down to the token.
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 2 |
| Onchain necessity | low | 1 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
- Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
- Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The AI agent answers questions and works with data (wallet balances / token research / web search — as claimed on the website).
- Evidence: Tier‑1 — https://cortexprotocol.com/
- Why sufficient / why not (one line): There is a Tier‑1 description of features, but without metrics (AI_3=0) and the model’s technical architecture (AI_4=0).
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): Tier‑1 documentation includes user guides with examples of using Cortex Agent (queries/operations).
- Evidence: Tier‑1 — https://docs.cortexprotocol.com/docs/CortexAgent/Guide/
- Why sufficient / why not (one line): There are official guides with examples of actions/queries; model quality metrics (AI_3) and a tech description of the model (AI_4) are still not recorded.
- 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): AI quality metrics were not found per Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No Tier‑1 tech description of the AI model (model/versions) was found.
- Evidence: Tier‑1 — https://docs.cortexprotocol.com/
- Why sufficient / why not (one line): 1 requires a specific tech description of the model/versions; this is not recorded in the available Tier‑1 sources.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: ERC‑20 token contract: 0x000000000000012def132e61759048be5b5c6033
- Evidence: Tier‑1 — https://etherscan.io/token/0x000000000000012DeF132E61759048bE5b5C6033
- Why sufficient / why not (one line): Onchain fact: the token contract address on a public network.
- 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) per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no confirmation of onchain logic beyond the token, so 0.
- 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 onchain (per Tier‑1).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no justification of onchain criticality, so 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token on the Ethereum network.
- Evidence: Tier‑1 — https://etherscan.io/token/0x000000000000012DeF132E61759048bE5b5C6033
- Why sufficient / why not (one line): The existence of the token is confirmed by the explorer.
- 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): No Tier‑1 confirmation of mandatory payments with the token for the service was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without evidence, we set 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): In Tier‑1 documentation, CX is described as part of the agent economy: activities generate fees in CX, and security is enhanced through agent staking mechanisms.
- Evidence: Tier‑1 — https://docs.cortexprotocol.com/docs/AgentPlatform
- Why sufficient / why not (one line): The official documentation directly links CX with fees and staking-based security mechanisms (at the level of protocol description).
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): In Tier‑1 documentation, CX is described as the native governance token of Cortex related contracts/protocol/products.
- Evidence: Tier‑1 — https://docs.cortexprotocol.com/docs/CX
- Why sufficient / why not (one line): The Tier‑1 source explicitly records the governance role of 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 — —
- Why sufficient / why not (one line): Without justification, we set 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://cortexprotocol.com/ | Tier‑1 description of the product as an AI agent (balances/perps/ask). |
| Tier‑1 | https://docs.cortexprotocol.com/ | Project documentation (Tier‑1 entry point). |
| Tier‑1 | https://docs.cortexprotocol.com/docs/CortexAgent/Guide/ | User guides with examples of using Cortex Agent (AI_2). |
| Tier‑1 | https://docs.cortexprotocol.com/docs/CX | Tier‑1 description of CX features (governance, gated‑access, agent gas/fees as a future feature) + tokenomics. |
| Tier‑1 | https://docs.cortexprotocol.com/docs/AgentPlatform | Agent Platform: fees in CX and staking mechanisms (protocol description level). |
| Tier‑1 | https://github.com/cortexprotocol/ | Project GitHub organization (Tier‑1). |
| Tier‑1 | https://etherscan.io/token/0x000000000000012DeF132E61759048bE5b5C6033 | Onchain fact: the token contract address on the Ethereum network. |
| Tier‑1 | https://cortexprotocol.com/stake | SYN→CX upgrade/convert portal (Tier‑1 confirmation of the SYN→CX migration). |
| Tier‑1 | — | No Tier‑1 AI quality metrics or tech description of the model (model/versions) were found. |
| Tier‑2 | https://coinmarketcap.com/currencies/cortex-protocol/ | Reference token profile (context). |
No comments to display
No comments to display