Skip to main content

aiPump

aiPump (AIPUMP) — 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).

aiPump (AIPUMP) — an AI/Agents project (a platform for launching AI agents/AI tokens), token (symbol: AIPUMP) on Solana.

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 platform for creating and launching AI agents/AI tokens (per the official docs) + the utility token AIPUMP (per the white paper).
  • Who it’s for: for creators of AI agents/meme tokens and users who interact with such agents.
  • Why onchain/token: in the white paper, the token is described as the central element of the ecosystem: creation/customization/deployment of agents, payment of fees, governance and staking.
  • What you can actually touch (Tier‑1): Launch App: https://app.aipump.ai/

How it works (very briefly)

  1. The user does: creates an AI agent/token on the platform (per the docs).
  2. The system does: provides a no‑code interface (drag‑and‑drop) and launch mechanics (per the docs).
  3. The user gets: a launched AI agent/token and interaction channels (for example X/Telegram — per the docs).
  4. Where the blockchain is: the AIPUMP token is issued on Solana (and Base is also mentioned), and the white paper describes smart contracts and fair launch mechanics.
  5. Token role (if any): the token is used for creation/customization/deployment of agents, payment of fees, governance and staking (per the white paper).

Quick links: AI thesis fit

Project passport

Field Value
Project name aiPump
Also known as (aliases) AIPUMP
Logo (logo) —
Token symbol (ticker) AIPUMP
Category AI/Agents | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) 2025
Project status (status) active
Token (standard) SPL
Token contract 2w3A2P5juwg234spHKfps7WReWoVmujtErqjaZm9VaiP
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000
Issuance —
Tokenomics (tokenomics, brief) utility token for the AI agent platform; supply 1B (per the white paper)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent launch platform
Use‑case (use_case) create/deploy tokenized AI agents
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 3 / 3
Last verified 2026-02-11

General project overview

In the official documentation, aiPump describes a platform for launching AI agents with a no‑code interface and the idea of “AI agent meme coins”. In the white paper (MiCAR format), the AIPUMP token is described as a utility token for creation/customization/deployment of AI agents, payment of fees, participation in governance and staking mechanics.

Features/modules

  • A no‑code (drag‑and‑drop) platform for creating AI agents (per the docs).
  • A mechanic for launching AI tokens/agents and interaction on social platforms (per the docs).
  • The white paper describes the token as the core element for creation/customization/deployment of agents, fees, governance, staking.

Typical scenarios

  • Scenario 1: a creator configures an AI agent (personality/modules/data sources) → launches/deploys it (per the docs).
  • Scenario 2: a token holder participates in staking → receives Node Points/Fragments and benefits (per the white paper).

Getting started (wallet/network)

  • What you need: read the official docs; for operations with the token — a Solana wallet.
  • Network/chain: Solana (Base is also mentioned in the docs/white paper).
  • Fees: Solana fees for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: an offchain platform/interface + the token on Solana; the white paper describes smart contract risks and the underlying technology.
  • Participant roles: agent creators/users; token holders/stakers; the platform operator.
  • Where logic runs: the AI part and interactions — mostly offchain; onchain — the token/smart contract mechanics.
  • Dependencies: Solana (token) + the offchain infrastructure of the product.

Token/economics (expanded, no forecasts)

  • Token utility: white paper: creation/customization/deployment of AI agents, payment of fees, governance, staking.
  • Protocol necessity drivers: the token is described as the central element of the aiPump ecosystem.
  • Who pays fees: users for onchain operations with the token.
  • Where fees go: — (not extracted from Tier‑1 sources).
  • Issuance/burn: total supply 1,000,000,000 (white paper); other parameters require separate extraction/tables.
  • Incentive mechanisms: staking → Node Points/Fragments → creation of nodes (white paper).
  • Distribution/vesting: the white paper has a section on allocation/vesting (not transcribed into this card).
  • Treasury: —.

Governance

  • Who makes decisions: governance is claimed via the token (per the white paper), but specific mechanics/addresses were not extracted from the Tier‑1 source within this card.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: — (no Tier‑1 confirmation of incidents found).
  • Threat model: the white paper directly mentions smart contract vulnerabilities and AI agent risks (errors/exploits).

Project status and timeline

  • Current status: active; the token exists on Solana.
  • Key releases/milestones: —.
  • Roadmap: the white paper has a roadmap by quarters for 2024–2025.

Ecosystem/integrations

  • Integrations: Solana/Base (as the mentioned chains) + social platforms (X/Telegram) per the docs.
  • Partners: — (no Tier‑1 confirmation of partners found).
  • Where it’s actually used: described in the official docs and the white paper; there is also a Launch App (see links_*).

