Skip to main content

Agently

Agently — 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).

Agently — an AI/Agents | Infra project on the Ethereum network, token (symbol: —).

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/framework for creating, deploying and managing AI agents as configurable software (without writing code).
  • Who it’s for: individual users, businesses and teams that need AI agents for tasks in products/operations.
  • Why onchain/token: the onchain fact of the token’s existence on the Ethereum network is confirmed; the token utility is partially confirmed by Tier‑1 (staking + revenue sharing).
  • What you can actually touch (Tier‑1): https://app.agently.dev/ (registration/login to the application).

How it works (very briefly)

  1. The user does: creates/configures an agent in a no‑code interface.
  2. The system does: deploys the agent and connects integrations/channels specified by the configuration.
  3. The user gets: a working agent (or a set of agents) for a specific use case.
  4. Where the blockchain is: the token contract on the Ethereum network is confirmed; onchain logic “other than the token” is not established per Tier‑1.
  5. Token role (if any): Staking (APR) and revenue sharing (ETH revenue share) are confirmed by Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Agently
Also known as (aliases) —
Logo (logo) ../assets/857_agently_logo.png
Token symbol (ticker) AGI
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 0xB8690004604b0352b3832408BA7e02Fe717e9cfD
Token model (token_type) utility (staking + revenue sharing)
Max supply 1 000 000 000 AGI
Issuance —
Tokenomics (tokenomics, brief) staking 25%; liquidity 10%; migration 10%; airdrop partnerships 25% (locked); CEX listings 10% (locked); team/burn wallet 15% (locked); KOLs 5%
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agent creation + deployment platform
Use‑case (use_case) no-code AI agents
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

Agently describes itself as an end‑to‑end framework/platform for creating, deploying and managing AI agents as “functional, configurable software” without writing code. The documentation distinguishes product layers (prebuilt solutions, custom agents, multi‑agent coordination/agency, marketplace, analytics) and deployment/integration options.

Features/modules

  • Prebuilt solutions: ready‑made agents for specific use cases.
  • Custom agents: no‑code configuration of behavior/integrations.
  • AI Agency: coordination of several specialized agents (multi‑agent).
  • Marketplace + analytics: distribution/monitoring and measurement of agent operation.

Typical scenarios

  • Scenario 1: a team creates an agent for an internal process → the agent operates in the selected channels and automates some tasks.
  • Scenario 2: a business deploys an agent as an interface (chat/assistant) → gets a manageable workflow without development.

Getting started (wallet/network)

  • What you need: an account/access to the platform (see Website/Docs).
  • Network/chain: Ethereum (the token contract is recorded in links_* → Explorer).
  • Fees: Ethereum fees for operations with the token (if performed).

Architecture/tech (non‑AI)

  • Components: a web platform for configuring/deploying agents; an onchain token artifact on Ethereum.
  • Participant roles: users/teams that create/manage agents.
  • Where logic runs: A Tier‑1 description of the product’s onchain component (other than the token) is not established; the main product logic appears to be an offchain platform.
  • Dependencies: — (not established per Tier‑1).

Token/economics (expanded, no forecasts)

  • Fact: links_* lists the token contract on the Ethereum network.
  • Token utility: Staking (APR) and revenue sharing (ETH revenue share) are confirmed by Tier‑1 on the official website.
  • Tokenomics (Tier‑1): total supply 1,000,000,000 $AGI; distribution: staking 25%, liquidity 10%, migration 10%, airdrop partnerships 25% (locked), CEX listings 10% (locked), team/burn wallet 15% (locked), KOLs 5%.

Governance

  • — (not established per Tier‑1).

Security and incidents

  • Audits: — (not established per Tier‑1).
  • Bug bounty: — (not established per Tier‑1).
  • Incidents: — (not established per Tier‑1).

Project status and timeline

  • Current status: active (based on the state of the website/documentation).
  • Roadmap: — (not established per Tier‑1).

