Skip to main content

Agrello

Agrello (DELTA) — 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).

Agrello — a project on Ethereum with the DELTA token (ERC‑20); Tier‑1 sources claim the use of AI as part of the product (intent), but no confirmation of a working AI component at the protocol level was found.

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/product for creating and managing agreements/smart contracts (claimed in Tier‑1).
  • Who it’s for: teams and users who need a “human‑oriented” interface for agreements and automation of obligations (claimed).
  • Why onchain/token: the existence of the DELTA token (ERC‑20) and its contract is confirmed in Tier‑1; the necessity of the token for access/payment in the product is not established per Tier‑1.

How it works (very briefly)

  1. The user does: creates/configures an agreement and its terms (claimed).
  2. The system does: forms the structure/terms of the agreement and helps go through the scenario (claimed).
  3. The user gets: the agreement document/terms and an execution/accounting mechanism (claimed).
  4. Where the blockchain is: the DELTA token contract on Ethereum is confirmed in Tier‑1; other onchain components (registry/execution) are not established per Tier‑1.
  5. Token role (if any): the DELTA token exists; no Tier‑1 confirmation of a specific utility (payment/access/incentives) was found.

Quick links: AI thesis fit

Project passport

Field Value
Project name Agrello
Also known as (aliases) Agrello DELTA; DELTA token
Logo (logo) ../assets/541_agrello-delta_logo.svg
Token symbol (ticker) DELTA
Category AI/Other
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0x07e3c70653548B04f0A75970C1F81B4CBbFB606f
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI assistance/agents for agreements
Use‑case (use_case) smart contracts for agreements
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 0 / 2
Last verified 2026-02-11

General project overview

Agrello positions itself as a product in the field of agreements/smart contracts with an emphasis on “human‑oriented” creation and management of terms, as well as on AI assistance (intent).
No Tier‑1 confirmation of a working AI component at the protocol/product level with measurable artifacts (metrics/architecture/demo) was found.

Features/modules

  • “Human‑friendly” creation/management of agreements (claimed).
  • AI assistance/assistant (intent; without confirmation of measurable artifacts per Tier‑1).

Typical scenarios

  • Scenario 1: the user forms an agreement → receives the terms/document and the process (claimed).
  • Scenario 2: a team agrees on terms between the parties → receives a single agreement artifact (claimed).

Getting started (wallet/network)

  • What you need: an account/access to the product (details are not established per Tier‑1).
  • Network/chain: Ethereum (the DELTA token — ERC‑20).
  • Fees: Ethereum network fees when interacting with the token; other fees/product mechanics — not established.

Architecture/tech (non‑AI)

  • Components: the DELTA token contract on Ethereum + offchain components of the product (details not established).
  • Participant roles: users/teams creating and signing agreements (claimed).
  • Where logic runs: onchain is confirmed only at the token level; the rest of the logic — not established.
  • Dependencies: — (not found per Tier‑1).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (other than the fact of the token’s existence).
  • Protocol necessity drivers: not established.
  • Who pays fees: users for onchain operations with the token (Ethereum).
  • Where fees go: to the Ethereum network validators (gas); Agrello protocol fees — not established.
  • Issuance/burn: — (not established).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: — (not established).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established).
  • How protocol parameters change: — (not established).
  • Where decisions are discussed/made: — (not established).
  • Keys/multisig: — (not established).

Security and incidents

  • Audits: — (not found per Tier‑1).
  • Bug bounty: — (not found per Tier‑1).
  • Incidents: — (not found per Tier‑1).
  • Threat model: no verifiable AI artifacts were found per Tier-1; the necessity of the token is also not established.

Project status and timeline

  • Current status: — (not established).
  • Key releases/milestones: — (not established).
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: — (not found per Tier‑1).
  • Partners: — (not found per Tier‑1).
  • Where it’s actually used: — (not found per Tier‑1).

AI component of the project

  • What is real AI here? Tier‑1 sources claim the use of AI assistance/agents, but no confirmation of a working AI component with metrics/architecture was found.
  • What is truly onchain? The DELTA token on Ethereum is confirmed (ERC‑20 contract). Other onchain components of the product are not established per Tier‑1.
  • Why is a token needed? The existence of the token is confirmed; no Tier‑1 confirmation of a specific necessity of the token for access/payment/incentives was found.
  • Red flags (based on the information found): AI‑washing risk (intent without verifiable artifacts), token‑washing risk (the necessity of the token is not established), the token utility and the actual status of the product require re‑checking.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 partial 2
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): in Tier‑1 sources the project is positioned as “powered by AI”/AI‑assisted.
  • Evidence: Tier‑1 — https://www.agrello.id/
  • Why sufficient / why not (one line): this records intent but does not prove a working AI component (without metrics/architecture/demo).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): what exactly the AI component does (in terms of functions/boundaries) — not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.agrello.org/Agrello-Self-Aware_Whitepaper-English.pdf
  • Why sufficient / why not (one line): no unambiguous, verifiable description of AI features sufficient for 1 was found.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a public demo/example of the AI part in operation was not found per Tier‑1.
  • Evidence: Tier‑1 — https://www.agrello.id/
  • Why sufficient / why not (one line): without a Tier‑1 demo/guide we set 0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found.
  • Context (version/date/how measured): not found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): metrics/benchmarks were not found → 0.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a tech description/architecture of the AI component sufficient for 1 is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.agrello.org/Agrello-Self-Aware_Whitepaper-English.pdf
  • Why sufficient / why not (one line): not enough specifics for 1 were found per Tier‑1.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the DELTA token (ERC‑20): 0x07e3c70653548B04f0A75970C1F81B4CBbFB606f
  • Evidence: Tier‑1 — https://etherscan.io/token/0x07e3c70653548B04f0A75970C1F81B4CBbFB606f
  • Why sufficient / why not (one line): the existence of the onchain artifact is confirmed in the block 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 (per Tier‑1 only the token is confirmed).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without confirmation of onchain logic beyond the token, we set 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established what breaks down without onchain (per Tier‑1).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, DELTA (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x07e3c70653548B04f0A75970C1F81B4CBbFB606f
  • Why sufficient / why not (one line): the existence of the token is confirmed by the contract.
  • 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 necessity of the token as payment for the service is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without Tier‑1 confirmation of utility → 0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentive/collateral/penalty mechanisms via the token are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • 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 — —
  • Why sufficient / why not (one line): no grounds for 1 were found → 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token (for example, with regular payment) is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): insufficient data for a conclusion → 0 (conservatively).
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.agrello.id/ intent: the project is positioned as AI‑assisted/powered by AI
Tier‑1 https://docs.agrello.org/Agrello-Self-Aware_Whitepaper-English.pdf Tier‑1 documentation/whitepaper of the project (context)
Tier‑1 https://etherscan.io/token/0x07e3c70653548B04f0A75970C1F81B4CBbFB606f onchain: the DELTA token contract (ERC‑20, Ethereum)
Tier‑1 https://github.com/Agrello the official GitHub (a development artifact; by itself it does not prove the product)
Tier‑1 — No Tier‑1 source for claim “the token is mandatory for payment/access in the product” was found.
Tier‑2 https://coinmarketcap.com/currencies/agrello-delta/ reference token profile (not proof of utility)
Tier‑3 — —

No comments to display

Back to top