Skip to main content

aiagent.app

aiagent.app (AI Agent App) — 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).

aiagent.app is a web application for creating and using AI agents (assistants for tasks). This card also lists an SPL token on the Solana network, but the Tier‑1 link between the token and payment for/access to the product is not confirmed.

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 web application for creating and launching AI agents for tasks (marketing/sales/content/chat, etc.).
  • Who it’s for: individual users and teams who need an “agentic” assistant for their tasks.
  • Why onchain/token: an SPL token on Solana is confirmed; the necessity of onchain for the product to work (other than the existence of the token) is not established per Tier‑1.
  • What you can actually touch (Tier‑1): the agent catalog/creation https://aiagent.app/agents.

How it works (very briefly)

  1. The user does: goes to the website, opens the agents section, creates/configures an agent.
  2. The system does: runs agentic scenarios (LLM assistants) and integrations/automation (per the description on the website).
  3. The user gets: answers/a plan/drafts/automation of routine tasks.
  4. Where the blockchain is: an SPL token on Solana is confirmed (per the explorer links), but the link between the token and the product mechanics is not confirmed by Tier‑1.
  5. Token role (if any): No Tier‑1 source for claim “the token is needed for payment/access in the product” was found.

Quick links: AI thesis fit

Project passport

Field Value
Project name aiagent.app
Also known as (aliases) AI Agent App
Logo (logo) ../assets/396_aiagent-app_logo.svg
Token symbol (ticker) —
Category AI/Agents | Productivity
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoH+PoS (Tower BFT)
Launch date (launch_date) —
Project status (status) active (web‑app available)
Token (standard) SPL
Token contract 275FUEyp5o7TWo1dCDYJyprb4o2WBcxEQsvmt816pump
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Tier‑1 utility of the token in the product is not confirmed
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) grants (mentioned on the website; the terms require separate verification)
AI component (ai_component) LLM-based agent assistants
Use‑case (use_case) AI agent creation + launch
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Per the Tier‑1 materials of the aiagent.app website, the project provides a web interface for working with AI agents: choosing ready‑made agents and creating your own agents with instructions/knowledge/tools (per the description). The positioning is mostly about “agent productivity” and the automation of routine tasks.

This card also lists an SPL token on the Solana network. However, the available Tier‑1 sources do not record that this token is a mandatory part of the payment/access mechanics of the product.

Features/modules

  • Agent catalog: browsing and launching ready‑made agents.
  • Agent creation: configuring purpose/instructions/knowledge/tools (per the description).
  • Integrations/automation: “integrations” and “smart automation” are claimed (the details of the integrations require separate verification).
  • Changelog: a separate page with product changes.

Typical scenarios

  • Scenario 1: a user chooses a ready‑made agent → gets drafts/answers/plans for the task.
  • Scenario 2: a user creates a custom agent → uses it as an assistant for recurring tasks.
  • Scenario 3: a team uses agents as “operators” for individual functions (marketing/sales/content).

Getting started (wallet/network)

  • What you need: access to https://aiagent.app/ (and the /agents section).
  • Network/chain: using the web‑app does not require onchain operations (per the public page); for working with the token — Solana.
  • Fees: Solana fees arise only for operations with the token (if the user performs them).

Architecture/tech (non‑AI)

  • Components: the web client and the server side of the service; the token on Solana as a separate onchain artifact.
  • Where logic runs: AI inference and task orchestration — offchain (judging by the form of the product); onchain — only the token (confirmed by the explorer link).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Token utility: not established per Tier‑1.
  • Who pays fees: Solana users for operations with the token.
  • Issuance/burn/distribution: not established per Tier‑1 sources.

Governance

  • Who makes decisions: — (not established per Tier‑1 sources).

Security and incidents

  • Audits / bug bounty: — (not established per Tier‑1 sources).
  • Threat model: typical SaaS risks (access to data/integrations), as well as token risks (phishing/address substitution/DEX risks).

Project status and timeline

  • Current status: the web‑app is available; there is a public changelog page.
  • Roadmap: — (not found per Tier‑1 sources).

Ecosystem/integrations

  • Integrations: “integrations” are claimed on the Tier‑1 website (the list of integrations was not extracted).
  • Where it’s actually used: use as a tool for tasks/content/sales (per the description of the use‑cases).

AI component of the project

  • What is real AI here? AI agents/assistants for performing tasks and generating results (per the product description).
  • What is truly onchain? an SPL token on Solana (the mint address is given in this card).
  • Why is a token needed? per Tier‑1 sources, the utility of the token for the product is not confirmed.
  • Red flags (based on the information found): mixing of a SaaS product and a token without an explicit Tier‑1 “token ↔ product” link.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium 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 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim: AI is described as current product functionality (agents/catalog/creation), not only as a plan.
  • Evidence: Tier‑1 — https://aiagent.app/
  • Why sufficient / why not: the intent flag applies when there are only plans without a described product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim: AI agents are used as assistants for tasks and can work with instructions/knowledge/tools (per the description).
  • Evidence: Tier‑1 — https://aiagent.app/
  • Why sufficient / why not: the Tier‑1 website describes the purpose of the AI agents and the usage scenarios.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim: a public /agents section with a catalog and an agent creation interface.
  • Evidence: Tier‑1 — https://aiagent.app/agents
  • Why sufficient / why not: there is an accessible web interface — “what you can touch”.
  • 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: the Tier‑1 sources do not record quality metrics of the models/agents (reproducible benchmarks/evaluations).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim: no Tier‑1 tech description of the architecture/models/versions of the product was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the public page describes the product at the level of capabilities but does not disclose engineering details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: 275FUEyp5o7TWo1dCDYJyprb4o2WBcxEQsvmt816pump
  • Evidence: Tier‑1 — https://solscan.io/token/275FUEyp5o7TWo1dCDYJyprb4o2WBcxEQsvmt816pump
  • Why sufficient / why not: the link to the onchain explorer records the mint address of the token on 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 per Tier‑1 (other than the existence of the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no Tier‑1 description of useful onchain logic of the product.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that a key property of the product breaks down without the blockchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the product looks like an offchain web service; the criticality of onchain is not substantiated.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim: this card lists an SPL token on the Solana network.
  • Evidence: Tier‑1 — https://solscan.io/token/275FUEyp5o7TWo1dCDYJyprb4o2WBcxEQsvmt816pump
  • Why sufficient / why not: the existence of the token is recorded by the explorer link with the mint address.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim: No Tier‑1 source for claim “payment for the service with the token” was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no Tier‑1 description that the token is used to pay for the product.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim: Tier‑1 mechanics of incentives/collateral/penalties via the token are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no verifiable Tier‑1 description of token mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim: Tier‑1 confirmation of governance use of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no Tier‑1 description of a governance process/contracts.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim: a conclusion about the replaceability of the token with an alternative mechanism is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without a described utility of the token, no strict conclusion can be drawn.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://aiagent.app/ positioning of the product as a web application for AI agents; description of scenarios and capabilities
Tier‑1 https://aiagent.app/agents an accessible interface for the catalog/creation of agents (“what you can touch”)
Tier‑1 https://solscan.io/token/275FUEyp5o7TWo1dCDYJyprb4o2WBcxEQsvmt816pump mint address of the SPL token (onchain artifact)
Tier‑1 — No Tier‑1 source for claim “the token is used for payment/access in the product” was found.
Tier‑2 https://coinmarketcap.com/currencies/aiagent-app/ reference profile of the token/project

No comments to display

Back to top