CMX Agent
CMX Agent — 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).
CMX Agent — an AI/Agents project on Ethereum, token (symbol: CMX).
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/bot for “on‑ramp/off‑ramp” operations and exchange via chat (claimed on the website).
- Who it’s for: users who want to perform operations via a chat interface (claimed).
- Why onchain/token: onchain is confirmed at the token/contract level on Ethereum; the token utility is not established in Tier‑1.
- What you can actually touch (Tier‑1): Telegram bot/channel — https://t.me/cmxagent_bot
How it works (very briefly)
- The user does: writes to the chatbot what needs to be done (on‑ramp/off‑ramp/exchange — claimed).
- The system does: automates the process of executing the operation (implementation details are not disclosed in Tier‑1).
- The user gets: the result of the operation (not established at the level of a verifiable protocol; this is a product description).
- Where the blockchain is: the token contract on Ethereum.
- Token role (if any): not established in Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | CMX Agent |
| Also known as (aliases) | CMX |
| Logo (logo) | ../assets/894_cmx-agent_logo.png |
| Token symbol (ticker) | CMX |
| Category | AI/Agents | 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 | 0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | chatbot for on/off-ramp + swapping |
| Use‑case (use_case) | exchange + on/off-ramp via chat |
| 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 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://cmxagent.com |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | https://cmxagent.com/roadmap |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e |
| App / Demo | https://t.me/cmxagent_bot |
| X | https://twitter.com/cmxagent |
| Discord | — |
| Telegram | https://t.me/cmxagent |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/cmx-agent |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/cmx-agent/ |
General project overview
CMX Agent describes itself as an AI agent/bot “in chat” that helps perform exchange and on‑ramp/off‑ramp operations. No Tier‑1 document explaining AI architecture/risks/security was found; the token contract on Ethereum and a public link to the Telegram bot remain the verifiable artifacts.
Features/modules
- Chat‑interface: interaction via chat (claimed).
- On‑ramp / off‑ramp: support for several currencies (claimed on the website).
Typical scenarios
- Scenario 1: a user writes a request to the Telegram bot → gets the operation executed (as claimed).
Getting started (wallet/network)
- What you need: Telegram to access the bot (see links_*); an EVM wallet for operations with the token.
- Network/chain: Ethereum.
- Fees: Ethereum network fees for operations with the token/contract.
Architecture/tech (non‑AI)
- Components: only the token contract is confirmed.
- Participant roles: —.
- Where logic runs: not established (Tier‑1).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established (no Tier‑1).
- Issuance/burn: not established.
- Distribution: not established.
Governance
- Who makes decisions: not established.
- How protocol parameters change: —.
Security and incidents
- Audits: not established.
- Bug bounty: not established.
- Incidents: not established.
- Threat model: not established.
Project status and timeline
- Current status: active (based on the website/bot and the token’s onchain artifact).
- Roadmap: there is a roadmap page (see links_*).
Ecosystem/integrations
- Integrations: Telegram (interface).
- Partners: not established.
- Where it’s actually used: not established in the form of verifiable production cases.
AI component of the project
- What is real AI here? per Tier‑1 an “AI agent” is described as a product (a chatbot for operations), but there is no tech description or metrics.
- What is truly onchain? the token contract on Ethereum is confirmed via the explorer.
- Why is a token needed? not established (Tier‑1).
- Red flags (based on the information found): no Tier‑1 tech description of AI; no Tier‑1 description of the token utility; onchain looks like “token only” (OC_2=0).
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 present | 1 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described as a product feature (an AI agent in chat), rather than as “intent only”.
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): AI_0 is used for “intent without implementation”; here Tier‑1 claims a working product.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): An AI agent in chat automates exchange and on‑ramp/off‑ramp operations (as claimed).
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): The Tier‑1 page describes the product’s purpose as an AI agent for exchange/fiat↔crypto operations.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a public link to the Telegram bot/channel (“Try CMX” / bot).
- Evidence: Tier‑1 — https://cmxagent.com/ ; https://t.me/cmxagent_bot
- Why sufficient / why not (one line): The link to the bot allows the presence of a product surface 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://cmxagent.com/
- Why sufficient / why not (one line): No quality metrics/benchmarks were found in Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A technical description/architecture of the AI system is not established in Tier‑1.
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): There is a product description, but no technical docs/versions/architecture.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e
- Evidence: Tier‑1 — https://etherscan.io/token/0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e
- Why sufficient / why not (one line): There is a verifiable onchain artifact (the token contract).
- 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://etherscan.io/token/0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e
- Why sufficient / why not (one line): No Tier‑1 description of protocol onchain logic was found.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established.
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token (contract on Ethereum).
- Evidence: Tier‑1 — https://etherscan.io/token/0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e
- Why sufficient / why not (one line): The token contract is verifiable via 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): The token utility as payment for the service is not established in Tier‑1.
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): 1 requires an explicit Tier‑1 description of payment/fees with the token.
- 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 established in Tier‑1.
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): 1 requires an explicit description of incentives/staking/slashing.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The governance mechanics of the token are not established in Tier‑1.
- Evidence: Tier‑1 — https://cmxagent.com/
- Why sufficient / why not (one line): 1 requires an explicit description of governance/voting with 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://cmxagent.com/
- Why sufficient / why not (one line): 1 requires explicit argumentation of replaceability.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://cmxagent.com/ | Description of the product as “AI Agent … exchange / on‑ramp / off‑ramp”. |
| Tier‑1 | https://t.me/cmxagent_bot | Product surface: Telegram bot/channel (“Try CMX”). |
| Tier‑1 | https://etherscan.io/token/0x30cbdfdaab4bc15e26caf11e1a4703323d77cd3e | Onchain artifact: the token contract on Ethereum. |
| Tier‑1 | — | No Tier‑1 source on the token utility (payments/incentives/governance) was found. |
No comments to display
No comments to display