Ecosystem/integrations

  • Integrations: various deployment options/channels and integrations are described per Tier‑1 (see Docs).
  • Partners: — (not established per Tier‑1).
  • Where it’s actually used: — (not established per Tier‑1).

AI component of the project

  • What is real AI here? the product is described as a platform for creating and managing AI agents (automation of tasks/channels/integrations).
  • What is truly onchain? the token contract on the Ethereum network is confirmed; onchain logic “other than the token” is not established per Tier‑1.
  • Why is a token needed? Staking and revenue sharing are confirmed by Tier‑1; other utilities (payment/incentives in the protocol/governance) are not established per Tier‑1.
  • Red flags (based on the information found): if the token is declared mandatory for access/payments — Tier‑1 tokenomics/terms are needed; the onchain part may come down to the token.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity low 1
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described in Tier‑1 as an operating product/platform, not only as intent/roadmap.
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): This flag is needed only for “AI intent without evidence”; here there is a description of the platform.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The platform enables creating/deploying AI agents and managing them (including as “configurable software”).
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): The Executive Summary explicitly describes the purpose of the platform and the product layers.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public entry point into the application (app), where users can register/log in and start using the platform.
  • Evidence: Tier‑1 — https://app.agently.dev/
  • Why sufficient / why not (one line): There is an unambiguous link to the application (demo surface) on the project’s domain.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): No Tier‑1 quality/performance metrics sufficient for AI_3=1 were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The documentation describes the platform layers, deployment and usage scenarios (at the product level).
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): There is a coherent technical/product description of the structure and modules.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: token: 0xB8690004604b0352b3832408BA7e02Fe717e9cfD
  • Evidence: Tier‑1 — https://etherscan.io/token/0xB8690004604b0352b3832408BA7e02Fe717e9cfD
  • Why sufficient / why not (one line): The onchain fact of the token contract is available in the explorer.
  • 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 token).
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): No Tier‑1 description of the product’s onchain logic, distinct from the token, was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established (conservatively 0).
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): There is insufficient data to assert 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 (contract on the Ethereum network).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xB8690004604b0352b3832408BA7e02Fe717e9cfD
  • Why sufficient / why not (one line): The Explorer confirms 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): 0
  • Claim (one line): The use of the token as a means of payment is not established per Tier‑1.
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): There is no Tier‑1 description of “what the token is used to pay for” (conservatively 0).
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The official website describes staking $AGI with APR and revenue sharing (ETH revenue share) under the token lock mechanics.
  • Evidence: Tier‑1 — https://www.agently.dev/staking
  • Why sufficient / why not (one line): This is Tier‑1 confirmation of incentive mechanics through staking returns/a share of revenue.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1.
  • Evidence: Tier‑1 — https://agently.gitbook.io/agently
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics.
  • 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://agently.gitbook.io/agently
  • Why sufficient / why not (one line): There is no Tier‑1 argumentation “replaceable/irreplaceable”; we conservatively set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://agently.gitbook.io/agently Description of the platform as a no‑code framework for AI agents (product layers, purpose, deployment options).
Tier‑1 https://www.agently.dev/ Product positioning and UI descriptions (“AI workforce”, layers/agents) as the official website.
Tier‑1 https://app.agently.dev/ Public entry point into the application (registration/login) as a “demo surface”.
Tier‑1 https://www.agently.dev/tokenomics Tokenomics: total supply 1,000,000,000 $AGI and distribution.
Tier‑1 https://www.agently.dev/staking Staking $AGI: APR and ETH revenue share (token utility through staking/revenue sharing).
Tier‑1 https://etherscan.io/token/0xB8690004604b0352b3832408BA7e02Fe717e9cfD Onchain fact of the token contract’s existence on the Ethereum network.
Tier‑1 — No Tier‑1 source for claim “the use of the token for governance” was found.

No comments to display

Back to top