AI component of the project

  • What is real AI here? The Tier‑1 docs describe AI agents and the platform for their creation/customization (but without quality metrics).
  • What is truly onchain? The Tier‑1 white paper describes the token issuance and smart contract risks/mechanics; the token contract is confirmed in the Solana explorer.
  • Why is a token needed? The white paper lists the utilities: creation/customization/deployment of agents, fees, governance and staking (Node Points/Fragments).
  • Red flags (based on the information found): quality metrics of the AI agents are not disclosed in Tier‑1 sources; re‑checking is required of which parts of the logic/inference run onchain vs offchain (other than the token).

DecAI Fit component summary

  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity high 3
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 part of the product/platform, not just as intent.
  • Evidence: Tier‑1 — https://docs.aipump.ai/intro
  • Why sufficient / why not (one line): The documentation describes AI agents and the platform.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI agents are created/customized and interact with users on platforms such as X/Telegram (per the docs).
  • Evidence: Tier‑1 — https://docs.aipump.ai/intro ; https://docs.aipump.ai/ai-agent-launch-platform
  • Why sufficient / why not (one line): Tier‑1 describes interaction scenarios and platform modules.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The official website has a Launch App (app.aipump.ai).
  • Evidence: Tier‑1 — https://aipump.ai/ ; https://www.aipump.ai/launch ; https://app.aipump.ai/
  • Why sufficient / why not (one line): There is a public entry point into the product (Launch App) that can be verified.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: —
  • Why sufficient / why not (one line): Quality metrics of the AI agents were not found in Tier‑1 sources.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): There is Tier‑1 documentation and a white paper with a description of the token/project and risks.
  • Evidence: Tier‑1 — https://docs.aipump.ai/intro ; https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf
  • Why sufficient / why not (one line): The presence of a white paper increases the verifiability of the key claims.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: 2w3A2P5juwg234spHKfps7WReWoVmujtErqjaZm9VaiP
  • Evidence: Tier‑1 — https://solscan.io/token/2w3A2P5juwg234spHKfps7WReWoVmujtErqjaZm9VaiP ; https://docs.aipump.ai/intro
  • Why sufficient / why not (one line): The token address is listed in the Tier‑1 docs and confirmed in the explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the white paper describes smart contracts/fairlaunch mechanics (and related risks), and the token is used for interactions on the platform.
  • Evidence: Tier‑1 — https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf
  • Why sufficient / why not (one line): The white paper has sections on the underlying technology and smart contract vulnerabilities.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: strict onchain criticality for the product is not proven per Tier‑1 sources.
  • Evidence: —
  • Why sufficient / why not (one line): There are onchain mechanics and a token, but no clear proof of “without the blockchain the product breaks down”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a utility token, AIPUMP.
  • Evidence: Tier‑1 — https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf ; https://solscan.io/token/2w3A2P5juwg234spHKfps7WReWoVmujtErqjaZm9VaiP
  • Why sufficient / why not (one line): The white paper and the explorer confirm the token.
  • 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): In the white paper: the token is used for creation/customization of AI Agents and payment of transaction fees for interactions on the platform.
  • Evidence: Tier‑1 — https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf
  • Why sufficient / why not (one line): Tier‑1 explicitly lists the practical applications of the token.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): The white paper describes staking: staking tokens → Node Points/Fragments → creation of additional nodes and benefits.
  • Evidence: Tier‑1 — https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf
  • Why sufficient / why not (one line): Tier‑1 directly describes the staking structure and roles.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): In the white paper, the token is described as a governance token: participation in key decisions on the platform’s development.
  • Evidence: Tier‑1 — https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf
  • Why sufficient / why not (one line): Tier‑1 contains wording about the governance function.
  • 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 sources.
  • Evidence: —
  • Why sufficient / why not (one line): The white paper asserts that the token is built into the platform’s mechanics, but no comparison with alternatives is provided.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.aipump.ai/intro Description of the aiPump platform, AI agents and the claimed features.
Tier‑1 https://docs.aipump.ai/ai-agent-launch-platform Description of the no‑code platform and the components of AI agents.
Tier‑1 https://docs.aipump.ai/intro The docs list the Base CA and Solana CA of the token.
Tier‑1 https://solscan.io/token/2w3A2P5juwg234spHKfps7WReWoVmujtErqjaZm9VaiP Onchain fact: the token on Solana.
Tier‑1 https://app.aipump.ai/ Launch App (public entry point into the product).
Tier‑1 https://cdn.prod.website-files.com/673dc59d09096b984d43a8a6/67d880759d6042469b66a1a7_NIMBUS%20ENTERPRISES%20LTD%20-%20AIPUMP%20White%20Paper%20under%20MiCAR.pdf White paper: token utility (create agents/fees/governance/staking) and technical/risk details.
Tier‑2 https://www.coingecko.com/en/coins/aipump Token context/metadata (aggregator).

No comments to display

Back to top