AgentLayer
AgentLayer (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).
AgentLayer — an AI/Agents | Infra project: in the Tier‑1 Whitepaper it is described as an infrastructure/layer for AI agents with an economy around the AGENT token; the onchain fact of the token is confirmed by BaseScan.
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: an infrastructure/platform for launching and interacting with AI agents (as described in the Tier‑1 Whitepaper).
- Who it’s for: developers and teams that create/deploy AI agents; users who consume agent services.
- What you can actually touch (Tier‑1): the Explorer & Discover page with the agent catalog.
- Why onchain/token: the AGENT token on Base (Tier‑1 explorer); the Whitepaper claims roles of the token in payment/incentive mechanics and governance.
How it works (very briefly)
- The user does: creates/deploys an AI agent or uses an existing agent.
- The system does: provides a coordination/execution layer and an economy of interaction between agents/users (per the Whitepaper).
- The user gets: access to agent services/tools and interactions.
- Where the blockchain is: the onchain AGENT token (BaseScan); addresses of the protocol’s onchain logic (other than the token) are not confirmed by Tier‑1 sources.
- Token role (if any): payment/staking/rewards and governance are claimed (Whitepaper).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AgentLayer |
| Also known as (aliases) | AGENT |
| Logo (logo) | — |
| Token symbol (ticker) | AGENT |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | L2 (Optimistic Rollup, Base on Ethereum) |
| Launch date (launch_date) | 2024-09-18 (claimed) |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0xF5Bc3439f53A45607cCaD667AbC7DAF5A583633F |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | 1,000,000,000 (as claimed); BaseScan max total supply ~998,003,801.5879 (as of 2026-02-08) |
| Issuance | fixed (as claimed) |
| Tokenomics (tokenomics, brief) | total supply 1B (as claimed); distribution (Core/Community/Ecosystem/Investors/Treasury/Advisors); utility: fees + staking + governance (Tier‑1) |
| Governance | on-chain governance (as claimed) |
| Admins/keys | timelock execution (as claimed); multisig for critical situations (as claimed) |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | execution/coordination infrastructure for AI agents |
| Use‑case (use_case) | deploy + run AI agents |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 3 / 2 / 3 / 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.agentlayer.xyz |
| Docs | https://docs.agentlayer.xyz/ |
| GitHub | — |
| Releases / Changelog | https://agentlayer.medium.com/ |
| Whitepaper | https://agentlayer.xyz/whitepaper |
| Roadmap | https://agentlayer.xyz/whitepaper |
| Security advisories | — |
| Explorer | https://basescan.org/token/0xF5Bc3439f53A45607cCaD667AbC7DAF5A583633F |
| App / Demo | https://agentlayer.xyz/registry |
| X | https://twitter.com/Agent_Layer |
| Discord | https://discord.com/invite/vZK7fCwp7d |
| Telegram | https://t.me/agentlayer |
| Medium | https://agentlayer.medium.com/ |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/agentlayer |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/agentlayer/ |
General project overview
The Tier‑1 Whitepaper describes AgentLayer as an infrastructure/layer for AI agents, where agents can be deployed and interact in a shared environment, while the economy and incentives are tied to the AGENT token. The onchain fact of the token on Base is confirmed; addresses of other protocol contracts (if any) have not been identified.
Features/modules
- Infrastructure for launching and interacting with AI agents (Tier‑1 Whitepaper).
- Claimed mechanics of payment/incentives/participation via AGENT (Tier‑1 Whitepaper).
Typical scenarios
- Scenario 1: a developer deploys an agent → publishes/uses it in the AgentLayer ecosystem.
- Scenario 2: a user calls an agent service → pays for usage/fees (as claimed in the Whitepaper).
Getting started (wallet/network)
- What you need: an EVM wallet and the Base network for onchain operations with the token.
- Network/chain: Base.
- Fees: Base network fees (gas) for operations.
Architecture/tech (non‑AI)
- Components: the EVM AGENT token, offchain execution/coordination components (per the Whitepaper).
- Where logic runs: onchain is confirmed for the token; the rest of the logic is described as infrastructural in the Whitepaper.
Token/economics (expanded, no forecasts)
- Total supply (claimed): 1,000,000,000 $AGENT (Tier‑1 Whitepaper). At the same time, BaseScan shows a Max Total Supply of ~998,003,801.5879 for the token (as of 2026-02-08) — the difference may be due to the format/state of the contract/rounding; this requires re‑checking.
- Token utility (Tier‑1):
- Service fees / platform usage: payments for data transmission, agent deployment and access to APIs/advanced features.
- Staking: a stake is required to launch new agent tokens; staking rewards/node rewards.
- Governance: on-chain voting (token-weighted voting) on upgrades/parameters/allocations.
- Market mechanisms: trading of agent assets/tokens via AGENT (claimed).
- Token distribution (Tier‑1): Core Contributors 20%, Community Building & Node Release 20%, Ecosystem Building 39%, Investors 10%, Long-term Treasury 8%, Advisors 3% (with cliff/vesting per the Whitepaper).
- Limitation: without addresses of protocol contracts (other than the token) we do not confirm onchain necessity above the OC_2 level.
Governance
- On-chain governance (Tier‑1): proposals → community review → token-weighted voting → time-locked execution phase.
- Emergency path (Tier‑1): a multisig wallet is described for critical situations (claimed).
Security and incidents
- Security & compliance (Tier‑1, claimed): watchdog infrastructure, proactive threat detection/response, systematic testing/validation, KYC/AML for compliance.
- Audit / bug bounty: no confirmation found in Tier‑1 sources.
- Incidents: not recorded in Tier‑1 sources.
Project status and timeline
- Token launch (claimed): 2024-09-18 (Tier‑1 Whitepaper).
- Roadmap 2025 (Tier‑1): open-source release of AgentStudio, launch of a decentralized agent marketplace, cross-chain, multi-agent coordination, developer tools/SDK.
Ecosystem/integrations
- AgentStudio (Tier‑1): no-code framework + multimodal base models + APIs + RAG + JS/Python customization.
- AgentLink (Tier‑1): multi-agent orchestration protocols (shared knowledge DB / message queue / command queue).
AI component of the project
- What is real AI here? the AI part is claimed as “agents” (software AI agents performing tasks) and the infrastructure for them.
- What is truly onchain? the AGENT token on Base; the protocol’s onchain logic (other than the token) is not confirmed by addresses in Tier‑1 sources.
- Why is a token needed? per the Whitepaper: payment/incentives/staking and governance.
- Red flags (based on the information found): onchain‑washing — if in the implementation onchain is reduced only to the token; what to double‑check — the existence/addresses of protocol contracts other than the token.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 3 |
| Onchain necessity | medium | 2 |
| Token necessity | high | 3 |
| Evidence | Tier‑1 present | 0 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is claimed as a functional part of the product (AI agents), not only an intent.
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): the intent flag (AI_0) is not needed when there is a Tier‑1 description of an AI feature (AI_1).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): the product describes an infrastructure for AI agents (agents perform tasks/interact in the network).
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): the Tier‑1 Whitepaper describes the agent system as the purpose of the product.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): the official website has an Explorer & Discover page where agents can be opened and tried.
- Evidence: Tier‑1 — https://agentlayer.xyz/registry
- Why sufficient / why not (one line): there is a Tier‑1 “what you can touch” artifact (agent catalog/pages).
- 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): quality metrics of agents/models are not recorded in Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the Whitepaper contains a tech description/architectural elements of the system (within the description of the protocol/layer).
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): there is a Tier‑1 document with an architectural description (sufficient for AI_4=1 per the SSOT).
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: token AGENT: 0xF5Bc3439f53A45607cCaD667AbC7DAF5A583633F
- Evidence: Tier‑1 — https://basescan.org/token/0xF5Bc3439f53A45607cCaD667AbC7DAF5A583633F
- Why sufficient / why not (one line): the onchain fact of the token and the network is confirmed by the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: an on-chain registry and on-chain minting/deployment/trading of AI assets (claimed).
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): the Whitepaper describes the onchain registry and operations with agent assets as part of the protocol.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not proven per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data to prove onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, AGENT.
- Evidence: Tier‑1 — https://basescan.org/token/0xF5Bc3439f53A45607cCaD667AbC7DAF5A583633F
- Why sufficient / why not (one line): the token is confirmed by the explorer.
- 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 payment/fees for services/usage via the token.
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): the Tier‑1 document describes the role of the token in the usage economy.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): the Whitepaper claims staking/incentives via the token.
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): the Tier‑1 document describes staking/incentives as part of the model.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): the Whitepaper claims a governance role of the token.
- Evidence: Tier‑1 — https://agentlayer.xyz/whitepaper
- Why sufficient / why not (one line): the Tier‑1 document describes governance via the token.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): no conclusion about the replaceability of the token has been drawn.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 comparison “with the token/without the token”.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://agentlayer.xyz/whitepaper | description of the product (AI agents) and the roles of the token (fees/staking/governance) |
| Tier‑1 | https://agentlayer.xyz/registry | Agent catalog/pages (“Explorer & Discover”) as “what you can touch”. |
| Tier‑1 | https://basescan.org/token/0xF5Bc3439f53A45607cCaD667AbC7DAF5A583633F | onchain fact of the AGENT token on Base |
| Tier‑1 | — | No Tier‑1 source for claim “addresses/contracts of the protocol (other than the token) and their onchain logic” was found. |
No comments to display
No comments to display