Skip to main content

AI Agent Layer

AI Agent Layer — 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).

AI Agent Layer — an AI/Agents | Infra project on the Base network, token (symbol: AIFUN).

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 where you can create “personas”/AI agents and issue tokens for them (tokenized agents), and then interact with the agents and trade their tokens (per Tier‑1 sources).
  • Who it’s for: users/communities who want to launch AI personas and the tokens associated with them; creators of content/personas.
  • Why onchain/token: onchain is needed for the issuance and circulation of the AIFUN ERC‑20 token (and agent tokens); AIFUN is claimed as a pairing/payment token within the ecosystem.
  • What you can actually touch (Tier‑1): the platform’s web application: https://fun.aiagentlayer.com/.

How it works (very briefly)

  1. The user does: creates an agent (description/persona, data from X, etc.) in the web application.
  2. The system does: launches the agent and issues the associated token (per the platform’s description).
  3. The user gets: the ability to chat with the agent (after the bonding curve threshold) and to use/distribute the agent on social media.
  4. Where the blockchain is: the AIFUN token and the circulation of tokens (including “agent tokens”) are tied to Base/EVM.
  5. Token role: AIFUN is described as the pairing token for agent tokens and as the payment method for platform features.

Quick links: AI thesis fit

Project passport

Field Value
Project name AI Agent Layer
Also known as (aliases) AIFUN, fun.aiagentlayer.com
Logo (logo) ../assets/597_ai-agent-layer_logo.webp
Token symbol (ticker) AIFUN
Category AI/Agents | Infra
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) PoS (Base; Ethereum L2)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xbDF317F9C153246C429F23f4093087164B145390
Token model (token_type) utility (payments)
Max supply 500,000,000 AIFUN
Issuance —
Tokenomics (tokenomics, brief) Max total supply 500,000,000 AIFUN (per the explorer).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent creation + tokenization
Use‑case (use_case) launch AI personas + agent tokens
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

In Tier‑1 sources, AI Agent Layer describes a platform where the user can create an AI agent (a “persona”), after which a token is issued for the agent. The documentation/website mentions a mechanic of gaining access to chatting with the agent after passing the bonding curve threshold and “DEX trading” after reaching 100%.

The verifiable onchain artifacts are the AIFUN ERC‑20 token on Base and the links/contract associated with it.

Features/modules

  • Web application: agent creation, basic platform actions (see links_*).
  • Documentation (whitepaper): a description of the platform mechanics and the role of the AIFUN token.
  • AIFUN token: pairing/payment token (per the Tier‑1 description) and an ERC‑20 contract on Base.

Typical scenarios

  • Scenario 1: the user creates an AI persona → gets a working agent and the associated agent token.
  • Scenario 2: the user chats with the agent → uses the agent for social interactions/content (per the platform’s description).
  • Scenario 3: the user uses AIFUN for platform features (payments/pairs) — per the documentation.

Getting started (wallet/network)

  • What you need: access to the web application; for onchain actions — an EVM wallet.
  • Network/chain: Base.
  • Fees: Base/EVM network fees for ERC‑20 operations.

Architecture/tech (non‑AI)

  • Components: the platform’s web application; documentation; the AIFUN ERC‑20 contract on Base.
  • Participant roles: users, creators/owners of “agents”, participants of the agent token market.
  • Where logic runs: onchain — the circulation of the AIFUN token and tokens; offchain — the operation of AI agents/the interface (implementation details are not established).
  • Dependencies: — (not identified as verifiable technical dependencies, other than Base/EVM and the external services mentioned on the website).

Token/economics (expanded, no forecasts)

  • Token utility (per Tier‑1): pairing token for the tokens created on the platform; payment method for creating agents on “advanced models” and for access to larger datasets.
  • Max supply: 500,000,000 AIFUN (per BaseScan).
  • Other parameters (distribution/vesting): not established per Tier‑1.

Governance

  • Governance: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.

Project status and timeline

  • Current status: active (based on the presence of the website, documentation and web application).
  • Roadmap: see links_* (GitBook).

Ecosystem/integrations

  • Integrations/partners: — (we do not record them without Tier‑1 confirmations).

