QWEN AI Agent
QWEN AI 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).
QWEN AI Agent — an AI/Agents | Meme 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 token on the Solana network with a claimed “AI agent” positioning (no Tier‑1 confirmation of the AI was found).
- Who it’s for: community members/users who interact with the token.
- Why onchain/token: onchain is needed for issuing/transferring the token; the role of the token in the product is not established per Tier‑1.
How it works (very briefly)
- The user does: buys/transfers the token or adds it to a wallet.
- The system does: onchain records operations with the token.
- The user gets: ownership of the token and the ability to use it where this is supported (not established per Tier‑1).
- Where the blockchain is: the token mint and operations on the Solana network.
- Token role (if any): per Tier‑1, it is not established that the token grants access/functions in the product.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | QWEN AI Agent |
| Also known as (aliases) | — |
| Logo (logo) | — |
| Token symbol (ticker) | — |
| Category | AI/Agents | Meme |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | SPL |
| Token contract | EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh |
| 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) | — |
| Use‑case (use_case) | — |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://qwenai.club/ |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://solscan.io/token/EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh |
| X | https://twitter.com/QWENAI_X |
| Discord | — |
| Telegram | https://t.me/QWENAICTO |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/qwen-ai-agent/ |
General project overview
Per the available Tier‑1 artifacts, only the onchain fact of the token’s existence (mint) on the Solana network is confirmed. No Tier‑1 description of the product/AI component (what exactly the “AI agent” does) and its functions was found.
Features/modules
- Onchain artifact: the token on the Solana network (mint).
Typical scenarios
- Scenario 1: a user transfers the token → gets ownership at an address on the Solana network.
- Scenario 2: a user interacts with the community/channels → the functional part of the product is not established per Tier‑1.
Getting started (wallet/network)
- What you need: a Solana wallet.
- Network/chain: Solana.
- Fees: Solana network fees.
Architecture/tech (non‑AI)
- Components: the token mint on the Solana network.
- Participant roles: token holders.
- Where logic runs: operations with the token — onchain; the “AI agent” product logic is not established per Tier‑1.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1.
- Supply parameters/issuance model: not established per Tier‑1.
Governance
- Who makes decisions: —.
Security and incidents
- Audits: not found per Tier‑1.
- Bug bounty: not found per Tier‑1.
- Incidents: —.
- Threat model: typical token risks (fraud/source spoofing, liquidity risks); without claims of guarantees.
Project status and timeline
- Current status: mainnet (Solana).
- Key releases/milestones: —.
- Roadmap: not found per Tier‑1.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: not established per Tier‑1.
AI component of the project
- What is real AI here? No Tier‑1 confirmation of the AI component/“AI agent” functions was found.
- What is truly onchain? the token mint and operations with the token on the Solana network.
- Why is a token needed? the role of the token in the product is not established per Tier‑1.
- Red flags (based on the information found): AI positioning without Tier‑1 artifacts (docs/code/demo/metrics); onchain boils down to the token; the token utility is not confirmed.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | low | 0 |
| 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): No Tier‑1 declaration of AI intentions was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 source we set 0 (conservatively).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): Per Tier‑1, it is not established what exactly the “AI agent” does.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): A Tier‑1 description of the AI functionality (docs/code/demo) is required.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No public demo/examples of operation were found per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): AI_2=1 requires a verifiable app/demo/tutorial.
- 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): Metrics/benchmarks 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): The tech description/architecture/versions were not found per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): AI_4=1 requires a Tier‑1 tech doc/architecture.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: token mint EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh
- Evidence: Tier‑1 — https://solscan.io/token/EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh
- Why sufficient / why not (one line): There is a verifiable onchain artifact (the token mint) and a 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 per Tier‑1 (other than the issuance/operations of the token).
- Evidence: Tier‑1 — https://solscan.io/token/EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh
- Why sufficient / why not (one line): OC_2=1 requires artifacts of useful onchain logic (contracts/addresses/docs).
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the criticality of onchain for the product is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): OC_3=1 requires the argument “a key property breaks down without the blockchain”.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token (mint on the Solana network).
- Evidence: Tier‑1 — https://solscan.io/token/EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh
- Why sufficient / why not (one line): The onchain artifact confirms the existence of the token.
- 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): Per Tier‑1, it was not found that the token is used to pay for the service/functions of the product.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): A Tier‑1 source (docs/terms/contracts) that describes payment for services with the token is needed.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Incentive/collateral/penalty mechanisms are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): TK_2=1 requires artifacts of the protocol economy (staking/slashing/rewards) with sources.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the token in governance is not confirmed per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): TK_3=1 requires a governance process and confirmation that voting is tied to 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 assessed per Tier‑1 (there is no description of the token’s functions in the product).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): TK_4 requires the context “what function the token performs”.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://solscan.io/token/EQ9n3VXuZu5xJsVvbZQvLRcsdjhQcaPwvziwE76RFMNh | Onchain fact of the token’s existence (mint) on the Solana network. |
| Tier‑1 | — | No Tier‑1 source for claim “what exactly the AI agent does” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “why is a token needed (utility)” was found. |
No comments to display
No comments to display