PAAL AI
PAAL AI (PAAL) — 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).
PAAL AI — an AI/Agents | Infra project on Ethereum, token (symbol: PAAL).
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 set of AI products (bots/agents/trading/audits) and a platform for integrating them into communities and business processes.
- Who it’s for: communities/projects that need an AI bot; teams that need AI agents, AI audits and research/trading tools.
- Why onchain/token: the PAAL token is used as access/payment and as an incentive mechanism (staking/revshare) in the ecosystem.
- What you can actually touch (Tier‑1):
app.paal.ai(Paal Bot),audit.paal.ai(AI audits),agents.paal.ai(Enterprise Agents, login),rewards.paal.ai(staking).
How it works (very briefly)
- The user does: connects a Paal bot/agent or orders an AI service (bot, agent, audit, trading tool).
- The system does: provides the interface/integrations (web/chat), performs the AI processing and delivers results (answers, signals, reports).
- The user gets: an AI assistant/agent or a report/audit/analytics.
- Where the blockchain is: onchain, the PAAL token (ERC‑20) and its mechanics (staking/revshare/access) are confirmed.
- Token role: access/payment for AI products + staking/rewards (Tier‑1).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | PAAL AI |
| Also known as (aliases) | PAAL | $PAAL | PaalMind |
| Logo (logo) | ../assets/51_paal-ai_logo.webp |
| Token symbol (ticker) | PAAL |
| 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 | 0x14fee680690900ba0cccfc76ad70fd1b95d10e16 |
| Token model (token_type) | utility (payments + staking + rewards) |
| Max supply | 1,000,000,000 |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | 0% buy/sell tax; buybacks → staking pools; revshare + staking rewards (Tier‑1) |
| Governance | company / community (as claimed in the whitepaper) |
| Admins/keys | renounced (token contract) |
| Audit | yes (AI audits product + audit page) |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agent platform (workflows/tools/KB) |
| Use‑case (use_case) | AI bots/agents for crypto + communities |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 1 / token_score 2 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.paal.ai/ |
| Docs | https://docs.paal.ai/ |
| GitHub | https://github.com/paal-ai |
| Releases / Changelog | https://www.paal.ai/blog |
| Whitepaper | https://docs.paal.ai/collaborating/how-we-work-together/whitepaper |
| Roadmap | https://www.paal.ai/roadmap |
| Security advisories | https://github.com/paal-ai/twitter-reply-bot/security/advisories |
| Explorer | https://etherscan.io/token/0x14fee680690900ba0cccfc76ad70fd1b95d10e16 |
| App / Demo | https://app.paal.ai/ |
| X | https://twitter.com/PaalMind |
| Discord | https://discord.com/invite/paalai |
| Telegram | https://t.me/paal_ai |
| Medium | https://medium.com/@admin_42570 |
| Audit report(s) | https://docs.paal.ai/features/products/ai-audits |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/paal-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/paal-ai/ |
General project overview
PAAL AI is a product ecosystem around AI bots and AI agents for communities and businesses. Per Tier‑1 sources it includes: “Paal Bot” (a web bot), Enterprise Agents (a platform for creating/managing agents and workflows), AI contract audits (Audit.Paal), staking/rewards and other products (including a trading agent/terminal and GPU rentals — in the whitepaper). The onchain part in this card is confirmed primarily by the PAAL token (ERC‑20) and by the fact that access/payment/staking are tied to the token.
Features/modules
- Paal Bot / AI Studio:
app.paal.aias the entry point for “Get bot”. - Enterprise Agents: the
agents.paal.aiweb platform (login) for creating/managing AI assistants and workflows (description on the website). - AI Audits:
audit.paal.ai+ documentation on the product and API (Tier‑1 docs). - Tokenomics/incentives: supply 1B, 0% tax, staking + ETH rewards (Tier‑1 docs).
Typical scenarios
- Scenario 1 (community bot): an admin/team connects a Paal bot → gets an AI assistant for answers/research/metrics in a chat channel (per the product descriptions).
- Scenario 2 (AI contract audit): a user enters a contract address in Audit.Paal → gets a security score/insights and a report (Tier‑1 docs).
- Scenario 3 (staking): a holder stakes PAAL on
rewards.paal.ai→ receives PAAL and/or ETH rewards per pool (Tier‑1 docs).
Getting started (wallet/network)
- What you need: an account/access to the web products (Paal Bot / Agents / Audit); for staking — an EVM wallet with PAAL.
- Network/chain: Ethereum mainnet (the ERC‑20 PAAL token).
- Fees: gas on Ethereum (approve/stake/transfer), as well as possible product payments/subscriptions in PAAL (whitepaper + docs).
Architecture/tech (non‑AI)
- Components: web applications (app/agents/audit), the API for Audit.Paal, the onchain ERC‑20 PAAL token and staking contracts (described in the docs; staking addresses were not extracted).
- Participant roles: users/clients of the AI services; token holders/stakers; the team/platform operator (company).
- Where logic runs: offchain — AI inference/processing and product functions; onchain — token ownership/transfer, staking and the related rewards.
- Dependencies: Ethereum; external AI models/providers are mentioned in the whitepaper (GPT‑4/Claude/IBM WatsonX), but the specific implementation was not verified.
Token/economics (expanded, no forecasts)
- Token utility: access/payment for AI services (“all core products … require $Paal for access” — whitepaper), staking rewards and revshare (docs).
- Protocol necessity drivers: the token is used for access to the products and as a condition for participation in staking/rewards.
- Who pays fees: Ethereum users (gas); users pay PAAL for the service/subscriptions (whitepaper).
- Where fees go: onchain fees (gas) — to Ethereum validators; product payments/revenues — into the project’s economy (revshare/buybacks are claimed; distribution details were not extracted).
- Issuance/burn: total supply 1,000,000,000; the docs state a fixed supply; the whitepaper describes deflationary mechanics as part of the model (without specific parameters).
- Security/incentive mechanisms: staking pools of 14/28/56 days; APY (PAAL) and distribution of ETH rewards across the pools (Tier‑1 docs).
- Distribution and token issuance schedule: — (not extracted per Tier‑1).
- Treasury: — (not extracted).
Governance
- Who makes decisions: the team/company; the whitepaper claims governance participation for token holders, but the specific onchain mechanism is not confirmed.
- How protocol parameters change: — (not extracted).
- Where decisions are discussed/made: —.
- Keys/multisig: the token contract is claimed to be renounced (docs); the rest — not extracted.
Security and incidents
- Audits: there is an “AI Audits” product with security scores/reports and an API (Tier‑1 docs); the whitepaper also describes AI audits as a component.
- Bug bounty: — (not found in links_*).
- Incidents: — (not established).
- Threat model: centralization of the backend/AI inference, the need to separately confirm claims about AI with measurable artifacts and metrics, the risk of errors in AI audits/scoring, dependence on web interfaces and API keys.
Project status and timeline
- Current status: the product interfaces are available; the PAAL token is active on Ethereum (Tier‑1).
- Key releases/milestones: — (versions/releases were not recorded).
- Roadmap: a separate roadmap page is published (Tier‑1).
Ecosystem/integrations
- Integrations: Discord/Telegram bots and a web widget (sections in the docs); the API for Audit.Paal; EVM integration for staking.
- Partners: “Supported by …” are listed on the website (e.g. IBM/Google Cloud), but the details of the partnerships were not verified.
- Where it’s actually used: as a set of AI products for users/communities (app/audit/agents) and as a token‑gating/staking system.
AI component of the project
- What is real AI here? Tier‑1 describes a product line of AI bots/agents and services such as AI audits of smart contracts (including an API) and AI trading/research (whitepaper + website + docs).
- What is truly onchain? The ERC‑20 PAAL token on Ethereum is confirmed; the rest of the logic (bots/agents/audits) is predominantly offchain.
- Why is a token needed? Tier‑1 states that the token grants access to AI services/subscriptions and is used in the staking/revshare mechanics.
- Red flags (based on the information found): AI‑washing (the whitepaper contains broad claims about “decentralized AI” and governance without verifiable metrics), onchain‑washing (the product lives offchain), token‑washing (it needs to be re‑checked whether access to the products really strictly requires PAAL and how billing is set up), what to double‑check: the addresses/code of the staking contracts, the buyback/revshare economics and the actual access conditions.
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 3 |
| Onchain necessity | low | 1 |
| Token necessity | high | 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): The presence of AI is confirmed not only by intent but by available products (bot/agents/audits).
- Evidence: Tier‑1 — https://www.paal.ai/, https://docs.paal.ai/
- Why sufficient / why not (one line): the intent flag is not needed when demo artifacts are present (AI_2=1).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): PAAL provides AI bots/agents and AI audits of smart contracts (security score/reports) as products.
- Evidence: Tier‑1 — https://www.paal.ai/, https://docs.paal.ai/features/products/ai-audits
- Why sufficient / why not (one line): Tier‑1 describes specific functions of the AI products.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): there are public product interfaces:
app.paal.ai(Paal Bot) andaudit.paal.ai(running an audit/score), as well asrewards.paal.aifor staking. - Evidence: Tier‑1 — https://app.paal.ai/, https://docs.paal.ai/features/products/ai-audits, https://docs.paal.ai/tokenomics/staking
- Why sufficient / why not (one line): these are reproducible entry points into the product + usage instructions.
- Conflict note (if any): some features may require an account/credits.
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://3811185256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5bkDvV8shY8wIeGZMnwo%2Fuploads%2FcHgsnzx70QfhKorCizcU%2FPaal%20AI%20Whitepaper%202025.pdf?alt=media&token=f3a52c81-6de8-4a93-adae-48414481bee7
- Why sufficient / why not (one line): Tier‑1 has no verifiable quality benchmarks for the models/audit scoring.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): docs and a whitepaper are published describing the components (bots/agents/audits/AI Studio/tokenomics) and product instructions (Audit.Paal API, staking).
- Evidence: Tier‑1 — https://docs.paal.ai/, https://3811185256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5bkDvV8shY8wIeGZMnwo%2Fuploads%2FcHgsnzx70QfhKorCizcU%2FPaal%20AI%20Whitepaper%202025.pdf?alt=media&token=f3a52c81-6de8-4a93-adae-48414481bee7
- Why sufficient / why not (one line): there is a technical description at the level of architecture and usage procedures.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: PAAL (ERC‑20): 0x14fee680690900ba0cccfc76ad70fd1b95d10e16
- Evidence: Tier‑1 — https://etherscan.io/token/0x14fee680690900ba0cccfc76ad70fd1b95d10e16, https://docs.paal.ai/tokenomics/token-information
- Why sufficient / why not (one line): the token contract and the chain are verifiable via the explorer and the Tier‑1 token page.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: apart from the token and the staking mechanics (contract addresses not extracted), the product’s onchain logic is not proven in the reviewed Tier‑1 sources.
- Evidence: Tier‑1 — https://www.paal.ai/, https://docs.paal.ai/
- Why sufficient / why not (one line): the product functions (bots/agents/audits) are described as offchain services.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the core product (AI services) can work without a blockchain; the blockchain here is the token/incentive/access layer.
- Evidence: Tier‑1 — https://www.paal.ai/, https://docs.paal.ai/
- Why sufficient / why not (one line): onchain criticality is not proven.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, PAAL (ERC‑20), on Ethereum.
- Evidence: Tier‑1 — https://docs.paal.ai/tokenomics/token-information
- Why sufficient / why not (one line): Tier‑1 records the token parameters and the chain.
- 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): the whitepaper claims that “all core products and services … require $Paal for access”, including payments for AI tools/subscriptions/audits.
- Evidence: Tier‑1 — https://3811185256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5bkDvV8shY8wIeGZMnwo%2Fuploads%2FcHgsnzx70QfhKorCizcU%2FPaal%20AI%20Whitepaper%202025.pdf?alt=media&token=f3a52c81-6de8-4a93-adae-48414481bee7
- Why sufficient / why not (one line): Tier‑1 explicitly positions the token as the payment/access rail for the products.
- Conflict note (if any): the actual pricing/billing was not extracted.
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): the staking and reward model is described in Tier‑1 (PAAL rewards + distribution of ETH rewards across the pools).
- Evidence: Tier‑1 — https://docs.paal.ai/tokenomics/staking, https://docs.paal.ai/tokenomics/token-information
- Why sufficient / why not (one line): Tier‑1 gives specific pool/distribution parameters.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the whitepaper mentions governance participation, but a specific implemented voting/DAO mechanism is not confirmed in the extracted Tier‑1 artifacts.
- Evidence: Tier‑1 — https://3811185256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5bkDvV8shY8wIeGZMnwo%2Fuploads%2FcHgsnzx70QfhKorCizcU%2FPaal%20AI%20Whitepaper%202025.pdf?alt=media&token=f3a52c81-6de8-4a93-adae-48414481bee7
- Why sufficient / why not (one line): without Tier‑1 links to an actually working governance process 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 as a strict conclusion per Tier‑1.
- Evidence: Tier‑1 — https://docs.paal.ai/tokenomics/token-information
- Why sufficient / why not (one line): Tier‑1 describes the utility but does not compare it with alternatives.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.paal.ai/ | Tier‑1: the product line (Paal Bot, Enterprise Agents, trading agent, links to app/agents/rewards) and positioning. |
| Tier‑1 | https://docs.paal.ai/tokenomics/token-information | Tier‑1: the PAAL token on Ethereum, total supply 1B, 0% taxes, renounced, utility (revshare/buybacks/staking/premium services). |
| Tier‑1 | https://docs.paal.ai/tokenomics/staking | Tier‑1: staking pools, APY and distribution of ETH rewards by term. |
| Tier‑1 | https://3811185256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5bkDvV8shY8wIeGZMnwo%2Fuploads%2FcHgsnzx70QfhKorCizcU%2FPaal%20AI%20Whitepaper%202025.pdf?alt=media&token=f3a52c81-6de8-4a93-adae-48414481bee7 | Tier‑1: whitepaper 2025 (components, token gating claims, AI audits/agents/studio/GPU rentals). |
| Tier‑1 | https://docs.paal.ai/features/products/ai-audits | Tier‑1: Audit.Paal as a product (multi‑chain, security score, API endpoints). |
| Tier‑1 | https://etherscan.io/token/0x14fee680690900ba0cccfc76ad70fd1b95d10e16 | Tier‑1: the onchain fact of the PAAL ERC‑20 contract on Ethereum. |
| Tier‑1 | — | No Tier‑1 bug bounty / security advisories were found (not confirmed by Tier‑1). |
| Tier‑2 | — | — |
| Tier‑3 | — | — |
No comments to display
No comments to display