AI component of the project

  • What is real AI here? the project claims a platform for creating and using AI agents/personas (described in Tier‑1 sources).
  • What is truly onchain? the AIFUN ERC‑20 contract on Base is confirmed; other platform logic onchain is not identified as separate contracts per Tier‑1.
  • Why is a token needed? AIFUN is described as the pairing/payment token for the tokens created in the ecosystem.
  • Red flags (based on the information found): absence of quality metrics/agent quality metrics (AI_3=0); it is unclear which parts of the system are actually onchain other than the token; key claims about “decentralization” require verifiable artifacts.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity medium 1
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 agents are described as a working part of the product (not only intent/roadmap).
  • Evidence: Tier‑1 — https://aiagentlayer.com/ ; https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): We use AI_0 only when there is “AI intent” without a description of a working AI component; here the AI functionality is described as current.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The platform allows creating AI agents/personas and interacting with them; the agents are linked to tokenization.
  • Evidence: Tier‑1 — https://aiagentlayer.com/ ; https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): Tier‑1 sources describe the purpose of the platform and the basic “create/tokenize/chat/trade” flow.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a web application in which you can create an agent and go through the platform flow.
  • Evidence: Tier‑1 — https://fun.aiagentlayer.com/ ; https://aiagentlayer.com/
  • Why sufficient / why not (one line): A public application is sufficient as a demonstration of “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 — https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): No set of reproducible quality metrics for the AI agents was found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the model architecture/versions at a level sufficient for 1 is not established per Tier‑1.
  • Evidence: Tier‑1 — https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): The documentation describes the product and the flow, but contains no explicit tech description of the AI stack/versioning sufficient for AI_4=1.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: ERC‑20 AIFUN: 0xbDF317F9C153246C429F23f4093087164B145390
  • Evidence: Tier‑1 — https://basescan.org/token/0xbDF317F9C153246C429F23f4093087164B145390
  • Why sufficient / why not (one line): The Explorer page of the token confirms the onchain artifact and the contract address.
  • 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 issuance/circulation of the AIFUN token).
  • Evidence: Tier‑1 — https://aifun-1.gitbook.io/aiagentlayer ; https://aiagentlayer.com/
  • Why sufficient / why not (one line): No enumeration of onchain contracts/addresses of the platform logic other than the token was found (per Tier‑1).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 (other than the fact that the issuance/circulation of tokens requires a network).
  • Evidence: Tier‑1 — https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): OC_3=1 requires an explicit Tier‑1 justification of why a key property of the product breaks down without the blockchain, not only “there is a token”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, AIFUN (ERC‑20 on Base).
  • Evidence: Tier‑1 — https://basescan.org/token/0xbDF317F9C153246C429F23f4093087164B145390 ; https://aiagentlayer.com/
  • Why sufficient / why not (one line): The existence of the contract in the explorer and the mention of $AIFUN on the official website confirm 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): 1
  • Claim (one line): In the Tier‑1 description, AIFUN is specified as the payment method for creating agents on advanced models and for access to larger datasets.
  • Evidence: Tier‑1 — https://aiagentlayer.com/
  • Why sufficient / why not (one line): The official website explicitly describes the payment role of the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentive/collateral/penalty mechanisms requiring AIFUN are not established per Tier‑1.
  • Evidence: Tier‑1 — https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): TK_2=1 requires an explicit incentives/staking/slashing mechanism; it was not found per Tier‑1.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of AIFUN for governance is not established per Tier‑1.
  • Evidence: Tier‑1 — https://aifun-1.gitbook.io/aiagentlayer
  • Why sufficient / why not (one line): There is no explicit description of governance mechanics 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 established per Tier‑1.
  • Evidence: Tier‑1 — https://aiagentlayer.com/
  • Why sufficient / why not (one line): TK_4=1 requires a justification “can be replaced without loss of meaning”; the sources do not assert this.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://aifun-1.gitbook.io/aiagentlayer Tier‑1 description of the platform: “create/personalize/tokenize AI Agents”, the role of $AIFUN and the tokenomics/roadmap sections.
Tier‑1 https://aiagentlayer.com/ Official description of the platform flow (create/tokenize/chat/trade) and of the role of the AIFUN token as a pairing/payment token.
Tier‑1 https://fun.aiagentlayer.com/ “Touch surface” of the product: the platform’s web application (AI_2=1).
Tier‑1 https://basescan.org/token/0xbDF317F9C153246C429F23f4093087164B145390 Onchain fact: ERC‑20 AIFUN on Base, the contract and max total supply.

No comments to display

Back to top