CPAI by Moontax
CPAI by Moontax — 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).
CPAI by Moontax — a product described as an AI service for automating crypto tax reconciliation (Tier‑1: official website). The CPAI token (ERC‑20, Ethereum) is described as a utility token for Moontax/CPAI services (Tier‑1: documentation).
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 service for processing and categorizing crypto transactions for tax reporting.
- Who it’s for: CPA/tax professionals and users with a large number of crypto transactions.
- Why onchain/token: the CPAI token is described as a utility token for payment/redemption of Moontax services; the existence of the ERC‑20 contract is confirmed onchain.
- What you can actually touch (Tier‑1): the “Get Started” page (onboarding into beta) — https://www.cpai.io/get-started
How it works (very briefly)
- The user does: connects wallets/exchanges and imports transactions (per the product description).
- The system does: the AI engine categorizes transactions and assists with reconciliation.
- The user gets: reports/explanations and results for preparing tax reports.
- Where the blockchain is: the CPAI token exists as an ERC‑20 on Ethereum.
- Token role (if any): redemption of tokens for Moontax credits/services (described in Tier‑1 documentation).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | CPAI by Moontax |
| Also known as (aliases) | Moontax; CPAI |
| Logo (logo) | ../assets/846_moontax_logo.png |
| Token symbol (ticker) | CPAI |
| Category | AI/Analytics | Consumer |
| 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 | 0x6ef69Ba2d051761aFD38F218F0a3cF517D64A760 |
| Token model (token_type) | utility (payments) |
| Max supply | 100,000,000 |
| Issuance | — |
| Tokenomics (tokenomics, brief) | a utility token for Moontax services; there is a burn on redemption (Tier‑1: docs) |
| Governance | company |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI categorization of crypto transactions |
| Use‑case (use_case) | crypto taxes + reconciliation |
| DecAI Fit — AI thesis fit | 2/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 2 / 1 / 1 / 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.cpai.io/ |
| Docs | https://docs.cpai.io/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://docs.cpai.io/solving-your-data-problem-with-ai./the-power-of-ai/cpai-ai-whitepaper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x6ef69Ba2d051761aFD38F218F0a3cF517D64A760 |
| App / Demo | https://www.cpai.io/get-started |
| X | https://twitter.com/OfficialCPAI |
| Discord | — |
| Telegram | https://t.me/OfficialCPAI |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/moontax |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/moontax/ |
General project overview
CPAI describes the product as an AI platform for processing crypto transactions for tax reconciliation and compliance tasks. The documentation describes the CPAI token as a utility token for purchasing/redeeming Moontax services (with a burn mechanism on redemption).
Features/modules
- Connecting wallets/exchanges and importing transactions (claimed).
- AI auto‑categorization of transactions (claimed).
- Tools for manual reconciliation and an audit trail (claimed).
- Report export (claimed).
Typical scenarios
- Scenario: a user connects sources, the system categorizes transactions, then the user exports a report for preparing tax reports.
Getting started (wallet/network)
- What you need: complete onboarding on the “Get Started” page (beta) and connect transaction sources (per the website description).
- Network/chain: Ethereum — for operations with the token.
- Fees: Ethereum network fees for operations with the token.
Architecture/tech (non‑AI)
- Components: a web application + offchain data processing; the ERC‑20 token on Ethereum.
- Where logic runs: analysis/categorization — offchain; the token — onchain (Ethereum).
Token/economics (expanded, no forecasts)
- Token utility: tokens are redeemed for credit/payment for Moontax services (per the documentation).
- Issuance/burn: the documentation describes a burn mechanism on redemption.
- Max supply: 100,000,000 (Tier‑1: Etherscan).
Governance
- Who makes decisions: not established; per the available sources, this is a company product.
Security and incidents
- Audits: not found (no Tier‑1).
- Bug bounty: not found (no Tier‑1).
- Incidents: not established (no Tier‑1).
Project status and timeline
- Current status: beta (per the website description).
Ecosystem/integrations
- Integrations: connections to 50+ wallets/exchanges are claimed.
AI component of the project
- What is real AI here? Per Tier‑1, an AI engine for categorizing transactions and assisting with reconciliation is described.
- What is truly onchain? The CPAI ERC‑20 token on the Ethereum network.
- Why is a token needed? In the documentation, the token is described as a utility token for obtaining Moontax credits/services (redemption; burn on redemption).
- Red flags (based on the information found): accuracy metrics are claimed without methodology/context; no Tier‑1 information about a smart contract audit.
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 | 1 |
| 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 intent is recorded as a product description; a separate AI roadmap is not singled out in Tier‑1.
- Evidence: Tier‑1 — https://www.cpai.io/
- Why sufficient / why not (one line): AI is already claimed as part of the product; we use AI_0 as “intent only”.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): the AI engine categorizes crypto transactions and assists with reconciliation.
- Evidence: Tier‑1 — https://www.cpai.io/
- Why sufficient / why not (one line): the website describes AI auto‑categorization and the reconciliation workflow.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): The official website has a “Get Started” page for onboarding into beta.
- Evidence: Tier‑1 — https://www.cpai.io/get-started
- Why sufficient / why not (one line): there is a public surface (onboarding) that allows users to start working with the product.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: percentages/speed are claimed on the website, but without methodology.
- Context (version/date/how measured): not found.
- Evidence: Tier‑1 — https://www.cpai.io/
- Why sufficient / why not (one line): without context and methodology, we do not consider the metrics sufficient → 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): the tech description/architecture of the AI engine and model versions are not identified in Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a technical specification/versions, we set 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract = 0x6ef69Ba2d051761aFD38F218F0a3cF517D64A760
- Evidence: Tier‑1 — https://etherscan.io/token/0x6ef69Ba2d051761aFD38F218F0a3cF517D64A760
- Why sufficient / why not (one line): Etherscan confirms the token contract and the 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).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of onchain logic beyond the token was identified.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established (no Tier‑1 justification of onchain criticality).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without explicit justification, we set 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the token exists (ERC‑20 on Ethereum).
- Evidence: Tier‑1 — https://etherscan.io/token/0x6ef69Ba2d051761aFD38F218F0a3cF517D64A760
- Why sufficient / why not (one line): the token is identified by the contract and network.
- 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): CPAI tokens are redeemed for credit/payment for Moontax/CPAI services.
- Evidence: Tier‑1 — https://docs.cpai.io/
- Why sufficient / why not (one line): the documentation describes token redemption as credit towards services.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): not established (no Tier‑1 description of incentives/collateral/penalties).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without Tier‑1, we set 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): not established (no Tier‑1 description of governance).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without Tier‑1, we set 0.
- 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 (no Tier‑1 justification).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): with insufficient data, we set 0 (conservatively).
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.cpai.io/ | Product positioning as an AI service for crypto tax reconciliation and auto‑categorization. |
| Tier‑1 | https://www.cpai.io/get-started | App/Demo surface: a public onboarding page for beta (Get Started). |
| Tier‑1 | https://docs.cpai.io/ | Token utility: redemption for credit towards Moontax services; a burn mechanism on redemption is described. |
| Tier‑1 | https://etherscan.io/token/0x6ef69Ba2d051761aFD38F218F0a3cF517D64A760 | The CPAI ERC‑20 token on Ethereum (contract, max total supply). |
| Tier‑1 | — | No Tier‑1 source for claim “onchain logic beyond the token” was found. |
No comments to display
No comments to display