Data covers ERC-8004 agent registrations and Agent Trust Score assessments. Week 31 = week ending Sunday, August 2, 2026.

Week 31 looked stable at first glance – 21,378 new agents registered, only 7.0% below Week 30’s 22,989. But the number of unique owner wallets behind those registrations collapsed, down 58.7% to just 8,413. The gap between those two numbers tells the real story: registrations concentrated sharply into fewer hands this week. Median trust score also fell further, down 33.1% to 200 – the floor of the Elevated Risk tier, and a value historically associated with farm-flagged registration batches.

Week 31 Key Numbers

Week 31 Analysis

Registrations Held Steady – But Unique Owners Collapsed

Taken on its own, a 7.0% drop in registrations would read as an unremarkable, quiet week. It is the unique owner count that changes the picture entirely: only 8,413 distinct wallets registered agents in Week 31, down from 20,355 in Week 30 – a 58.7% collapse. Registrations fell only slightly while the number of participants fell by more than half, which can only mean one thing: the wallets that did register this week each registered far more agents, on average, than in the prior week.

Agents Per Owner More Than Doubles

Dividing registrations by unique owners gives a rough measure of how concentrated a week’s activity is. In Week 30, that ratio was about 1.13 agents per owner – consistent with most owners registering a single agent, broad-based growth. In Week 31, the same ratio jumped to about 2.54 agents per owner – more than double. This is a marked shift from the pattern described in last week’s tracker, where owner growth closely tracked registration growth. This week, a smaller set of wallets accounts for a similar volume of registrations, which is the signature of batch or fleet-style registration activity rather than broad, independent participation.

Median Trust Hits the Tier Floor

Median trust score fell again, down 33.1% to exactly 200 – the lowest boundary of the Elevated Risk tier, one step above Untrusted. This is not a new value in the tracker’s history: several earlier weeks – W07, W09, W13, W21, and W22 – also recorded a median of exactly 200, and those weeks were consistent with cohorts dominated by low-history or farm-flagged registrations rather than organically diverse agent deployments. Combined with this week’s collapse in unique owners, Week 31 fits that same pattern: a smaller number of wallets registering agents in bulk, with a trust profile that reflects it.

Three Weeks, Three Different Stories

The past three weeks illustrate how differently a similar registration number can behave under the surface. Week 29 saw registrations fall sharply alongside owners, in step with each other. Week 30 saw registrations more than double alongside a nearly equal rise in unique owners – broad-based growth with declining trust. Week 31 saw registrations hold roughly steady while unique owners collapsed – concentrated growth with trust at the tier floor. The registration count alone would not have distinguished any of these three weeks from one another; the unique owner metric is what reveals the difference.

Week-on-Week Comparison: W29 – W31

2026 Weekly Registration History – W25 to W31

Note: Median trust score reflects the median Agent Trust Score of agents registered in that specific week, not the cumulative population median. Unique owner wallets counts distinct wallets that registered at least one agent that week; agents per owner is registrations divided by unique owners for that week.

About This Tracker

ChainAware.ai’s weekly ERC-8004 agent tracker monitors new agent registrations on the ERC-8004 Identity Registry, the number of unique owner wallets behind those registrations, and the median Agent Trust Score of each week’s registration cohort. Agent Trust Score is a 0-1000 score combining owner wallet fraud probability, feeder address analysis, farm detection, and criminal record checks – see the full Agent Trust Score methodology for how the model scores agents and their controlling wallets. Data is updated weekly alongside ChainAware’s PancakeSwap/Uniswap rug pull tracker.

The post ERC-8004 Agent Trust Tracker Week 31 2026 – Unique Owners Collapse 58.7% as Registrations Concentrate and Trust Hits Floor first appeared on ChainAware.ai.

Data covers ERC-8004 agent registrations and Agent Trust Score assessments. Week 30 = week ending Sunday, July 26, 2026.

Week 30 saw new ERC-8004 agent registrations more than double. 22,989 new agents registered – up 108.5% from Week 29’s 11,026, the second-highest weekly registration count since tracking began. Unique owner wallets grew at nearly the same pace, up 96.9% to 20,355. But the median trust score of this week’s cohort fell sharply, down 26.4% to 299 – the lowest median trust score recorded since Week 20, and low enough to drop out of the Provisional tier into Elevated Risk.

Week 30 Key Numbers

Week 30 Analysis

Registrations More Than Double

22,989 new agents registered in Week 30, more than double Week 29’s 11,026. This is the second-highest weekly registration count recorded since tracking began, behind only Week 27’s 29,577. Registration volume has now swung sharply for three straight weeks: down 54.9% in Week 29, then up 108.5% in Week 30 – a reminder that weekly registration counts remain highly volatile rather than settling into a stable trend.

Introducing Unique Owners: How Spread Out Is This Week’s Growth?

Starting this week, the tracker also reports unique owner wallets – the number of distinct wallets that registered at least one agent that week. This matters because a large registration number can mean two very different things: it could reflect many different people or teams each registering an agent, or it could reflect a small number of wallets registering large batches of agents at once.

In Week 30, 20,355 unique wallets registered 22,989 agents – an average of about 1.13 agents per owner. In other words, most owners this week registered only a single agent, rather than large batches. Owner wallet growth (+96.9%) closely tracked registration growth (+108.5%), which means the doubling in registrations came from a broad increase in the number of distinct wallets participating, not from a small number of wallets registering many agents each. This is a meaningfully different picture than a scenario where the doubling was driven by one or two operators mass-registering fleets.

Median Trust Score Falls to Its Lowest Since Week 20

Despite registrations being broad-based rather than concentrated in a few wallets, the median trust score of Week 30’s cohort still fell sharply, down 26.4% to 299 – moving out of the Provisional tier (400-599) that the past three weeks had occupied, and into the Elevated Risk tier (200-399). This is the lowest median trust score recorded since Week 20’s 291, and one of the lower readings in the tracker’s history overall. A broad base of new owner wallets does not automatically mean a trustworthy one – many of this week’s registering wallets appear to be new or thin on established on-chain history, which is one of the signals the Agent Trust Score model weighs when assigning a score.

Week-on-Week Comparison: W28 – W30

2026 Weekly Registration History – W24 to W30

Note: Median trust score reflects the median Agent Trust Score of agents registered in that specific week, not the cumulative population median. Unique owner wallets counts distinct wallets that registered at least one agent that week.

About This Tracker

ChainAware.ai’s weekly ERC-8004 agent tracker monitors new agent registrations on the ERC-8004 Identity Registry, the number of unique owner wallets behind those registrations, and the median Agent Trust Score of each week’s registration cohort. Agent Trust Score is a 0-1000 score combining owner wallet fraud probability, feeder address analysis, farm detection, and criminal record checks – see the full Agent Trust Score methodology for how the model scores agents and their controlling wallets. Data is updated weekly alongside ChainAware’s PancakeSwap/Uniswap rug pull tracker.

The post ERC-8004 Agent Trust Tracker Week 30 2026 – Registrations More Than Double to 22,989 as Median Trust Falls to Elevated Risk first appeared on ChainAware.ai.

Source data in this piece comes from “Paper Agents, Paper Gains: An Empirical Analysis of DeFi Investment Agents” (arXiv:2605.29174, May 2026), authored by researchers affiliated with Pantera Capital, Stanford University, IC3, and Ava Labs.

The industry’s own numbers just confirmed the problem Agent Trust Score exists to solve

For the last two years, “AI agent” has been one of the most valuable labels a crypto project could attach to itself. Combined AI-agent token valuations peaked above $3 billion in early 2025, built on a simple pitch: autonomous, on-chain trading systems that manage pooled capital better than a human could.

A new academic study puts real numbers behind that pitch for the first time, and the numbers are not kind. Researchers surveyed over 1,900 AI-tagged crypto projects, narrowed the field to 1,035 that actually function as DeFi investment agents, and then ran a deep architectural analysis of the two dominant frameworks in the space, ElizaOS and Virtuals Protocol, alongside a quantitative performance study of 11 Solana-based agent treasuries covering 925,323 token holders.

The core finding is not that these agents are unprofitable. It is that almost nobody, including the researchers themselves, can actually verify what these agents are doing, which is exactly the gap ChainAware’s Agent Trust Score was built to close.

The scale of the survey is worth sitting with for a moment. The combined dataset pulled from CoinGecko and Messari covered 1,900 projects with recorded token market capitalizations and 182 venture-funded entities totaling $1.87 billion across 229 funding rounds. After applying strict inclusion criteria, filtering out infrastructure plays, data and oracle layers, and traditional robo-advisors that merely touch digital assets, 1,035 projects remained classifiable as genuine DeFi investment agents. From that pool, the researchers selected 10 projects spanning passive, advisory, and active-trading strategies for deep analysis, and found a pattern: projects funded through public token launches consistently showed higher observability, since the token itself creates an on-chain footprint and community incentive for scrutiny, while projects funded through individual user wallets remained largely opaque by default. Observability, in other words, was mostly a side effect of the fundraising mechanism, not a deliberate design choice toward transparency.

Transparency is not the same thing as verifiability

The study’s most important conclusion has nothing to do with returns. It is a methodological wall the researchers hit while trying to do their job: even among the agents with fully public, on-chain wallet addresses, autonomy could not be confirmed.

Of the 10 representative projects examined in depth, only 3 showed clear evidence of autonomous trade execution. Developer interviews with the ElizaOS and Virtuals Protocol teams suggested that a large share of visible deployments amount to basic API integrations rather than genuine autonomous decision-making. And critically, even the 4 highest-observability projects in the study, ones with public wallet addresses that any outsider could audit, could not be independently confirmed as autonomous versus manually operated. A wallet address shows what transaction happened. It does not show who or what decided to make it.

This is the exact distinction ChainAware has been making publicly about agent trust: a score predicts, a record proves. On-chain data alone gives you the record of execution. It does not give you proof of who or what initiated that execution, and without that proof, “autonomous AI agent” is a marketing claim rather than a verifiable fact.

The framework builders say the same thing

The researchers did not have to speculate about this gap. They interviewed core contributors from both ElizaOS and Virtuals Protocol directly, and both teams independently converged on the same conclusion: trust remains the central barrier to adoption, and current-generation LLM agents cannot trade well without human-supplied insight and domain expertise sitting behind them.

Part of why verification is so difficult comes down to how these frameworks are actually built. ElizaOS runs on a plugin architecture: an LLM receives context from data providers, such as wallet balances or price feeds, selects an action from a registry of over 90 available plugins, including token swaps on Solana or spot trading on Hyperliquid, and an evaluator updates memory afterward. The framework itself is open source, but which plugins a specific deployed agent has enabled is not publicly auditable. Virtuals Protocol works differently, mints each agent as an ERC-6551 token-bound account on Base and routes decision-making through a hierarchical planner that delegates to specialized workers, but plugin and strategy selection is similarly developer-controlled and opaque from the outside. In both cases, the framework gives you a wallet address and a record of what it did. It does not give you a way to confirm that a human did not simply sign each transaction manually.

The Virtuals team pointed to founder-side trading expertise, not the underlying framework, as the actual differentiator between agents that perform and agents that fail. That is a notable admission from the team running a platform that has launched over 17,000 agents: the framework itself is not what makes an agent trustworthy or profitable. Something else has to establish that, and today, nothing systematically does, which is the exact gap our suite of AI agent trust and verification tools is built to close.

What that trust gap costs, in dollars

The paper’s performance analysis puts a number on what happens when trust and verification are absent from a market that is otherwise moving billions of dollars.

At their peak, DeFi investment agent token holders across the 11 platforms studied were sitting on more than $2.4 billion in paper gains. By the study’s latest snapshot, that had collapsed into a collective loss of $191.7 million across 925,323 wallets. Only two of the eleven platforms studied still showed positive aggregate user returns.

The distribution of who actually profited is sharply skewed. Across all platforms, the top 1 percent of profitable wallets, just 2,590 out of 259,016 winners, captured 81.4 percent of all gains, or $1.81 billion. The remaining 62.2 percent of participants realized losses. Median returns were negative or effectively zero on every single platform studied, meaning the typical participant in a typical agent token lost money regardless of which platform they chose.

Token price action tells a similar story. Agent tokens declined 93 percent on average from their all-time highs, nearly double the 54 percent peak-to-trough drawdown of a simple SOL buy-and-hold position over the same window. Meanwhile, market-cap-to-AUM ratios for these agent platforms exceeded 10,000x at points, compared to a ratio below 1x for established DeFi protocols like Aave, Curve, and Uniswap. The researchers read this gap as evidence that valuations were being driven by narrative around AI capability rather than by what the treasuries actually held or earned.

The authors are careful to note this is a descriptive finding, not an accusation. They are not arguing these platforms were built to extract value from later entrants. But they do note the resulting payoff structure, early participants capturing outsized gains while the majority of later entrants lose money, resembles the distributional pattern documented in prior research on Ponzi and pyramid schemes in blockchain contexts. The mechanism is different. The shape of who wins and who loses is not.

There is also a timing pattern in the data that reinforces how disconnected these valuations were from underlying agent activity. Market capitalizations across nearly every platform peaked within the same narrow window, late 2024 into early 2025, which points to a shared narrative cycle driving prices rather than individual project fundamentals or trading performance. More tellingly, peak assets under management in agent treasuries tended to arrive after each token’s all-time high, sometimes by weeks, with Virtuals-based agents showing the longest lag. Capital flowed into these treasuries only after the speculative peak had already passed, a reflexive pattern where narrative drove price first and fresh capital followed the narrative rather than the other way around. Treasury and portfolio composition tell a related story: essentially every agent studied held at least one position under $10 million in market cap among its top holdings, a sharp contrast to established DAO treasuries such as Uniswap, Aave, and Arbitrum, whose largest positions all exceed $50 million. Agent treasuries were concentrated in the same small-cap, high-volatility tokens driving the broader speculative cycle, not diversified away from it.

A maturity framework that maps directly onto what Agent Trust Score already does

Rather than stopping at diagnosis, the researchers propose three criteria for what a mature, production-grade DeFi investment agent would need to satisfy:

• Verifiable autonomous execution: observers should be able to determine whether a transaction was initiated by declared agent logic, a human operator, or some other off-chain process, not just that a transaction occurred.
• Sustained risk-adjusted performance: returns benchmarked against passive alternatives across multiple market regimes, not a single favorable cycle.
• Transparent stakeholder alignment: a clear, explicit relationship between what an agent earns, what a treasury retains, and what actually flows back to token holders.

The first criterion is where ChainAware’s Agent Trust Score already operates today. Rather than taking a public wallet address at face value, the score evaluates both the agent wallet and the wallet funding it, the feeder, since a clean-looking deployment wallet funded from a compromised or unknown source is exactly the kind of gap a naive audit would miss. This is a distinct problem from identity verification or social-graph trust, which is why it sits alongside, not in place of, the other layers covered in our five-category breakdown of Web3 trust verification systems. Trust delegation lets an established, well-behaved owner wallet extend a credibility floor to a fresh agent wallet it controls, while a fraud-flagged or unknown feeder drags the score down regardless of how new or old the agent wallet itself is. None of this requires exposing the underlying identity behind either wallet. It requires only that the behavioral signals feeding the score are real, checkable, and resistant to the kind of surface-level gaming a purely public wallet address invites, a distinction we unpack further in our comparison of Web3 reputation scoring approaches.

Put simply: the paper’s Criterion 1 asks the market to stop treating “public wallet address” as a proxy for “verifiable autonomy.” Agent Trust Score was built around that same premise before this paper existed to confirm it, which is precisely why an independent, Pantera-affiliated academic study arriving at the same conclusion matters. It is not ChainAware making the case for itself. It is the market’s own data making it.

Check before you trust an agent, not after

The $191.7 million in aggregate losses documented in this study did not happen because retail participants were reckless. It happened because there was no reliable, independent way to check whether the agent or the wallet behind it deserved trust in the first place, until after the fact, when the paper gains had already turned into real losses.

None of the three maturity criteria the researchers propose are solved by a bigger treasury, a louder narrative, or a longer track record on Crypto Twitter. They are solved by making the thing that actually matters, whether this agent and its owner have earned trust, checkable before capital moves rather than after it disappears.

The post How Should Investors Evaluate AI Trading Agents? A New Study Has Answers first appeared on ChainAware.ai.

Data covers ERC-8004 agent registrations and Agent Trust Score assessments. Week 29 = week ending Sunday, July 19, 2026.

Week 29 brought a sharp pullback in new ERC-8004 agent registrations after two unusually active weeks. 11,026 new agents registered – a 54.9% decline from Week 28’s 24,458 and the lowest weekly registration count since Week 24. The median trust score of this week’s registration cohort also fell, down 12.5% to 406, placing the typical new agent squarely in the Provisional tier. ChainAware now has 317,589 agents indexed across the ERC-8004 Identity Registry.

Week 29 Key Numbers

Week 29 Analysis

A Sharp Reversion After Two Elevated Weeks

Weeks 27 and 28 were the two highest registration weeks since tracking began – 29,577 and 24,458 new agents respectively, well above the roughly 6,000-19,000 range that characterized most weeks from W16 through W26. Week 29’s 11,026 registrations mark a return closer to that longer-run baseline rather than a continuation of the W27-W28 surge. Whether that surge reflected a genuine wave of new agent deployment or a temporary registration campaign by a smaller number of operators is not yet clear from registration counts alone – the trust score data below offers a partial answer.

Median Trust Score Also Declined

Unlike a simple reversion where volume falls but quality holds steady, Week 29’s median trust score of 406 is also down from 464 in Week 28 and 432 in Week 27 – a 12.5% week-on-week decline. All three of the most recent weeks sit in the Provisional tier (400-599), but Week 29 is the weakest of the three. This differs from Week 26, where median trust reached 644 (Trusted tier) alongside a comparatively modest 13,816 registrations – the highest median trust score recorded since tracking began.

The historical range for median weekly trust is wide: from a low of 105 in Week 8 up to 644 in Week 26. Several weeks – W07, W09, W13, W21, and W22 – recorded a median of exactly 200, the floor of the Elevated Risk tier, which is consistent with cohorts dominated by low-history or farm-flagged registrations rather than organically diverse agent deployments.

Most Agents Score Either Very Low or Very High

Weekly registration counts and median scores describe the flow of new agents. A separate, and arguably more important, picture is how trust scores are spread across all 317,589 agents currently indexed. In a healthy, evenly-distributed population, most agents would land somewhere in the middle of the scale. That is not what the data shows. Instead, agents tend to fall into one of two groups: a large cluster with very low scores, and a large cluster with very high scores – with comparatively few agents sitting in between.

On the low end, 27.5% of all indexed agents fall into the Untrusted tier – and within that group, 70,435 agents (22.2% of the entire population) score below 100, the single largest group in the whole dataset. These are typically agents flagged for suspicious patterns: fleets of agents registered together, or agents whose controlling wallet has a history of fraud.

On the high end, 21.3% of agents score in the Sovereign tier – the highest trust level ChainAware assigns – with the very top scoring band (900-1000) alone holding 42,749 agents (13.5%), the second-largest group in the dataset. These are typically agents backed by an owner wallet with a long, clean, well-established on-chain history.

In between these two extremes, the three middle tiers – Elevated Risk, Provisional, and Trusted – are each individually smaller than either the bottom or the top group, even though together they cover a much wider range of scores. In other words: it is more common for an agent to be clearly low-trust or clearly high-trust than to be somewhere in the middle.

This pattern lines up with how ChainAware’s Agent Trust Score is designed to work. Several of the checks behind the score apply sharp penalties rather than gradual ones: agents registered in large batches at the same time are flagged as likely fleets and pushed toward the bottom of the scale, and a confirmed history of fraud in an agent’s ownership chain caps the score outright, regardless of anything else. On the other end, an agent backed by an owner with an established, trustworthy track record is lifted quickly toward the top of the scale. Few agents end up stuck in the middle, because the scoring logic is built to sort agents into clear categories rather than spread them out evenly. For the full scoring methodology behind these tier boundaries, see the Agent Trust Score methodology page.

Week-on-Week Comparison: W27 – W29

2026 Weekly Registration History – W23 to W29

Note: Median trust score reflects the median Agent Trust Score of agents registered in that specific week, not the cumulative population median. Total agents indexed (317,589) reflects the full registry snapshot as of Week 29.

About This Tracker

ChainAware.ai’s weekly ERC-8004 agent tracker monitors new agent registrations on the ERC-8004 Identity Registry and the median Agent Trust Score of each week’s registration cohort. Agent Trust Score is a 0-1000 score combining owner wallet fraud probability, feeder address analysis, farm detection, and criminal record checks – see the full Agent Trust Score methodology for how the model scores agents and their controlling wallets. Data is updated weekly alongside ChainAware’s PancakeSwap/Uniswap rug pull tracker.

The post ERC-8004 Agent Trust Tracker Week 29 2026 – Registrations Fall 54.9% as Most Agents Score Either Very Low or Very High first appeared on ChainAware.ai.

ChainAware has indexed 274,792 ERC-8004 agents across Ethereum, BSC, Base, and Avalanche. The data reveals a striking picture of the current agent ecosystem: 26% of indexed agents score Untrusted, 21.1% are flagged as farm-detected Sybil operations, and only 21.1% reach the Sovereign tier. More than half of all registered ERC-8004 agents carry material trust risk — and until today, no infrastructure existed to surface that risk before an interaction.

The Problem Agent Trust Score Solves

Agentic commerce — where AI agents execute transactions autonomously on behalf of users — is accelerating rapidly. McKinsey estimates AI agents could mediate $3-5 trillion in global commerce by 2030 . Today, 68% of new DeFi protocols launched in Q1 2026 include at least one autonomous AI agent. Every one of those agents initiates transactions without human approval — and every one of those transactions is a trust decision that previously had no infrastructure layer behind it.

The ERC-8004 Identity Registry tells you an agent exists. It does not tell you whether to trust it. Voting-based reputation systems can be gamed in hours — an operator deploying 50 agent wallets can manufacture a full review history at near-zero cost. ChainAware’s Agent Trust Score bypasses the reputation layer entirely and scores the human controlling the agent: their on-chain behavioral history, who funded their wallet, and whether they have previously created rug pull pools or honeypot tokens.

What the Data Shows

Additional signals: 21.1% carry the FARM_DETECTED flag, 9.5% have unknown feeder addresses, 7.6% use EIP-7702 delegated ownership, and 741 agents have confirmed rug pull history in their feeder chain.

CB Insights Validation

The launch follows ChainAware’s inclusion in the CB Insights AI Fraud Prevention Market Map , placing ChainAware in the On-Chain Intelligence category alongside Chainalysis, Elliptic, and TRM Labs. Read the full analysis in our CB Insights market map coverage.

Co-Founder Statement

“We indexed 274,792 ERC-8004 agents and found that more than half score either Untrusted or Elevated Risk. The agentic economy is being built on top of a registry that has no trust infrastructure. Agent Trust Score is the infrastructure that closes that gap.” — Martin Ploom, Co-Founder, ChainAware.ai

Integration

The Agent Trust Score API returns a 0-1000 score, tier, and flag set for any indexed ERC-8004 agent in under 100ms. It integrates natively with ChainAware’s Prediction MCP server. Enterprise rate limits, SLA, and webhook notifications are available on request.

For the full technical breakdown, integration guide, and ERC-8004 ecosystem data analysis, read the deep-dive: Agent Trust Score: On-Chain Trust Scoring for the Agentic Commerce Era →

ChainAware.ai is the Web3 Agentic Growth Infrastructure — 20M+ wallet personas, 98% fraud detection accuracy, <100ms API latency. Named in CB Insights’ AI Fraud Prevention Market Map. chainaware.ai

The post ChainAware Launches Agent Trust Score — On-Chain Trust Scoring for the Agentic Commerce Era first appeared on ChainAware.ai.

Something fundamental is changing in how commerce works. AI agents — software systems that can perceive, decide, and act autonomously — are beginning to transact. They are paying for APIs, settling invoices, executing DeFi strategies, managing DAO treasuries, and interacting with financial infrastructure in ways that traditional systems were never designed to handle. McKinsey estimates AI agents could mediate $3-5 trillion in global commerce by 2030 . Today, 68% of new DeFi protocols launched in Q1 2026 already include at least one autonomous AI agent.

Every one of those agents initiates transactions without human approval. Furthermore, every one of those transactions is a trust decision — a question of whether the agent on the other side of the interaction is controlled by a legitimate operator, or by someone whose on-chain history includes rug pulls, honeypot tokens, mixer exposure, and Sybil farming at scale. Until today, no infrastructure existed to answer that question. ChainAware’s Agent Trust Score is that infrastructure.

Read the launch announcement: ChainAware Launches Agent Trust Score — Official Announcement →

Table of Contents

1. The Agentic Commerce Era: Why Trust Is the Missing Layer
2. The Agentic Commerce Trust Stack: Where Agent Trust Score Fits
3. CB Insights Validation: ChainAware in the AI Fraud Prevention Market Map
4. What ERC-8004 Gives You — and What It Doesn’t
5. State of the ERC-8004 Registry: Trust Analysis of 274,792 Agents
6. The Five Signals Only ChainAware Provides
7. The Data Moat: Why This Cannot Be Replicated
8. How the Agent Trust Score Works
9. Score Tiers: What Each One Means
10. The Compounding Risk of Unscreened Agent Access
11. Integration Guide for DeFi Protocol Builders
12. Guide for Agent Creators: How Your Score Is Determined
13. How Agent Trust Score Compares to Other Platforms
14. Frequently Asked Questions

The Agentic Commerce Era: Why Trust Is the Missing Layer

Agentic commerce is not a future scenario — it is happening now, across every DeFi protocol that accepts agent-initiated transactions. Consequently, DeFi protocol builders face an immediate and urgent problem: how do you trust an agent you have never met, whose controlling wallet was created last week, whose funding source you cannot trace, and whose operator may have a history of financial fraud under a different wallet identity?

The scale of the shift is concrete. Morgan Stanley projects that nearly half of all online shoppers will use AI shopping agents by 2030 , accounting for approximately 25% of their total spending. In Web3 specifically, the transition is even faster — agents are moving from advisory roles (suggesting trades) to execution roles (completing them). The distinction between advice and execution is the distinction between a bad recommendation and an empty wallet.

Three converging forces are accelerating this shift in Web3. First, ERC-8004 went live on Ethereum mainnet in January 2026, giving AI agents a standardized on-chain identity for the first time. Second, x402 — the open payment protocol championed by Coinbase, Google Cloud, and Circle — provides agents with stablecoin-native payment rails, enabling micropayments without human login flows. Third, trust infrastructure has lagged behind. As Google Cloud’s Global Head of Strategy for Web3 stated at Consensus 2026: “The biggest friction points center on the fact that most products are still built for humans, not agents.” Agent Trust Score is ChainAware’s response to that friction at the trust layer specifically.

For a deep dive into the commercial context, see our article on why the first step in agentic commerce is trust, not integration.

The Know Your Agent (KYA) Imperative

Know Your Agent — KYA — is emerging as the agent-layer equivalent of KYC. Unlike KYC, however, KYA for Web3 is necessarily on-chain behavioral rather than documentary. There are no passports in DeFi. Instead, there is transaction history — permanent, public, immutable, and available for scoring without touching any personal data. KYA answers the same fundamental question KYC does — who is this entity, should I trust them? — using behavioral pattern analysis across 20M+ wallet personas trained on confirmed fraud and legitimate address populations.

The regulatory tailwind is real. The EU AI Act , which takes full effect in August 2026, creates documentation and risk assessment requirements for high-risk AI systems. Autonomous agents with financial execution permissions are a clear candidate for high-risk classification. Protocols operating in EU-regulated markets need demonstrable risk controls for agent interactions — Agent Trust Score satisfies that requirement without adding friction for legitimate agents.

The Agentic Commerce Trust Stack: Where Agent Trust Score Fits

The agentic economy has built four of its five required infrastructure layers. The fifth — trust — launched today. Understanding where Agent Trust Score sits in the full stack clarifies both what it does and why no existing protocol addresses the same problem.

This framework — which we call the Agentic Commerce Trust Stack — maps the four distinct problems any agentic commerce protocol must solve before autonomous transactions can happen safely. Each layer answers a different question. Moreover, each layer requires different infrastructure. x402 handles payment rails. ERC-8183 handles disputes after transactions complete. ERC-8004 handles identity registration. Agent Trust Score handles the question that must be answered before any interaction begins: is this agent controlled by someone whose on-chain history warrants the trust implied by autonomous execution?

The stack is not theoretical. Mastercard completed Europe’s first live AI-agent bank payment in 2026. Visa launched an agent-focused payment framework. TON Foundation launched Agentic Wallets in April 2026, allowing AI agents on Telegram to autonomously store and spend funds within user-defined limits. The payment rails are live. The dispute layer is being built. The identity layer has 274,792 registered agents. The trust layer — until today — was the missing piece.

CB Insights Validation: ChainAware in the AI Fraud Prevention Market Map

Context matters for a product launch in a nascent category. ChainAware’s inclusion in the CB Insights AI Fraud Prevention Market Map provides that context clearly. CB Insights mapped 200+ of the most promising companies building AI-powered fraud prevention infrastructure, from deepfake detection to on-chain intelligence and — their exact words — “agentic trust infrastructure.” ChainAware appears in the On-Chain Intelligence category alongside Chainalysis, Elliptic, and TRM Labs.

The CB Insights placement is significant for three reasons. First, it validates the methodology — CB Insights uses Mosaic scores and predictive signals, not self-reported data, to select companies. Second, it identifies “agentic trust infrastructure” as a standalone market segment within fraud prevention — confirming that Agent Trust Score addresses a recognized institutional need, not a speculative niche. Third, it positions ChainAware as the Web3-native player in a category otherwise dominated by forensic analytics firms whose methodology is reactive rather than predictive.

For the full analysis of what the CB Insights placement means for ChainAware’s market position, see our CB Insights market map coverage article. For the competitive landscape of agent trust platforms specifically, see our Agent Trust Infrastructure Race analysis comparing six platforms across 19 capabilities.

What ERC-8004 Gives You — and What It Doesn’t

ERC-8004 is a well-designed standard that solves a specific problem: giving AI agents a standardized, verifiable on-chain identity. Every registered agent receives an ERC-721 NFT representing its identity, a controlling owner wallet, an agent payment wallet, and a URI pointing to its agent card JSON. The registry answers the question “does this agent exist?” cleanly and cryptographically.

The standard does not answer the question “should I trust this agent?” — and the specification explicitly leaves scoring to third parties. This design choice is correct architecturally: the registry should be a neutral data layer, not an opinion engine. However, it means that every protocol integrating ERC-8004 agents is responsible for answering the trust question independently. Most currently do not — they query the registry to confirm the agent exists and proceed. Agent Trust Score is what fills the gap between “agent exists” and “agent is safe to interact with autonomously.”

The Voting-Based Reputation Problem

ERC-8004 also includes a built-in Reputation Registry — a standard interface for peer feedback. On paper, this sounds like a trust mechanism. In practice, it is a manufactured-trust system waiting to be exploited. An operator deploying 50 agent wallets can have each one review every other, generating a full positive reputation history in hours at a cost measured in gas fees. On BSC or Base, that cost is less than a dollar. The result is indistinguishable from genuine reputation on any platform that reads the registry naively.

ChainAware does not read the ERC-8004 Reputation Registry to compute the Agent Trust Score. Instead, we look behind the agent at the behavioral history of the wallets controlling it and funding its controller. That history is immutable — it cannot be manufactured overnight. An operator who rugged three liquidity pools in Q4 2025 and registered 47 agents in Q1 2026 carries that history forward regardless of how many peer reviews the new agents accumulate. For a detailed analysis of why voting-based reputation fails at scale, see our guide to Web3 Wallet Auditing Providers in 2026.

State of the ERC-8004 Registry: First Ever Trust Analysis of 274,792 Agents

ChainAware has indexed the complete ERC-8004 registry — 274,792 agents across Ethereum mainnet, BSC, Base, and Avalanche — and applied the Agent Trust Score to produce the first comprehensive behavioral trust analysis of the agentic economy. The results reveal a striking picture that should concern any DeFi protocol granting autonomous execution access to registry agents.

Trust Score Distribution

The headline finding is stark: more than half of all ERC-8004 registered agents — 51.8% — carry Elevated Risk or Untrusted scores. This is not a marginal tail of bad actors. It is the majority of the registry. Protocols granting autonomous execution access to unscreened ERC-8004 agents are, statistically, granting that access to a population where more than half present material trust risk.

Flag Analysis: What Is Driving Low Scores

• FARM_DETECTED: 58,061 agents (21.1%) — one in five agents belongs to a Sybil fleet where a single operator controls multiple agents
• FEEDER_UNKNOWN: 26,124 agents (9.5%) — nearly 1 in 10 agents has an owner wallet with an obfuscated or untraceable funding source
• EIP7702_DELEGATED: 20,946 agents (7.6%) — the registered owner has delegated control to a secondary address, potentially obscuring the real controller
• FEEDER_CEX_VERIFIED: 2,691 agents (1.0%) — confirmed CEX-funded owners, the strongest legitimacy signal available
• FEEDER_RUG_HISTORY: 741 agents (0.3%) — agents whose owner wallet was funded by a confirmed rug pull operator
• CREATOR_RUG_HISTORY: 59 agents (0.02%) — agents controlled directly by confirmed rug pull creators
• CREATOR_HONEYPOT_HISTORY: 3 agents — agents whose owner has previously created honeypot token contracts

The farm detection finding deserves particular attention. 58,061 agents — 21.1% of the entire registry — are controlled by fleet operators running multiple agents simultaneously, frequently registered in the same block. Individual agent scoring is structurally blind to this pattern. ChainAware detects it because we maintain an owner profile database tracking fleet size across all indexed chains — a capability that requires the full registry index, not just individual agent lookups.

For the full competitive context of how these signals compare to what RNWY, SkyeProfile, AXIS T-Score, and DJD Agent Score provide, see our Agent Trust Infrastructure Race analysis.

The Five Signals Only ChainAware Provides

Agent Trust Score combines signals that no other agent trust platform currently provides. Each one addresses a specific threat model that the other approaches structurally cannot reach. We intentionally do not publish the exact weights, thresholds, or model coefficients behind these signals — doing so would allow bad actors to calibrate their behavior to stay just below each detection threshold. What we do publish are the signal categories and what each one means for your trust decision.

Signal 1: Owner Wallet Behavioral Fraud Score

The owner wallet is the human or entity controlling the agent. ChainAware scores it using a predictive AI model trained on 20M+ wallet personas across Ethereum, BSC, Base, and beyond — achieving 98% fraud detection accuracy. This is not a blacklist check. Rather, it is a forward-looking behavioral prediction: given this wallet’s complete transaction history, what is the probability it will engage in fraudulent activity? The model retrains continuously on new confirmed fraud cases, meaning evasion strategies become stale quickly.

The fraud score is the primary input to the Agent Trust Score — a clean wallet starts at a high baseline, while a fraud-flagged wallet scores low regardless of any other signal. For the full methodology behind the fraud prediction model, see our AI-Powered Blockchain Analysis guide.

Signal 2: Feeder Address Analysis

The feeder address is the wallet that funded the owner. No other agent trust platform traces and scores this signal. ChainAware traces feeder addresses for approximately 38% of indexed agents. The feeder signal has three variants that carry different trust implications. A CEX-verified feeder (Binance, Coinbase, Kraken, OKX withdrawal address) implies the owner passed KYC somewhere upstream — ChainAware’s strongest positive signal. An unknown or obfuscated feeder is itself a risk signal. A feeder with confirmed fraud status applies hard suppression to the final score.

When the feeder address has rug pull or honeypot history in ChainAware’s database, the owner may have deliberately cycled wallets to obscure a fraud track record — the feeder criminal record check is what catches this pattern. For more on how feeder analysis works in practice, see our Forensic vs AI Blockchain Analysis guide.

Signal 3: Criminal Record — Rug Pull and Honeypot History

ChainAware maintains a database built from on-chain liquidity pair history and token audit data spanning over a year of activity. This database records which wallet addresses created pools that subsequently exhibited rug pull patterns, and which wallet addresses previously deployed honeypot token contracts. Before computing the Agent Trust Score, ChainAware cross-references both the owner wallet and the feeder address against this database.

Criminal record signals result in hard caps on the Agent Trust Score that no other signal can override. This is the signal that connects yesterday’s token fraud to today’s agent deployment. An operator who rugged pools on PancakeSwap in Q4 2025 and registered 40 agents in Q1 2026 is caught by this check. No other agent trust platform makes that connection because no other platform maintains a paired rug pull database and cross-references it against agent registry data. For background on how rug pull and honeypot patterns are detected, see our guide to Rug Pull vs Pump and Dump in Web3.

Signal 4: Trust Delegation

Agent payment wallets are frequently fresh addresses created specifically for the agent — they have no transaction history, no counterparty network, and no behavioral record. A naive scoring approach penalises every newly deployed agent regardless of the owner’s reputation, producing low scores for legitimate agents and making the score useless as a gate for new deployments.

ChainAware’s trust delegation mechanism solves this: the owner wallet’s reputation sets a floor for the agent wallet’s effective score. A reputable developer deploying their first agent wallet scores well through delegation. A fraud-flagged owner cannot delegate any meaningful trust — the delegation collapses, and the agent score reflects the owner’s history rather than the wallet’s lack of it.

Signal 5: Fleet-Level Farm Detection

Every competitor in this market scores agents individually. ChainAware maintains an owner profile database tracking agent fleet size across all indexed chains. Owners controlling unusually large numbers of agents — particularly those registered in tight time windows — receive farm modifiers that suppress scores across their entire fleet, regardless of how any individual agent scores in isolation.

This fleet-level view catches the specific agentic commerce attack pattern that individual scoring cannot surface: one operator manufacturing ecosystem depth through a controlled population of agents, each of which appears clean when scored independently. Our data shows 58,061 agents — 21.1% of the entire ERC-8004 registry — are already in this category today.

The Data Moat: Why This Cannot Be Replicated

Agent Trust Score is built on three proprietary data assets accumulated over years of continuous operation. A competitor starting today cannot purchase these assets, compress the time required to build them, or replicate them from publicly available sources alone. Each one compounds in value as it grows — making ChainAware’s intelligence advantage wider over time, not narrower.

20M+ Wallet Personas: Years of Behavioral Training Data

ChainAware’s fraud prediction model is trained on more than 20 million wallet personas across 8 blockchains. Each persona represents a complete behavioral fingerprint — transaction history, timing patterns, counterparty networks, protocol diversity, AML exposure, and dozens of derived features. Building this dataset required years of continuous on-chain data collection, labeling of confirmed fraud cases, and iterative model retraining against real-world fraud outcomes. The result is 98% fraud detection accuracy on held-out test data.

This persona depth cannot be replicated quickly. A new entrant would need years of historical blockchain data, a confirmed fraud label dataset from real fraud cases, and the engineering infrastructure to process and update 20 million behavioral profiles continuously. Furthermore, the model improves as the dataset grows — each new confirmed fraud case sharpens the prediction boundary. ChainAware’s advantage in this dimension compounds daily.

One Year of On-Chain Pair History: The Criminal Record Database

The rug pull and honeypot criminal record check that powers Agent Trust Score’s hardest caps requires a database of historical liquidity pair creation and token audit results — accumulated over more than a year of continuous on-chain monitoring. ChainAware has tracked pair creation across PancakeSwap, Uniswap, and other major DEX venues, cross-referencing creator wallet addresses against confirmed fraud outcomes: pools where liquidity was removed in rug pull patterns, and token contracts that embedded honeypot mechanics preventing buyers from selling.

This database is what catches the serial fraudster who registers new agents after previous fraud campaigns. It connects the rug puller of November 2025 to the agent creator of February 2026 — a connection that exists only if you have the historical data linking both events to the same wallet address. No competitor in the agent trust scoring market currently maintains this database. Furthermore, building it retroactively is impossible: the historical pair data exists on-chain, but the labeling of fraud outcomes requires the passage of time to observe liquidity removal patterns after the fact. For the data behind this detection engine, see our Rug Pull Tracker report and our AI-Based Predictive Fraud Detection guide.

38% Feeder Coverage: The Funding Chain Network

ChainAware traces feeder addresses — the wallets that funded owner wallets — for approximately 38% of indexed ERC-8004 agents. This coverage reflects the on-chain reality: some owner wallets receive funds from multiple sources, some from bridge or faucet infrastructure that does not produce a single attributable feeder, and some from deliberately obfuscated multi-hop paths. The 38% with traceable single-hop feeders represents the population where the funding chain reveals meaningful intelligence.

Feeder coverage is itself a compounding asset. As ChainAware indexes more agents and more wallet interactions over time, the feeder network graph grows denser — revealing connections between previously unlinked wallet clusters. An operator who cycled through three funding wallets across different campaigns may appear disconnected today but becomes linkable as the transaction graph accumulates more data points. Additionally, the CEX label database — identifying which addresses are verified exchange hot wallets — improves as exchange infrastructure evolves and new verified addresses are confirmed. The feeder signal is the one no competitor has reached because building it requires both the feeder tracing infrastructure and the fraud intelligence to score what you find at the other end of the funding chain.

Why the Moat Compounds

Each of these three data assets improves as it grows larger and older. More wallet personas means better fraud prediction boundary precision. More pair history means more confirmed criminal records attached to operator wallets. More feeder coverage means more fraud connections surfaced across the registry. A competitor starting today with identical engineering resources would still need years to catch up — and by the time they did, ChainAware’s assets would be proportionally larger still. This is the definition of a compounding data moat: the advantage is not a snapshot, it is a trajectory.

How the Agent Trust Score Works

The Agent Trust Score uses a multi-layer pipeline that combines owner fraud probability, trust delegation, feeder analysis, farm detection, and criminal record hard caps into a single 0-1000 score. Each layer applies a specific transformation before passing the result to the next.

We intentionally do not publish the exact weights, thresholds, or multipliers used in each layer. Publishing precise thresholds would allow bad actors to calibrate their behavior to stay just below each detection cap — which would directly undermine the system’s ability to catch sophisticated fraud. Our scoring model retrains continuously on new confirmed fraud patterns. What works as evasion today becomes detectable tomorrow as the model updates.

What we do publish is what each layer measures and why it matters:

• Owner fraud probability — the primary driver of the base score. A clean owner wallet starts at a high baseline. A fraud-flagged wallet scores low regardless of any other input.
• Experience and on-chain history — a modest bonus for owners with genuine DeFi activity over time. Experience adds to the score but cannot compensate for high fraud probability.
• Trust delegation — lifts a fresh agent wallet when the owner has strong history. Collapses when the owner is fraud-flagged.
• Feeder modifier — adjusts the score based on who funded the owner. CEX-verified feeders boost the score. Unknown or fraud feeders suppress it.
• Farm modifier — suppresses scores across an entire fleet when the owner controls an unusually large number of agents or registers them in bulk.
• Criminal record hard caps — override all other signals when confirmed rug pull or honeypot history is found. These caps are absolute and cannot be offset by positive signals elsewhere.

The result is a score between 0 and 1000. The full methodology overview — covering signal categories without exposing exact parameters — is available at chainaware.ai/learn/agent-trust-score.

Score Tiers: What Each One Means for Protocol Builders

The Agent Trust Score maps to five tiers on the 0-1000 scale. Each tier carries a specific operational recommendation for DeFi protocol builders. The right threshold for your protocol depends on the risk profile of the transactions involved — a high-value lending protocol and a low-value DEX swap use different thresholds against the same score.

Sovereign (800-1000) — Full Autonomous Access

Sovereign agents have strong owner fraud probability, a clean or CEX-verified feeder address, no criminal record signals, and no farm detection flags. Sovereign is appropriate for high-value autonomous operations: large-value lending, treasury management, and governance participation with financial consequences. Protocols can grant Sovereign agents the same execution permissions they would grant to established protocol participants.

Trusted (600-799) — Standard Integration

Trusted agents have strong owner fraud probability, a generally clean feeder, and no hard-cap signals. Trusted is appropriate for standard DeFi integrations — trading agents, yield optimisers, and automated compliance workflows where individual transaction risk is moderate and human monitoring is available as a backstop.

Provisional (400-599) — Monitoring Required

Provisional agents show mixed signals: moderate fraud probability, unknown feeder, or a fresh payment wallet. Provisional agents should not receive unsupervised autonomous execution access for high-value operations. However, they are appropriate for lower-risk automated workflows with active monitoring — read-only queries, low-value token swaps, or agentic onboarding flows where individual transaction size is capped.

Elevated Risk (200-399) — Restricted Access Only

Elevated Risk agents carry weak owner history, obfuscated feeders, or farm detection signals. These agents should not be permitted autonomous financial execution. If your protocol needs to serve Elevated Risk agents — for example in a permissionless DEX context — transaction size limits, velocity caps, and real-time monitoring should all be active simultaneously.

Untrusted (0-199) — Block

Untrusted agents carry active fraud signals, confirmed rug pull or honeypot history, confirmed farm detection, sanctioned address exposure, or repeat offender status. These agents should be blocked at the access control layer before any transaction reaches the execution layer. The score is not borderline — it reflects definitive fraud signals from immutable on-chain history. For context on the types of on-chain fraud that produce Untrusted scores, see our AI-Based Predictive Fraud Detection guide.

The Compounding Risk of Unscreened Agent Access

Human-initiated fraud and agent-initiated fraud differ in one fundamental operational characteristic: velocity. A fraudulent human interacting with your protocol manually can execute perhaps dozens of interactions before detection. A fraudulent agent operating autonomously executes thousands of interactions in the same period — at machine speed, without sleep, without rate-limit awareness unless you specifically implement it, and with the full behavioral sophistication of the AI model powering it.

Therefore, the cost of a single misidentified agent is not comparable to the cost of a single misidentified human user. The exposure scales with the agent’s operational capacity. A lending protocol that grants a fraudulent agent autonomous execution access for six hours faces losses that scale with protocol TVL and agent transaction rate. Traditional fraud detection tools are particularly poorly suited to this environment. Rule-based systems flag agent behavior as suspicious because agents naturally exhibit the patterns those rules target: high velocity, cross-category activity, unusual timing distributions. Consequently, you end up blocking legitimate agents while missing sophisticated fraudulent ones engineered to mimic human behavioral patterns.

The Farm Attack at Scale

Agent farming is a specific attack pattern that compounds differently from individual fraud. Consider the operational math: one operator registers a large fleet of agents across BSC and Base, each appearing clean individually. Each agent interacts with your protocol at modest frequency. Collectively, that generates thousands of agent interactions per day from a single coordinated operator. Furthermore, because each agent appears to be an independent participant, your protocol’s per-user rate limits and monitoring thresholds are never triggered on any single agent. Across a week, you may process tens of thousands of transactions from what is effectively a single fraud operation — without any individual agent exceeding your anomaly detection thresholds.

ChainAware’s fleet-level farm detection catches this pattern before the first transaction. When agents from the same owner wallet query the Agent Trust Score API, they return FARM_DETECTED — regardless of how clean any individual agent appears. The trust decision happens at the fleet level, not the individual agent level, because the fraud pattern exists at the fleet level. Our data shows 58,061 agents — 21.1% of the entire ERC-8004 registry — already carry the FARM_DETECTED flag. For the broader context of how predictive models compare to forensic analytics for this class of threat, see our Forensic vs AI analysis guide.

The Serial Fraudster Rotation Pattern

A second compounding risk pattern is the serial fraudster who rotates wallet identities between campaigns. The typical sequence: Wallet A runs a rug pull campaign, extracts funds, and becomes known to forensic databases. Wallet B is then created fresh, funded from Wallet A — the feeder relationship recorded immutably on-chain — and used to register new agents on ERC-8004. Every platform that scores only the agent or the current owner wallet sees a clean Wallet B. ChainAware traces the feeder and scores Wallet A, which carries the rug pull history. Wallet B’s agents receive suppressed scores regardless of how clean Wallet B’s own transaction history appears.

The data confirms this pattern is live in the current registry: 741 agents carry the FEEDER_RUG_HISTORY flag, meaning their owner wallet was funded by a confirmed rug pull operator. These 741 agents appear completely clean to any platform that does not trace the feeder chain. They represent confirmed serial fraudsters using fresh wallets to continue operations under new identities. For the macro picture of rug pull losses, see our Rug Pull Tracker report.

Integration Guide for DeFi Protocol Builders

Adding Agent Trust Score to a DeFi protocol requires one additional step between the ERC-8004 registry lookup and transaction execution. That step takes under 100ms and returns a structured output the protocol’s access control layer can act on directly.

The Trust-Aware Integration Pattern

Agent initiates transaction
  ↓
Resolve agent_id → owner_address + agent_wallet (ERC-8004 registry)
  ↓
GET /erc8004/agent/{chain_id}/{agent_id}/trust-score
  ↓
Response:
{
  "agent_trust_score": 882,
  "tier": "Sovereign",
  "flags": ["FEEDER_CEX_VERIFIED"],
  "scored_at": "2026-07-12T09:14:00Z"
}
  ↓
score ≥ protocol_threshold → execute
score < protocol_threshold → reject or route to human review

The threshold is your decision. Different use cases warrant different risk tolerances:

MCP Integration

Agent Trust Score integrates natively with ChainAware’s Prediction MCP server. Any Claude-based DeFi agent can call agent trust scoring as a native tool call without custom API integration code. For teams building on the MCP stack, our library of 32 ready-made agents includes agent verification logic that can be cloned and deployed in under 30 minutes. For DeFi credit scoring alongside agent trust verification, see our DeFi Credit Score Platform Comparison.

Latency and Rate Limits

Agent Trust Score returns results in under 100ms for pre-indexed agents. ChainAware pre-indexes the full ERC-8004 registry continuously, so the vast majority of queries return cached scores without a live computation cycle. Enterprise plans include dedicated rate limits, SLA guarantees, webhook notifications for score changes, and a dedicated integration engineer. Free tier covers the first 1,000 queries per month with no API key required for public indexed agents. For the AML and MiCA compliance context, see our DeFi Compliance and KYT/AML guide.

Guide for Agent Creators: How Your Score Is Determined

If you are deploying ERC-8004 agents, understanding how your agents are scored enables you to optimize for legitimate trust signals. The score reflects real behavioral history — it cannot be manufactured, but it can be legitimately improved over time through genuine on-chain activity.

What Improves Your Score

The primary lever is your owner wallet’s fraud probability — keeping it low requires genuine, diverse on-chain activity over time. Specifically, interacting with a range of DeFi protocols (lending, trading, staking, bridging) across multiple months produces a behavioral profile that scores well. Additionally, using a CEX withdrawal as your owner wallet’s funding source (Binance, Coinbase, Kraken) immediately flags your agent as FEEDER_CEX_VERIFIED and applies the maximum feeder boost. Furthermore, deploying agents with consistent patterns over time rather than in bulk avoids farm detection signals.

What Permanently Caps Your Score

Criminal record signals are immutable. A confirmed rug pull or honeypot in your on-chain history permanently caps your agents — regardless of how clean your current behavior is. These caps exist because the on-chain events that trigger them are permanent. A wallet that drained a liquidity pool cannot remove that event from the blockchain. Consequently, there is no path to a high Agent Trust Score for operators with confirmed fraud history. For context on how rug pull and honeypot patterns are detected, see our Rug Pull Detector learn page.

How Agent Trust Score Compares to Other Platforms

Agent trust scoring is a new market with several emerging approaches. Each platform answers a different question about the same agent. Understanding the distinction matters for protocol builders choosing a trust gating system — selecting the wrong approach means the specific fraud pattern you face is precisely the one your chosen platform cannot detect.

RNWY is the most established competitor and provides strong review quality analysis and sybil detection. However, their core methodology solves fake reviews — not fake owners. ChainAware solves fake owners. These are complementary approaches: DeFi protocols can use both simultaneously, with RNWY for reputation display and ChainAware as the fraud intelligence gate before execution. For the full 19-capability comparison across all six platforms, see our Agent Trust Infrastructure Race.

Frequently Asked Questions

Which chains does Agent Trust Score cover?

Agent Trust Score indexes ERC-8004 agents across Ethereum mainnet, BSC (BNB Chain), Base, and Avalanche C-Chain, with Mantle in progress. The owner wallet and feeder scoring draws on ChainAware’s broader behavioral intelligence database, which covers 8 blockchains including Polygon, TON, TRON, and HAQQ. Chain coverage expands continuously as new ERC-8004 registry deployments go live.

Does it require any personal data or KYC?

No. Agent Trust Score is derived entirely from public on-chain data. No personal information is collected, no identity verification is required, and no data is stored beyond what is already publicly available on the blockchain. The product is compatible with DeFi’s privacy-first ethos and compliant with GDPR by design.

Can an agent improve its score over time?

Yes — through the owner wallet’s behavioral history, not through the agent wallet itself. As the owner wallet accumulates genuine on-chain experience and maintains a clean fraud probability score, the Agent Trust Score improves. However, criminal record signals are permanent — they do not improve over time because the underlying on-chain events are immutable.

Why don’t you publish the exact scoring weights?

Publishing exact thresholds and weights would allow bad actors to calibrate their behavior to stay just below each detection cap. This is the same reason credit scoring agencies (FICO, Experian) publish the signal categories they use — payment history, credit utilization, account age — without publishing the precise weights. Our fraud model retrains continuously, so even partial knowledge of current parameters becomes stale quickly. The signal categories are published at chainaware.ai/learn/agent-trust-score. The exact parameters remain proprietary.

What happens when an agent is transferred to a new owner?

ERC-8004 agents are ERC-721 NFTs and can be transferred between wallets. When ChainAware detects an ownership transfer, the Agent Trust Score recalculates using the new owner wallet’s behavioral history. The score tracks the current controlling entity, not the original registrant. An agent cannot inherit a previous owner’s strong score after transfer.

How does EIP-7702 delegation affect the score?

When EIP-7702 delegation is detected, ChainAware scores both the registered owner and the delegate address. The Agent Trust Score takes the less favorable of the two results. Agents with EIP-7702 delegation are flagged explicitly in the API response as EIP7702_DELEGATED, giving protocol builders the option to apply additional scrutiny regardless of the final numerical score. Currently 7.6% of indexed agents — 20,946 agents — use EIP-7702 delegation.

How is Agent Trust Score different from Wallet Reputation Score?

Both use the same 0-1000 scale, making them directly comparable. However, Agent Trust Score applies the scoring to multiple addresses simultaneously — owner wallet, agent wallet, and feeder address — and combines them using trust delegation logic and fleet-level farm detection signals that do not exist in the standalone Wallet Reputation Score. Additionally, Agent Trust Score cross-references the criminal record database for rug pull and honeypot history. For the Wallet Reputation Score methodology, see our Wallet Auditor learn page.

What is the free tier?

The free tier covers 1,000 queries per month for indexed public agents on Ethereum, BSC, Base, and Avalanche. No API key required to start — simply query beta.chainaware.ai/agent-trust-score with any agent ID, owner address, or agent wallet. Enterprise plans with higher rate limits, SLA, webhooks, and dedicated integration support are available via chainaware.ai/schedule.

Further Reading

• Agent Trust Score — Methodology Overview
• The Agent Trust Infrastructure Race: Six Platforms Compared
• The First Step in Agentic Commerce Isn’t Integration. It’s Trust.
• CB Insights AI Fraud Prevention Market Map — ChainAware Coverage
• AI-Powered Blockchain Analysis for Crypto Security 2026
• Rug Pull Tracker — $569M on PancakeSwap V2
• DeFi Compliance: Complete KYT and AML Guide 2026
• Web3 Wallet Auditing Providers in 2026 — Complete Comparison
• Forensic vs AI-Powered Blockchain Analysis
• DeFi Credit Score Platforms Compared 2026
• Prediction MCP Setup Guide
• 32 Ready-Made Agents

ChainAware.ai is the Web3 Agentic Growth Infrastructure — behavioral intelligence for DeFi protocols, AI agents, and individual crypto users. 20M+ wallet personas, 98% fraud detection accuracy, <100ms API latency across 8 blockchains. Named in CB Insights’ AI Fraud Prevention Market Map in the On-Chain Intelligence category. chainaware.ai

The post ChainAware Launches Agent Trust Score – On-Chain Trust Scoring for the Agentic Commerce Era first appeared on ChainAware.ai.

A $3-5 trillion market is forming around one unsolved problem: how do you know whether to trust an AI agent before it touches your funds? Six distinct approaches have emerged in 2026 to answer that question. They carry similar names – trust scores, reputation scores, behavioral scores – but they answer fundamentally different questions, protect against different threat models, and leave very different blind spots.

Choosing the wrong approach does not mean you get a slightly worse score. It means the specific fraud pattern you face is exactly the one your chosen platform cannot detect. An operator running a Sybil farm of 50 agents will not be caught by a review-quality platform scoring each agent individually. A serial rug puller launching agents under a fresh wallet will not be caught by a platform that scores wallet age but ignores creation history. Understanding which approach catches which threat is the most important infrastructure decision in agentic commerce right now.

This guide maps every significant agent trust platform in 2026 – their methodology, their real strengths, their genuine blind spots, and the specific signals that separate them. It is written for three audiences: DeFi protocol builders integrating agents and choosing a trust gating system, agent creators who want to understand how their agents get scored across platforms, and investors evaluating the agent trust infrastructure market as a sector.

Table of Contents

1. Why the Approach Matters More Than the Score
2. The Four Questions Agent Trust Platforms Answer
3. Platform 1 – ERC-8004 Native Reputation Registry
4. Platform 2 – RNWY: Review Quality and Sybil Detection
5. Platform 3 – SkyeProfile: Multi-Attestation Wallet Trust
6. Platform 4 – AXIS T-Score: Runtime Performance Scoring
7. Platform 5 – DJD Agent Score: Wallet Activity Scoring
8. Platform 6 – ChainAware: Behavioral Fraud Intelligence
9. The Five Signals Only One Platform Provides
10. Head-to-Head Comparison Table
11. Decision Matrix: Which Platform for Which Use Case?
12. The White Space: Five Capabilities Nobody Has Built Yet
13. The Investor Lens: What Makes Agent Trust Infrastructure a Durable Market
14. Frequently Asked Questions

Why the Approach Matters More Than the Score

Every agent trust platform in 2026 returns a number. The number is not the product – the threat model behind it is. Two platforms can both return a score of 72 for the same agent and disagree completely about what that score means, because they measured entirely different things to compute it.

RNWY’s score of 72 tells you: the agent’s peer reviews show limited sybil activity and the reviewer wallets are moderately established. ChainAware’s score of 72 tells you something different: the owner wallet has a moderate fraud probability, the feeder address is unknown, and no criminal record signals are present. SkyeProfile’s assessment tells you something different again: the wallet passes certain solvency and governance checks but shows limited behavioral depth across attestation providers.

Each score is internally consistent. However, each one answers a different question about the same agent. Consequently, the correct question for any DeFi protocol builder, agent creator, or investor is not “which platform gives the highest scores?” It is “which platform’s threat model matches the risk I am actually trying to prevent?”

For context on how this same problem appears at the wallet intelligence layer, see our complete guide to Web3 Wallet Auditing Providers in 2026 – the same principle applies there, where raw data providers, descriptive profilers, and predictive intelligence systems each answer fundamentally different questions about the same wallet address.

The Four Questions Agent Trust Platforms Answer

Before comparing platforms, mapping the question each approach addresses clarifies the landscape considerably. Every platform in the 2026 agent trust market falls into one of four categories based on what it actually measures.

Question 1: Have other agents endorsed this agent?

This is the peer review / reputation registry approach. The ERC-8004 native system operates here. Additionally, RNWY’s core methodology operates here – with the significant enhancement of reviewing the quality of the reviewers rather than simply counting the reviews. The fundamental limitation of this approach is that endorsement and trustworthiness are not the same thing. Any operator who controls multiple agents can engineer endorsements between them at near-zero cost.

Question 2: Has this agent performed tasks well?

This is the runtime performance approach. AXIS T-Score operates exclusively in this category, measuring 11 behavioral dimensions of agent task execution – completion rate, instruction adherence, error recovery, security posture, and similar metrics. The limitation here is that runtime performance and financial trustworthiness are orthogonal. An agent that executes tasks reliably can still be controlled by a fraud operator using it as a front for financial extraction.

Question 3: What does the agent’s wallet history look like?

This is the wallet activity approach. DJD Agent Score operates here, scoring seven wallet dimensions including transaction history, partner diversity, and account age. SkyeProfile’s solvency layer also operates here. The limitation is that wallet history describes the agent wallet itself – which is frequently a fresh address created specifically for the agent, with minimal history by design. A fresh agent wallet with no history is not the same as a fraudulent one, but wallet-only scoring treats them identically.

Question 4: Who controls this agent, and what have they done on-chain?

This is the behavioral fraud intelligence approach. ChainAware operates here – scoring the owner wallet that controls the agent, the feeder address that funded the owner, and cross-referencing both against a database of confirmed rug pulls and honeypot token creations. The threat model this addresses is the one that matters most for autonomous financial execution: a sophisticated fraud operator registering a new agent identity to continue activities previously conducted under different wallet identities.

Each of these four approaches is internally valid. Furthermore, they are not mutually exclusive – DeFi protocols can layer multiple approaches. However, understanding which question each one answers is essential before choosing which to gate on.

Platform 1 – ERC-8004 Native Reputation Registry

What it is

The ERC-8004 standard includes a built-in Reputation Registry as an optional component of the agent identity specification. The registry provides a standard interface for posting and fetching feedback signals. Critically, the standard explicitly does not define a scoring algorithm – aggregation and scoring are intentionally delegated to third parties. The protocol is infrastructure. Every other platform in this comparison is a third-party scoring layer on top of it.

Methodology

Any wallet can submit a feedback signal to the Reputation Registry for any registered agent. The signal includes a rating and optional metadata. The registry stores it on-chain. Reading platforms aggregate these signals according to their own methodology – which means the “ERC-8004 reputation score” is not a single consistent number but rather different outputs from different aggregation strategies across different platforms reading the same underlying data.

Strengths

The registry is permissionless, transparent, and composable. Any smart contract can read it. Furthermore, on-chain storage means the feedback history is permanent and verifiable. For building a decentralised reputation system in principle, the architecture is sound.

Blind spots

The fundamental blind spot is that the registry cannot distinguish manufactured reviews from genuine ones without an external intelligence layer on top. An operator controlling 50 agents can give each one a 5-star review from the other 49 at a cost of a few dollars in gas. Additionally, the native registry provides no information about who controls the agent, no feeder analysis, no fraud prediction, and no criminal record check. It answers only “what have other agents said about this agent?” – which is the weakest possible trust signal in a system where agents can be created and coordinated freely.

Who it is for

The native registry is appropriate as an additional data layer for platforms that have already implemented stronger trust signals. It should not serve as a primary trust gate for any DeFi protocol permitting autonomous financial execution.

Platform 2 – RNWY: Review Quality and Sybil Detection

What it is

RNWY (rnwy.com) is the most established third-party agent trust platform operating on ERC-8004 in 2026. RNWY positions itself as the trust layer for an economy where participants might not be human, with 185K+ agents scored and every score showing its math – the same door for humans and AI alike. The platform is notable for its transparency: all scoring methodology is published, including exact signal weights.

Methodology

RNWY’s trust score uses six input signals combined with additive modifier stacking, logarithmic value scaling, buffer zones, and evaluator softening to produce a score out of 95 across five tiers. The six signals weight toward reviewer quality rather than raw review count.

RNWY’s sybil detection applies four signals with explicit weights: common funder (6×), inhuman velocity (5×), sweep pattern (3×), and score clustering (1×). The weighted score produces severity levels: Low (0-2), Moderate (3-9), Elevated (10-19), and Heavy (20+). This makes RNWY’s sybil detection notably rigorous – it specifically targets the coordinated-review attack that would compromise naive review counting.

Since v1.1.0 (April 2026), RNWY also returns an owner wallet score, commerce summary (provider jobs, counterparty count, commerce tenure), and transaction-backed review percentage in the API response. However, these are additional intelligence fields – they appear in the response but do not affect the tier calculation or the primary trust score. This is the critical distinction from ChainAware: RNWY surfaces the owner wallet score as informational context; it does not integrate it into the scoring formula.

RNWY also indexes 1.7 million commerce jobs across Olas, Virtuals ACP, and SATI – making it the most comprehensive commerce activity tracker in the agent ecosystem. Trust scores live on Base mainnet, meaning any smart contract can read an agent’s score, tier, and sybil severity mid-transaction without an API call or oracle fee. This on-chain accessibility is a significant technical advantage for DeFi protocols that want to gate at the smart contract level rather than the application layer.

Strengths

RNWY’s strengths are transparency, on-chain accessibility, and commerce job history depth. The published methodology with exact signal weights means any relying party can independently verify a score calculation. The on-chain trust oracle on Base enables smart contract-level gating. The 1.7M commerce job index provides genuine economic activity context that no other platform matches. Additionally, the sybil detection is genuinely sophisticated – the common funder signal (weighted 6×) specifically targets the attack pattern of one operator funding multiple reviewer wallets from a single source.

Blind spots

RNWY’s primary blind spot is the boundary it draws at the review layer. The owner wallet score is surfaced but does not affect the tier. Feeder address analysis does not exist. Prior token creation history – rug pulls, honeypots – is not queried. Farm detection operates only at the reviewer level, not at the fleet level. Consequently, a fresh wallet that has never received a review (no positive signals, no negative signals) scores the same as an established operator in RNWY’s primary score calculation – both lack review history. Furthermore, a serial rug puller who has never participated in the ERC-8004 review ecosystem will not trigger any RNWY detection signal, because their fraud history exists in token creation, not in agent reviews.

Who it is for

RNWY is the strongest choice for platforms where agent reputation is displayed to users (marketplaces, directories, leaderboards) and where the primary threat model is manufactured peer endorsements. It is a compelling addition to any trust stack as a review quality layer. However, it is not sufficient as a standalone gate for DeFi protocols where the primary threat is a fraud operator using agents as the execution vehicle for financial crimes.

Platform 3 – SkyeProfile: Multi-Attestation Wallet Trust

What it is

SkyeProfile (skyemeta.com) is a multi-attestation wallet trust profile that orchestrates nine specialised attestation providers and returns one unified signed profile per wallet. The system uses a dual-score model with Signal Depth (behavioral observability) and Risk Intensity (sybil and fraud risk) as independent axes, covering 150K+ agents across ERC-8004, Olas, Virtuals, and SATI registries.

Methodology

SkyeProfile works on a general contractor model – eight dimensions, eight independent providers, eight verifiable signatures. One API call returns ten independently verifiable attestations, each with a JWKS URI so relying parties can verify any dimension offline without trusting SkyeMeta itself. The dimensions span solvency (wallet holdings across 33 chains), governance participation, behavioral trust, identity, security posture, compliance, performance, and settlement track record.

Notably, SkyeProfile uses RNWY as its behavioral trust provider – RNWY maintains the dual-score model across 150K+ agents spanning twelve EVM chains and Solana within the SkyeProfile attestation framework. This means SkyeProfile inherits RNWY’s methodology for the behavioral dimension, including both RNWY’s strengths (sybil detection, review quality analysis) and RNWY’s blind spots (no feeder analysis, no criminal record check, owner wallet informational only).

Strengths

SkyeProfile’s primary strength is breadth and verifiability. By aggregating nine specialised providers and returning independently verifiable signatures, it gives relying parties a comprehensive wallet profile that no single provider can match across all dimensions. The cryptographic verifiability (ES256 or EdDSA signatures with JWKS-published keys) is technically rigorous and appropriate for high-stakes autonomous execution contexts. The 33-chain solvency layer is the most comprehensive wallet holdings analysis in the market.

Blind spots

SkyeProfile scores the agent wallet – the address registered with the ERC-8004 identity. Since it delegates behavioral trust to RNWY, it inherits RNWY’s blind spots on feeder analysis and criminal record checking. Furthermore, because SkyeProfile is built as a wallet profiling system rather than an agent-specific fraud intelligence system, it does not perform fleet-level farm detection or trust delegation from owner to agent wallet. The platform also scores 150K agents across multiple registries – which is valuable breadth, but means its ERC-8004 specific coverage is thinner than RNWY’s 185K ERC-8004-specific indexed agents.

Who it is for

SkyeProfile is strongest for use cases requiring verifiable, multi-dimensional wallet attestations – particularly in contexts where cryptographic proof of each assessment matters, such as compliance audit trails or high-stakes DeFi credit decisions. For the broader DeFi credit scoring context, see our DeFi Credit Score Platform comparison. SkyeProfile is not a standalone agent trust gate – it is a comprehensive wallet profiling layer that serves agent trust as one of several use cases.

Platform 4 – AXIS T-Score: Runtime Performance Scoring

What it is

AXIS T-Score (axistrust.io) operates in an entirely different category from every other platform in this comparison. While all other platforms score the agent’s identity and on-chain history, AXIS scores the agent’s runtime behavior – how well it performs tasks, follows instructions, and operates within defined guardrails during actual execution.

Methodology

AXIS measures 11 behavioral dimensions: task completion rate, instruction adherence, data handling, transparency, error recovery, consistency, scope compliance, resource efficiency, communication clarity, security posture, and audit trail quality. All of these metrics are off-chain – they measure what the agent does during task execution, not what its controlling wallet has done on-chain. Scores run from 0 to 1,000 across five tiers (T1-T5), using the same 0-1,000 scale as ChainAware’s Agent Trust Score but measuring completely different inputs.

Strengths

AXIS addresses a genuinely different problem: does this agent do what it claims to do? An agent that claims to be a compliance screener but routinely fails to flag sanctioned addresses will score low on AXIS – regardless of how trustworthy its owner wallet is. That quality assurance dimension is valuable and not addressed by any on-chain behavioral platform. For enterprise contexts where agents are deployed for specific task categories, AXIS provides the most rigorous evaluation of task quality available.

Blind spots

AXIS scores runtime performance, not financial trustworthiness. An agent can score T5 on AXIS (top-tier task execution) and be controlled by a serial rug puller who has stolen millions. The two assessments are orthogonal – they address completely different threat models. For DeFi protocols where the primary concern is financial fraud rather than task quality, AXIS provides no relevant signal. Additionally, AXIS is entirely off-chain, which means it has no chain coverage, no wallet analysis, and no on-chain verifiability. Scores cannot be read by smart contracts and cannot be cryptographically verified against on-chain data.

Who it is for

AXIS is most valuable for enterprise deployments where agents perform specific workflow tasks – research, content generation, data analysis – and where task quality rather than financial fraud is the primary concern. Layering AXIS with an on-chain identity trust system (ChainAware for fraud intelligence, RNWY for review quality) produces the most complete agent evaluation stack: you verify both who controls the agent and how well the agent performs.

Platform 5 – DJD Agent Score: Wallet Activity Scoring

What it is

DJD Agent Score is the smallest and most narrowly focused platform in this comparison. It returns a 0-100 behavioral trust score for any wallet, combining seven dimensions – transaction history, partner diversity, volume patterns, account age, balance stability, activity consistency, and USDC usage – with sybil detection and gaming velocity checks. Scores feed directly into the ERC-8004 Reputation Registry as off-chain attestations, and the service is monetised via x402 micropayments in USDC on Base.

Methodology and coverage

DJD scores the agent wallet address across those seven dimensions. The scoring approach is transparent and the seven dimensions are reasonable wallet activity signals. However, coverage is Base-only – the platform does not index agents on Ethereum mainnet, BSC, or Avalanche. Furthermore, like SkyeProfile’s solvency layer and the ERC-8004 native registry, DJD scores the agent wallet rather than the owner wallet. This means it faces the same fresh wallet problem: a newly created agent wallet with no transaction history will score near zero on all seven dimensions regardless of the owner’s reputation.

Strengths and limitations

DJD’s x402 integration is technically interesting – it demonstrates a viable micropayment-based business model for agent trust scoring that does not require API keys or subscription agreements. The seven-dimension wallet scoring is simple, auditable, and directly verifiable. However, the Base-only coverage and agent-wallet focus rather than owner-wallet focus significantly limit DJD’s utility as a primary trust gate. It is best understood as an early-stage product demonstrating one viable approach rather than a production-ready trust infrastructure system.

Platform 6 – ChainAware: Behavioral Fraud Intelligence

What it is

ChainAware’s Agent Trust Score approaches agent trust from the opposite direction of every other platform. Rather than starting from the agent and asking what signals the agent produces (reviews, task performance, wallet history), ChainAware starts from the human behind the agent and asks what that human has done on-chain across their entire history – including activities completely unrelated to the current agent registration.

This inversion is the foundation of every signal that differentiates ChainAware from the rest of the market. For a full technical explanation of the scoring formula, see the Agent Trust Score methodology page.

Core formula

The Agent Trust Score builds on the same Wallet Reputation Score formula used across ChainAware’s products:

ReputationScore = (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability)
Maximum: 1,000

This formula runs separately on the owner wallet and the agent wallet. Furthermore, it runs on the feeder address when traceable. The results are then combined using trust delegation logic, farm detection modifiers, and criminal record hard caps to produce the final Agent Trust Score. The 0-1000 scale is consistent with the Wallet Reputation Score – meaning a protocol that already uses ChainAware’s wallet intelligence can compare agent trust and wallet trust on the same axis without recalibration.

Coverage and infrastructure

ChainAware indexes 240,000+ ERC-8004 agents across Ethereum mainnet, BSC, Base, and Avalanche – the widest chain coverage in the market for a predictive fraud intelligence approach. The underlying wallet persona database covers 20M+ addresses across 8 blockchains, trained on behavioral data accumulated over multiple years. The fraud prediction model achieves 98% accuracy on held-out test data, as documented in our AI-Powered Blockchain Analysis guide. Additionally, scores are available via the Prediction MCP server, meaning any Claude-based DeFi agent can query agent trust scores as a native tool call without custom API integration.

The Five Signals Only One Platform Provides

Five signals in the Agent Trust Score are not replicated by any other platform currently operating in the ERC-8004 agent trust market. Each one addresses a specific threat model that the other approaches structurally cannot reach.

Signal 1: Feeder address analysis

The feeder address is the wallet that funded the agent’s owner wallet. Tracing and scoring it is the single most distinctive capability in the ChainAware Agent Trust Score. No other platform – not RNWY, not SkyeProfile, not DJD – performs feeder analysis.

Why it matters: an experienced fraud operator rotates owner wallets between campaigns. Wallet A runs a rug pull, gets flagged, and is abandoned. Wallet B is freshly created and funded from Wallet A. Wallet B then registers 40 agents on ERC-8004. Every platform that scores only the agent or the agent’s direct owner wallet will see a clean Wallet B with no fraud history. ChainAware traces the funding path and scores Wallet A – the feeder – which carries the fraud record. Wallet B’s agents receive hard-capped scores regardless of how clean Wallet B’s own history appears.

ChainAware covers feeder analysis for approximately 38% of indexed agents – the ones with a traceable single-hop funding source. For agents where the feeder is a verified CEX withdrawal address (Binance, Coinbase, Kraken, OKX), the platform flags this as FEEDER_CEX_VERIFIED – a positive trust signal that implies the owner wallet was funded via a KYC’d exchange withdrawal. For agents where the feeder is unknown or obfuscated, the platform applies a penalty reflecting the information asymmetry.

Signal 2: Criminal record – rug pull history

ChainAware maintains a database built from one year of on-chain liquidity pair history. That database records which wallet addresses created pools that subsequently exhibited rug pull patterns – rapid liquidity removal after price appreciation, following the operational signature documented in our Rug Pull vs Pump and Dump guide.

Before computing the Agent Trust Score, ChainAware cross-references both the owner wallet and the feeder address against this database. A single confirmed rug pull in the owner’s history generates a hard cap on the Agent Trust Score – a ceiling no other signal can override. This is the signal that connects yesterday’s token fraud to today’s agent deployment. An operator who rugged three pools on PancakeSwap in Q4 2025 and registered 40 agents in Q1 2026 is caught by this check. No other agent trust platform makes that connection, because no other platform maintains a paired rug pull database and cross-references it against agent registry data.

Signal 3: Criminal record – honeypot token history

Separately from rug pull detection, ChainAware maintains token audit data identifying honeypot contracts – tokens with embedded code that prevents buyers from selling. The creator wallet for each identified honeypot token is recorded. Cross-referencing agent owner wallets against this database produces a second criminal record dimension: has the agent’s controller previously created trap tokens that extracted funds from retail investors?

Honeypot creation and rug pull creation are related but distinct fraud patterns. Some operators specialise in one or the other; some use both. Having both databases cross-referenced produces a more complete criminal record than either alone. Together with rug pull history, this gives ChainAware the only criminal record check available in the agent trust market. For more on how token auditing produces these signals, see our Token Audit methodology.

Signal 4: Trust delegation

Trust delegation is ChainAware’s mechanism for handling the fresh agent wallet problem without penalising legitimate new agents. Agent payment wallets are frequently created specifically for an agent deployment – they are fresh addresses with no transaction history. A scoring approach that treats wallet age as a primary negative signal would incorrectly assign low trust to every newly deployed agent from a legitimate operator.

ChainAware’s trust delegation sets a floor for the agent wallet’s effective score based on the owner wallet’s Reputation Score. A strong owner (Sovereign tier, 800+) partially transfers credibility to the fresh agent wallet, resulting in a significantly higher Agent Trust Score than the agent wallet alone would produce. A fraud-flagged owner, by contrast, cannot delegate any meaningful trust – the delegation factor collapses to near zero. This means fresh wallets from reputable operators score correctly high, and fresh wallets from fraud operators score correctly low – which is the right outcome for both cases.

Signal 5: Fleet-level farm detection

Every other platform in this comparison scores agents individually. ChainAware maintains an owner profile database – tracking how many agents each owner controls across all indexed chains and whether those agents were registered in the same block (indicating automated bulk registration). This fleet-level view enables detection of agent farms that individual agent scoring cannot surface.

An operator running a farm of 50 agents will have each individual agent score independently on RNWY, SkyeProfile, or DJD. Nothing in those individual scores reveals the coordinated nature of the fleet. ChainAware sees the fleet. Owners controlling anomalously large numbers of agents receive a suppression modifier that applies to every agent in their fleet – including agents that individually might score cleanly. This is the signal that catches the specific agentic commerce attack pattern identified in our Blockchain Data Providers guide: one operator manufacturing ecosystem depth through controlled agent populations.

Head-to-Head Comparison Table

The following table compares all six approaches across every dimension relevant to DeFi protocol builders and investors evaluating the space. Each row describes a specific capability, not a general category, to make the comparison as concrete as possible.

Decision Matrix: Which Platform for Which Use Case?

No single platform is the correct choice for every context. The right stack depends on what you are trying to prevent, what signals matter for your specific use case, and what integration constraints you are working within. The following matrix maps use cases to recommended platform combinations.

DeFi protocol gating autonomous financial execution

Primary: ChainAware Agent Trust Score – owner fraud probability, feeder analysis, criminal record check, and farm detection are all directly relevant to the threat model. Set tier thresholds based on transaction risk: Trusted (600+) for high-value operations, Provisional (400+) for lower-risk flows with monitoring.

Secondary: RNWY for reputation display – show the RNWY score in your protocol’s agent directory alongside the ChainAware score. They answer different questions and the combination is more informative than either alone.

Optional: SkyeProfile attestations if your compliance framework requires cryptographically verifiable attestations as audit evidence. For the compliance context, see our DeFi Compliance and AML guide.

Agent marketplace or directory

Primary: RNWY – the on-chain trust oracle on Base enables smart contract-level minimum score requirements for job listing. The commerce job history (1.7M jobs) is directly relevant to marketplace quality filtering. The transparent published methodology means marketplace users can understand exactly why an agent scores as it does.

Secondary: ChainAware Agent Trust Score – surface it as a fraud intelligence layer alongside RNWY’s reputation score. The two scores are complementary: RNWY tells users whether the agent’s reviews are genuine; ChainAware tells users whether the human behind the agent has a history of financial fraud.

Enterprise workflow agent deployment

Primary: AXIS T-Score – for enterprise agents performing specific workflow tasks (research, compliance screening, content generation), task quality assurance is the primary concern. AXIS is the only platform that evaluates whether an agent does what it claims to do.

Secondary: ChainAware if the agent has financial execution permissions. Task quality and financial trustworthiness are both relevant for agents with write permissions to financial systems.

Agent creator wanting to understand their score

Agent creators interact with multiple trust systems simultaneously. Your agents are scored by every platform a buyer chooses to query. Understanding all five is therefore more important for creators than for buyers. Specifically:

• RNWY score: ensure your agent has genuine reviews from established reviewer wallets. Avoid requesting reviews from wallets that bulk-review across many agents – they will be detected as sybil reviewers and suppress your score
• ChainAware score: your owner wallet’s history is the primary input. A wallet with 12+ months of diverse DeFi activity scores significantly higher than a fresh wallet. If your feeder is a CEX withdrawal, this is a positive signal that surfaces automatically
• SkyeProfile: ensure your owner wallet holds governance tokens and participates in established protocols – the solvency and governance dimensions reward breadth of DeFi participation
• AXIS: if you want T-Score evaluation, ensure your agent returns reliable, consistent outputs and maintains audit trail quality across repeated task executions

The White Space: Five Capabilities Nobody Has Built Yet

The current agent trust infrastructure market is six months old. Consequently, significant white space remains – capabilities that no platform currently provides but that the market will almost certainly require as agentic commerce scales. The following five gaps represent the next investment and product opportunities in this category.

Gap 1: Agent-to-agent trust propagation

No platform currently answers this question: if Agent A scores Sovereign and has completed 10,000 successful interactions with Agent B, does that interaction history update Agent B’s trust score? In human systems, ongoing positive relationships build trust over time. In agent systems, every score is computed from static inputs without accounting for the accumulated interaction history between specific agent pairs. Building trust propagation that flows through agent interaction graphs – raising Agent B’s score based on verified positive interactions with high-scoring agents – would fundamentally change how trust compounds in the agentic economy.

Gap 2: Cross-registry agent identity resolution

An operator may deploy agents across ERC-8004, Olas, Virtuals, and SATI simultaneously. Currently, each registry treats these as separate identities. No platform provides unified entity resolution – grouping agents across registries that share the same owner wallet into a single entity profile. This matters because fleet-level behavior visible at the entity level (100 agents across 4 registries controlled by one owner) is invisible at the per-registry level (25 agents on each).

Gap 3: MCP server trust scoring

Every agent trust platform scores the agent itself. None score the MCP servers the agent calls. An agent connecting to a malicious or compromised MCP server is a trusted agent performing untrusted actions. As the MCP ecosystem grows – Smithery already indexes thousands of MCP servers – the trust question extends naturally from “who is the agent?” to “what tools is the agent using?”

Gap 4: Trust score-based insurance underwriting

No DeFi insurance protocol currently uses agent trust scores as an underwriting input. A protocol granting autonomous execution access to a Sovereign-tier agent (800+) takes on less risk than one granting the same access to a Provisional-tier agent (400-599). Insurance premiums, coverage limits, and deductibles could all be parameterised on agent trust scores – creating a financial market that prices the residual risk after trust gating rather than treating all agent access as equally risky.

Gap 5: Dynamic trust scores updating in real time

Current trust scores are computed at query time from static inputs and cached. None update continuously as new on-chain events occur. An agent whose owner wallet executes a suspicious transaction pattern at 14:00 UTC will not have its trust score updated until the next scoring cycle. Real-time trust score streaming – where scores update within seconds of relevant on-chain events – would enable dynamic access control that responds to emerging fraud signals rather than lagging behind them.

The Investor Lens: What Makes Agent Trust Infrastructure a Durable Market

For investors evaluating the agent trust infrastructure category, several structural dynamics shape the market’s long-term economics.

The TAM compounds with agent adoption

Agent trust infrastructure is a derived demand market – its TAM scales directly with agentic commerce adoption. McKinsey’s $3-5 trillion agentic commerce estimate implies that every dollar of economic activity flowing through autonomous agents creates a corresponding demand for trust verification of those agents. As Morgan Stanley projects , nearly half of online shoppers will use AI shopping agents by 2030. Each one of those agents represents a trust decision for every protocol or merchant it interacts with.

Consequently, market growth in agent trust infrastructure is structurally tied to the overall growth of agentic AI – a market with multiple large tailwinds including regulatory pressure (Know Your Agent protocols emerging from the EU AI Act framework), enterprise adoption (agents handling financial workflows requiring documented risk controls), and protocol incentives (DeFi protocols facing liability exposure from agent-initiated fraud).

Data network effects favour early movers with behavioral databases

Agent trust platforms that rely on behavioral databases – rather than purely algorithmic or review-based scoring – accumulate a compounding data advantage. A platform with one year of on-chain pair history knows which wallets created rug pools. A platform with two years knows which wallets have repeat patterns across multiple fraud campaigns. That historical depth cannot be compressed – a competitor starting today cannot buy the historical database that an early mover has built through continuous operation.

This dynamic differentiates behavioral fraud intelligence platforms from review-quality platforms. RNWY’s review quality algorithm could theoretically be replicated by a well-resourced team in months. The underlying behavioral database and fraud prediction model trained on years of on-chain data cannot. For context on how machine learning model development timelines apply to this space, see our AI-Powered Blockchain Analysis guide.

Complementary rather than winner-takes-all

The four distinct approaches in the market address different threat models that do not fully substitute for each other. RNWY’s review quality signal and ChainAware’s behavioral fraud intelligence are complementary – a protocol using both is better protected than a protocol using either alone. This means the agent trust market is likely to support multiple sustainable businesses serving different parts of the trust stack, rather than converging to a single dominant platform.

The parallel is the credit rating market – Moody’s, S&P, and Fitch coexist because rating agencies with complementary methodologies provide more value to the market than a single monopoly. Agent trust infrastructure may evolve similarly, with different platforms serving different trust dimensions in a layered stack. For investors, this implies that both the review quality layer (RNWY) and the behavioral fraud intelligence layer (ChainAware) have independent market positions rather than competing for the same slot in every protocol’s integration.

Regulatory tailwinds

The EU AI Act , which takes full effect in August 2026, creates documentation and risk assessment requirements for high-risk AI systems. Autonomous agents with financial execution permissions are a clear candidate for high-risk classification under this framework. Protocols operating in EU-regulated markets will need demonstrable risk controls for agent interactions – a requirement that agent trust scoring infrastructure directly satisfies. Additionally, Know Your Agent (KYA) protocols are emerging as the agent-layer equivalent of KYC, creating a compliance-driven pull for trust verification infrastructure beyond pure product adoption.

Frequently Asked Questions

Can I use multiple agent trust platforms simultaneously?

Yes – and for high-value use cases, this is the recommended approach. RNWY and ChainAware answer different questions about the same agent. Using RNWY for review quality and ChainAware for owner fraud intelligence produces a more complete picture than either alone. The integration is straightforward: make two API calls per agent and combine the results in your access control logic. DeFi protocol builders can set independent thresholds for each score – for example, requiring RNWY tier 3+ (genuine review history) AND ChainAware Trusted tier (600+) for full autonomous execution access.

Which platform is best for displaying trust to end users?

RNWY is the strongest choice for trust display because its methodology is fully published and each score shows its math. End users can understand exactly why an agent scored as it did – which reviewer wallets were flagged, which sybil patterns were detected, what the address age contributed. Transparency builds user confidence. ChainAware’s score is complementary but its weights are private (to prevent gaming), making RNWY more appropriate for user-facing display where explainability matters.

How do the different score scales compare?

The score scales are not directly comparable across platforms. RNWY scores out of 95 (not 100 – their maximum is 95 due to scoring mechanics). ChainAware and AXIS both use 0-1,000. DJD uses 0-100. SkyeProfile uses two independent axes rather than a single number. Converting between scales requires understanding what each platform actually measures, which is why the comparison table above focuses on capabilities rather than score values. An agent scoring 72/95 on RNWY and 650/1,000 on ChainAware is not inconsistent – those numbers describe entirely different assessments.

Does RNWY’s owner wallet score compete with ChainAware?

Not meaningfully. RNWY’s v1.1.0 update added owner wallet score as an informational field in the API response – but explicitly does not affect tier calculation or the primary trust score. The field surfaces the owner wallet’s RNWY-defined score as context for relying parties who want to incorporate it into their own decision logic. ChainAware makes the owner wallet score the primary input to the Agent Trust Score formula, combines it with feeder analysis and criminal record data, and applies trust delegation. The two approaches share the observation that owner wallet matters – but diverge completely on how to score it and how much weight it should carry.

What is ERC-8183 and how does it relate to agent trust?

ERC-8183 is a commerce protocol that gives AI agents trustless commerce capabilities – handling escrow, state transitions, and evaluator attestation for agent-to-agent job markets. The spec is intentionally minimal – it handles the commerce mechanics but explicitly does not handle trust scoring, discovery, or fraud detection. RNWY has built a marketplace and trust scoring layer on top of ERC-8183. ChainAware’s Agent Trust Score is compatible with ERC-8183 job markets as a pre-interaction trust gate – protocol teams can require a minimum Agent Trust Score before an agent can claim a job or receive escrowed funds.

How often do trust scores update?

Update frequencies vary by platform. ChainAware’s fraud prediction model retrains daily – meaning the fraud probability feeding into owner wallet scores updates continuously as new on-chain patterns emerge. Scores for specific agents update when new relevant events are detected (new agent registrations, owner wallet activity, feeder transactions). RNWY scores update as new reviews are submitted to the ERC-8004 Reputation Registry and as sybil analysis runs on reviewer wallets. AXIS T-Score updates based on runtime task execution data. None of the current platforms offer real-time streaming score updates – that remains a white space capability described above.

Is the ChainAware Agent Trust Score relevant for non-ERC-8004 agents?

Partially. The owner wallet and feeder address scoring works for any wallet address, regardless of whether it is associated with an ERC-8004 registration. A protocol that receives agent-initiated transactions from wallets not registered on any standard identity registry can still query ChainAware’s Fraud Detection API for the controlling wallet’s behavioral intelligence. The ERC-8004-specific signals (farm detection, trust delegation from registry data) require an ERC-8004 registration to function. However, the owner fraud probability, feeder analysis, and criminal record check work on any wallet regardless of registry status. For protocols on chains not yet covered by ERC-8004 registries, this means ChainAware provides partial Agent Trust Score functionality even before full ERC-8004 adoption on those chains.

Where can I read ChainAware’s full scoring methodology?

The complete methodology – including the five scoring layers, all flag definitions, score tier descriptions, and the trust delegation formula – is documented at chainaware.ai/learn/agent-trust-score. The signal categories are published. The exact weights and model coefficients remain private to prevent gaming. The equivalent documentation for the underlying Wallet Reputation Score (which feeds into the Agent Trust Score formula) is at chainaware.ai/learn/for-individuals/wallet-auditor.

Further Reading

• Agent Trust Score – Complete Methodology – the five scoring layers, all flags, tier definitions, and trust delegation formula
• The First Step in Agentic Commerce Isn’t Integration. It’s Trust. – the companion article covering the trust gap in DeFi protocol agent integrations
• Web3 Wallet Auditing Providers in 2026 – the same three-layer framework applied to the wallet intelligence market
• Web3 Analytics Tools for Dapps: Complete Comparison – where agent trust scoring fits in the broader DeFi analytics stack
• AI-Powered Blockchain Analysis for Crypto Security – the machine learning methodology behind ChainAware’s 98% fraud detection accuracy
• Rug Pull vs Pump and Dump – the fraud patterns that generate ChainAware’s criminal record database
• DeFi Compliance: KYT and AML Guide 2026 – regulatory context for DeFi agent integration compliance
• DeFi Credit Score Platforms Compared – how agent trust scoring combines with borrower creditworthiness assessment
• Prediction MCP Setup Guide – add ChainAware behavioral intelligence including Agent Trust Score to any Claude agent
• 32 Ready-Made Agents – pre-built Claude agents including agent verification, fraud detection, and compliance screening

ChainAware.ai is the Web3 Agentic Growth Infrastructure – behavioral intelligence for DeFi protocols, AI agents, and individual crypto users. 20M+ wallet personas, 98% fraud detection accuracy, <100ms API latency across 8 blockchains. Try free at chainaware.ai.

The post The Agent Trust Infrastructure Race: Who Is Building the Trust Layer for Agentic Commerce? first appeared on ChainAware.ai.

Your DeFi protocol is ready to integrate AI agents. You have evaluated the frameworks, chosen your ERC-8004 registry, mapped the wallet flows, and written the integration spec. Yet one question remains unanswered in that spec – a question that determines whether your agentic integration scales safely or becomes a fraud vector the moment it hits production volume.

Who is actually behind the agent you are about to trust with your users’ funds?

Agentic commerce is accelerating at a pace that has outrun the trust infrastructure supporting it. McKinsey estimates the model could redirect $3-5 trillion in global financial flows by 2030 . Meanwhile, 78% of financial institutions already expect fraud to spike specifically because of AI agents operating autonomously in commercial systems. The gap between “agent integration complete” and “agent interaction verified” is where the next generation of DeFi fraud will live.

This guide covers the entire problem – from the structural gap in the ERC-8004 standard to the specific signals that distinguish a legitimate agent from a manufactured one, to the concrete integration pattern that closes the trust gap in under 100ms per transaction.

Table of Contents

1. What Agentic Commerce Actually Means for DeFi Protocols
2. The Integration Stack Has a Trust Gap
3. Why Voting-Based Agent Reputation Fails at Scale
4. Know Your Agent: The Three Questions That Matter
5. Signal 1 – The Owner Wallet: Scoring the Human Behind the Agent
6. Signal 2 – The Feeder Address: Who Funded the Controller?
7. Signal 3 – The Criminal Record: Rug Pulls, Honeypots, and Prior Fraud
8. Trust Delegation: How a Strong Owner Legitimises a Fresh Agent Wallet
9. Farm Detection: One Operator, Dozens of Agents
10. EIP-7702 Delegation: The Hidden Controller Problem
11. The Trust-Aware Agent Integration Pattern
12. The Compounding Risk of Getting This Wrong
13. How ChainAware Compares to Other Agent Trust Platforms
14. Frequently Asked Questions

What Agentic Commerce Actually Means for DeFi Protocols

Agentic commerce describes the shift from humans clicking “confirm” to AI agents executing transactions autonomously on behalf of users. In Web3, this shift is not a future scenario – it is happening now, at scale, across every DeFi protocol that accepts agent-initiated transactions.

Agents are managing DAO treasuries, executing lending strategies, routing liquidity, screening counterparties, and processing governance votes – all without a human in the approval loop for each action. The operational efficiency gains are real. Furthermore, the fraud surface that comes with them is equally real and far less discussed.

For DeFi protocol builders, the critical insight is this: if your protocol accepts transactions from external wallets today, you are already serving agent-initiated transactions. Agent wallets are indistinguishable from human wallets at the RPC layer. Therefore, you do not need to deliberately “integrate agents” to be exposed to the trust problem – you already are exposed, today, because any wallet can be controlled by an agent rather than directly by a human.

The agentic commerce numbers clarify the urgency. Morgan Stanley projects that nearly half of online shoppers will use AI shopping agents by 2030, accounting for approximately 25% of their total spending . In DeFi specifically, the transition is faster – AI is moving from the advisory layer (suggesting trades) to the execution layer (completing them). The distinction between advice and execution is the distinction between a bad recommendation and an empty wallet. Consequently, DeFi protocol builders face the urgency of solving this in 2026, not 2028.

Traditional fraud detection systems are structurally unfit for this environment. As detailed in our guide on AI-Powered Blockchain Analysis for Crypto Security, rule-based systems generate false positive rates of 30-70% – and they produce those false positives specifically on the rapid, sequential, cross-category transaction patterns that legitimate AI agents exhibit. Therefore, you need a different approach: one that evaluates the agent’s identity and the human behind it, rather than flagging agent behaviour as inherently suspicious.

The Integration Stack Has a Trust Gap

A typical agentic commerce integration in 2026 follows a well-established pattern. The agent framework (ElizaOS, Virtuals, a custom build) registers an identity on the ERC-8004 Identity Registry. Subsequently, that identity is referenced when the agent initiates interactions with DeFi protocols. The protocol’s smart contract processes the transaction. Funds move.

Every layer in that stack has tooling, documentation, and standards. Agent frameworks have deployment guides. ERC-8004 has a specification and a registry of 240,000+ agents across Ethereum, BSC, Base, and Avalanche . Smart contracts have audit firms. Yet the gap between the ERC-8004 registry lookup and the protocol interaction has no standard tooling – and it is precisely where trust decisions need to happen.

The ERC-8004 registry tells you four things about an agent: that it exists, which wallet controls it, which wallet receives its payments, and what URI points to its agent card JSON. Those four data points answer the question “does this agent have an identity?” They do not answer the question “should I trust this agent with autonomous execution?”

Specifically, the registry tells you nothing about:

• Whether the owner wallet has a history of creating rug pull pools or honeypot tokens
• Whether the owner was funded by a mixer, a sanctioned address, or a known fraud operator
• Whether this agent is one of 47 registered in the same block by the same operator running a Sybil farm
• Whether the wallet controlling this agent also controls the 46 agents that gave it positive reviews

This is the trust gap. Moreover, it is not an oversight in the ERC-8004 specification – the standard explicitly leaves scoring to third parties. As a DeFi protocol builder, you are therefore responsible for filling that gap in your own integration layer.

For context on how behavioral wallet intelligence fills similar gaps in fraud detection, see our complete guide to Web3 Wallet Auditing Providers in 2026. The same principle applies at the agent layer: raw identity data requires an intelligence layer on top before it becomes a trust signal.

Why Voting-Based Agent Reputation Fails at Scale

ERC-8004 includes a built-in Reputation Registry – a standard interface for agents to receive and query peer feedback. The design is intentionally open: any agent can leave a review, any protocol can read the scores, and the aggregation algorithm is left to third parties. On paper, this sounds like a reasonable decentralised trust mechanism. In practice, it is a manufactured-trust system waiting to be exploited.

The attack requires minimal technical sophistication. An operator deploys 50 agent wallets. Each wallet reviews every other wallet positively. All 50 accumulate reputation scores indistinguishable from agents with genuine peer endorsements. Total cost: gas fees for the review transactions, which on BSC or Base amounts to a few dollars. Total time: hours. Total manufactured trust: a full reputation history that any naive integration will treat as legitimate.

Furthermore, the problem compounds in agentic commerce contexts. When B2B agent networks operate where AI buyers negotiate directly with AI sellers in fractions of a second , the speed of manufactured-reputation exploitation is not limited by human review cycles. One fraudulent agent with a manufactured score can interact with thousands of protocol users autonomously before any human notices the pattern.

Voting-based reputation also has a specific structural blind spot: it cannot distinguish between an agent with 100 genuine endorsements and an agent whose owner simultaneously controls the 100 endorsing agents. Consequently, any trust system that reads only the Reputation Registry score is solving the wrong problem. The question is not “how many agents have endorsed this agent?” The correct question is “who controls this agent, and what have they done on-chain?”

This distinction drives the entire design of the ChainAware Agent Trust Score. Rather than reading the ERC-8004 Reputation Registry, we look behind the agent at the behavioral history of the wallets controlling it and funding its controller. The result is a trust signal that cannot be manufactured in hours and cannot be faked by a cluster of cooperating wallets.

Know Your Agent: The Three Questions That Matter

Know Your Agent (KYA) is emerging as the agent-layer equivalent of KYC. However, unlike KYC – which verifies identity documents and requires data collection – KYA for DeFi is necessarily on-chain behavioral. There are no passports in Web3. There is only transaction history, and that history is immutable, public, and available for scoring without touching any personal data.

A robust KYA check for any ERC-8004 agent answers exactly three questions. Together, these three questions generate a trust signal that is structurally difficult to fake and impossible to manufacture overnight.

Question 1: Who controls this agent?

Every ERC-8004 agent has an owner wallet – the address that holds the ERC-721 NFT representing the agent’s on-chain identity. This is the human or entity behind the agent. Scoring that wallet’s behavioral history is the foundation of any meaningful trust assessment.

Question 2: Who funded the controller?

The feeder address – the wallet that funded the owner – is the signal most agent trust platforms cannot reach. It is also the hardest signal to fake, because it requires either real capital from a legitimate source or exposure to traceable fraud infrastructure. An owner wallet can be freshly created and carefully aged. The funding source is immutable on-chain history.

Question 3: Has the controller done this before – in a bad way?

A year of on-chain pair history combined with token audit data produces a direct criminal record check for the agent controller. Has this wallet created honeypot tokens? Has it created liquidity pools and removed funds in rug pull patterns? Has the feeder funded previous rug pull operators? These questions have definitive on-chain answers – and no peer-review system can surface them.

The following three sections address each signal in depth, including how it feeds into the Agent Trust Score formula and what it means for your integration.

Signal 1 – The Owner Wallet: Scoring the Human Behind the Agent

The owner wallet is the single most important input to any agent trust score. Everything else – the agent wallet, the agent card, the reputation registry score – can be created fresh for a new fraud operation. The owner wallet’s behavioral history cannot.

ChainAware scores the owner wallet using the same three-pillar Reputation Score formula applied across 20M+ wallet personas:

ReputationScore = (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability)
Maximum: 1,000

Each pillar captures a distinct dimension of the owner’s on-chain identity.

Experience

Experience measures how long and how actively the owner wallet has operated on-chain. A wallet with 18 months of diverse DeFi interactions – lending, trading, bridging, staking across multiple protocols – scores high on experience. Conversely, a wallet created three weeks ago that has done nothing but register agents scores near zero. Experience is hard to accelerate, because it is a function of time as much as activity. An operator cannot age a fresh wallet by transacting intensively for a week and matching the experience score of a genuinely established participant.

Risk Capability

Risk capability measures the behavioral breadth of the owner wallet. Does it interact with a range of DeFi protocols, or does it show narrow, mechanical patterns consistent with a purpose-built fraud wallet? Legitimate DeFi participants accumulate a diverse transaction graph over time – different counterparties, different protocol types, different token categories. Fraud wallets tend to exhibit concentrated patterns: high transaction frequency in a narrow activity type, often with timing patterns that indicate scripted rather than human behavior.

Fraud Probability

Fraud probability is ChainAware’s predictive AI model output – a score between 0.0 and 1.0 representing the likelihood that the owner wallet will engage in fraudulent behavior. This is not a blacklist check. Blacklists are reactive; they flag addresses after fraud has been confirmed. The ChainAware fraud model is predictive: it scores behavioral patterns against 20M+ wallet personas to estimate forward-looking risk, identifying likely fraud actors before they have generated a confirmed fraud record. For a detailed explanation of the machine learning methodology, see our AI-Powered Blockchain Analysis guide.

The Reputation Score applied to the owner wallet produces a single 0-1000 number that feeds into the Agent Trust Score formula as the primary input. A strong owner score (800+) indicates a Sovereign-tier controller with genuine on-chain history. A weak owner score (below 200) flags an Untrusted controller regardless of how clean the agent’s own wallet appears.

Signal 2 – The Feeder Address: Who Funded the Controller?

The feeder address is ChainAware’s most distinctive signal in the Agent Trust Score – and the signal that no competing agent trust platform currently reaches. RNWY surfaces the owner wallet but marks it as informational, non-scoring data. SkyeProfile performs partial operator wallet analysis. Neither traces the funding source of the controller.

ChainAware traces feeder addresses for approximately 38% of indexed agents. That 38% coverage rate reflects the on-chain reality: some owner wallets receive funds from obfuscated sources, some from multiple feeders that cannot be unambiguously attributed, and some from the native chain’s genesis or bridge infrastructure. When the feeder is traceable, the signal is highly informative.

Feeder categories and their trust implications

CEX withdrawal (Binance, Coinbase, Kraken, OKX, and others): A feeder address that is a verified CEX hot wallet implies that the owner wallet’s initial funding came from a centralized exchange withdrawal. CEX withdrawals imply the controller passed KYC somewhere upstream – not necessarily ChainAware’s KYC, but some identity verification process at deposit. This is the strongest positive feeder signal available. ChainAware flags this as FEEDER_CEX_VERIFIED and applies the maximum feeder factor in the scoring formula.

Known fraud operator or mixer: A feeder address that is a confirmed Tornado Cash wallet, ChipMixer output, or address previously flagged in ChainAware’s fraud database propagates that fraud signal directly to the agent score. An owner wallet funded by a mixer is not automatically fraudulent – there are legitimate privacy use cases – but combined with other risk signals it is a strong indicator of deliberate fund obfuscation. Mixers and confirmed fraud feeders apply a hard cap to the Agent Trust Score regardless of how clean the owner wallet’s own transaction history appears.

Unknown or obfuscated feeder: When the feeder cannot be determined, ChainAware applies a penalty to the feeder factor. Obfuscation is not neutral – the absence of a traceable funding source is itself a risk signal. Legitimate operators who funded their owner wallets via normal CEX withdrawals have nothing to hide and produce traceable feeder paths. Operators who deliberately route funds through multi-hop paths to obscure the source are doing so for a reason.

For compliance-oriented DeFi protocols, the feeder analysis also connects directly to AML obligations. Our guide on Blockchain Compliance for DeFi: KYT and AML in 2026 covers the regulatory context in detail. Notably, feeder address analysis extends the transaction monitoring horizon beyond the immediate counterparty – which is precisely what FATF’s Travel Rule guidance asks for in the context of virtual asset transfers.

Signal 3 – The Criminal Record: Rug Pulls, Honeypots, and Prior Fraud

This is the signal that makes the ChainAware Agent Trust Score genuinely unique – and the signal that matters most for DeFi protocol builders who have been operating in the space long enough to know that today’s agent creator is often yesterday’s rug pull operator wearing a fresh wallet.

ChainAware maintains a database built from one year of on-chain pair history and token audit data. Specifically, this database captures:

• Token contracts flagged as honeypots by ChainAware’s algorithmic analysis
• The creator wallet address for each honeypot token
• Liquidity pools where the creator removed funds in patterns consistent with rug pull execution
• The creator wallet address for each rug pull pool

Before computing the Agent Trust Score, ChainAware cross-references both the owner wallet and the feeder address against this database. Any match generates a hard cap on the final score – a ceiling that no other scoring signal can override.

The logic here is direct: a single confirmed rug pull or honeypot in an agent controller’s history is a disqualifying signal for autonomous execution trust. An operator who has previously stolen from retail investors through manufactured liquidity or tax-trap tokens is not a different actor simply because they have registered a new agent identity on ERC-8004. The on-chain history is permanent. The behavioral record cannot be expunged.

As we document in our guide to Rug Pull vs Pump and Dump: How Crypto Fraud Extracts Wealth from Retail Investors, approximately 95% of new pools on PancakeSwap end in rug pulls. Furthermore, the operators behind those pools are not typically first-time offenders – they are repeat actors who rotate wallets between campaigns. Connecting that historical fraud record to new agent registrations is what allows ChainAware to catch the serial fraudster who is simply moving from token launches to agent deployments as the market cycle shifts.

Feeder criminal record: the compounding signal

Criminal record analysis applies not only to the owner wallet but also to the feeder address. Consider the operational pattern of a sophisticated fraud operator:

1. Operator runs rug pull campaigns using Wallet A (primary fraud wallet, now flagged)
2. Operator creates fresh Wallet B with no fraud history
3. Wallet A funds Wallet B – the feeder relationship is recorded on-chain
4. Wallet B registers agents on ERC-8004, presenting a clean owner wallet history
5. Any platform that scores only the owner wallet (Wallet B) misses the connection entirely

ChainAware’s feeder analysis catches step 4. The funding source (Wallet A) has a confirmed rug pull history in our database. Therefore, Wallet B’s agents receive a hard cap score regardless of how clean Wallet B’s own transaction history appears. This is the operational pattern that makes the feeder signal irreplaceable – it is the signal sophisticated actors spend the most effort obscuring, precisely because it is the signal that most reliably connects new operations to old fraud records.

Trust Delegation: How a Strong Owner Legitimises a Fresh Agent Wallet

Agent wallets present a specific challenge for naive scoring approaches. These wallets are frequently created specifically for the agent – they are fresh addresses with no transaction history, no counterparty network, and no behavioral record. A scoring approach that treats wallet age and transaction history as primary inputs would therefore penalise every newly registered agent regardless of the owner’s reputation. That produces low scores for legitimate agents and renders the score less useful as a gate for agentic commerce integrations where new agents are continuously deployed.

ChainAware solves this problem with trust delegation. The owner wallet’s Reputation Score sets a floor for the agent wallet’s effective score. A strong owner partially transfers credibility to the fresh agent wallet. The exact delegation factor depends on feeder availability and the owner’s own fraud status.

# Trust delegation: owner lifts fresh agent wallet score
delegated_floor  = owner_score × delegation_factor

# Delegation factor varies by context:
# - Normal (feeder available, owner clean): 0.6
# - Feeder unknown (obfuscation signal):    0.3
# - Owner fraud-flagged:                    0.1

effective_wallet = max(wallet_score, delegated_floor)

This means a reputable developer deploying their first agent scores appropriately high – even with a fresh payment wallet – because the owner’s 18-month behavioral record delegates trust downward to the new agent wallet. A fraud-flagged owner, by contrast, cannot delegate any meaningful trust regardless of how the fresh agent wallet appears. The delegation factor collapses to near zero, and the agent score reflects the owner’s history rather than the wallet’s lack of it.

Trust delegation also captures the inverse correctly. If an agent wallet has a genuinely clean and established history (because the same operator has deployed agent wallets before), that score is used directly without needing the delegation floor. The formula takes the maximum of the two – the wallet’s own score and the delegated floor from the owner – ensuring that genuine wallet history is never penalised by the delegation mechanism.

This mechanism is unique to ChainAware among agent trust platforms operating on ERC-8004 in 2026. Competing platforms that surface the owner wallet as informational data but do not integrate it into their scoring formula cannot implement delegation – because delegation requires both the owner score and the wallet score to be computed on a comparable scale and combined algorithmically.

Farm Detection: One Operator, Dozens of Agents

Multi-agent orchestration is one of the defining architectural trends in agentic AI for 2026. Orchestrator agents coordinate specialised sub-agents working in parallel – a legitimate pattern that produces significant efficiency gains for complex workflows. However, the same architecture that enables powerful legitimate multi-agent systems also enables a specific attack pattern in agentic commerce: agent farming.

Agent farming is the practice of a single operator registering a large fleet of agents, typically in bulk during a narrow time window, with the goal of:

• Cross-endorsing each other to manufacture reputation scores
• Flooding agent marketplaces with controlled supply to manipulate pricing or availability
• Creating the appearance of ecosystem depth across multiple agent identities controlled by one bad actor
• Operating coordinated fraud campaigns across dozens of agent wallets that each individually appear to have limited exposure

ERC-8004 places no restrictions on how many agents a single owner can register. Consequently, a single wallet can register 500 agents in a single afternoon with no protocol-level friction. Individual agent scoring – which is what every competitor in this space does – is blind to the fleet-level pattern. Each agent scores independently; none of them individually triggers a threshold that reveals the fleet behavior.

ChainAware maintains an owner profile database that tracks agent fleet size per owner across all indexed chains. Owners controlling large numbers of agents receive a farm detection signal that suppresses the score for every agent in their fleet. Furthermore, the specific pattern of same-block registration – multiple agents minted in a single block – carries additional weight, because it indicates automated bulk registration rather than organic deployment over time.

The farm detection signal appears in the API response as the FARM_DETECTED flag. It does not expose the specific threshold that triggered the signal – sharing that threshold would tell operators exactly how many agents they can register before triggering detection. Instead, the flag communicates the category of signal without revealing the calibration.

From a DeFi protocol integration perspective, farm detection is the signal that turns individual agent trust scoring into a fleet-level intelligence system. Agents from the same owner share a trust destiny – if the owner’s fleet pattern is suspicious, every agent in that fleet is suspect regardless of how any individual agent scores in isolation.

EIP-7702 Delegation: The Hidden Controller Problem

EIP-7702 allows Externally Owned Accounts (EOAs) to delegate control to a secondary address for a single transaction or extended period. In the agent context, this means the wallet registered as the ERC-8004 agent owner may not be the wallet actually controlling the agent’s behavior – a secondary delegated address might be executing transactions on behalf of the nominal owner.

ChainAware detects EIP-7702 delegation for agent owner wallets. When detected, the scoring process adds the delegate address to the analysis and takes the lower of the two scores – owner and delegate – as the effective owner score feeding into the Agent Trust Score formula.

This matters because EIP-7702 delegation is a specific mechanism that sophisticated actors can use to obscure the real controlling entity behind an agent. The nominal owner wallet might have a strong reputation score built over many months. The delegate might be a fresh fraud wallet with no history. Without EIP-7702 analysis, the strong nominal owner score masks the fraudulent delegate’s risk profile. With it, the delegate’s low score pulls the effective owner score down to reflect the actual controlling entity.

Approximately 5% of indexed ERC-8004 agents have EIP-7702 delegated ownership, based on ChainAware’s current database. Agents with EIP-7702 delegation are flagged explicitly in the API response as EIP7702_DELEGATED – giving protocol builders the option to apply additional scrutiny to this category regardless of the final numerical score.

The Trust-Aware Agent Integration Pattern

A DeFi protocol that has addressed the trust gap adds one step between the ERC-8004 registry lookup and the transaction execution. That step takes under 100ms, requires one API call, and produces a structured output that the protocol’s access control layer can act on directly.

Agent initiates transaction
  ↓
Resolve agent_id → owner_address + agent_wallet (ERC-8004 registry)
  ↓
GET /erc8004/agent/{chain_id}/{agent_id}/trust-score
  ↓
Response:
  {
    "agent_trust_score": 882,
    "tier": "Sovereign",
    "flags": ["FEEDER_CEX_VERIFIED"]
  }
  ↓
score ≥ protocol_threshold → execute
score < protocol_threshold → reject or route to human review

The threshold is a protocol-level decision. Different use cases warrant different risk tolerances:

The ChainAware Agent Trust Score API integrates directly with the Prediction MCP server, meaning any Claude-based DeFi agent can call the scoring endpoint as a native MCP tool call without custom API integration code. For teams building on the MCP stack, see our Prediction MCP setup guide and our library of 32 ready-made agents that already include agent verification logic.

Additionally, the trust check does not add friction for legitimate agents. A reputable developer deploying their first agent – with a strong owner wallet history and a CEX-verified feeder – scores above 800 through trust delegation even with a brand-new agent payment wallet. The check identifies the fraudulent operator while leaving the legitimate one unrestricted. That asymmetry is the operational definition of a useful trust system.

The Compounding Risk of Getting This Wrong

Human-initiated fraud and agent-initiated fraud differ in one fundamental operational characteristic: velocity. A fraudulent human interacting with your protocol manually can execute perhaps dozens of interactions before detection. A fraudulent agent operating autonomously can execute thousands of interactions in the same period – at machine speed, without sleep, without rate-limit awareness unless you specifically implement it, and with the full behavioral sophistication of the AI model powering it.

Therefore, the cost of a single misidentified agent is not comparable to the cost of a single misidentified human user. The exposure scales with the agent’s operational capacity. A lending protocol that grants a fraudulent agent autonomous execution access for six hours faces losses that scale with the protocol’s TVL and the agent’s transaction rate – not with a single transaction amount.

Traditional fraud detection tools are particularly poorly suited to this environment for reasons we explore in detail in our DeFi Compliance and KYT guide. Rule-based systems flag agent behavior as suspicious because agents naturally exhibit the patterns those rules target: high velocity, cross-category activity, unusual timing distributions. Consequently, you end up blocking legitimate agents while missing sophisticated fraudulent ones that have been engineered to mimic human behavioral patterns.

The compounding risk calculation is straightforward. One fraudulent agent operating undetected for six hours at 100 transactions per minute generates 36,000 protocol interactions. If each interaction involves 0.1 ETH and the fraud extracts 50% of interaction value, that is 1,800 ETH in losses from a single agent integration oversight. The trust check that would have caught this agent costs one API call taking under 100ms. The return on that 100ms is measured in protocol TVL.

For protocols already implementing compliance infrastructure, the Agent Trust Score also extends the KYT monitoring timeline backward – connecting transaction monitoring at the agent level to the historical record of the human behind the agent. Our Web3 Analytics Tools comparison for 2026 covers how agent-level intelligence integrates with broader protocol analytics stacks.

The Five Agent Trust Score Tiers – What Each One Means for Your Protocol

The Agent Trust Score produces a single number between 0 and 1000, mapped to five tiers. Each tier has a distinct operational meaning for DeFi protocol builders – and a distinct set of recommended actions. Understanding what produces each tier helps protocol teams calibrate their threshold decisions correctly.

Tier 5 – Sovereign (800-1000)

Sovereign agents have an established owner wallet with strong on-chain history, a clean or CEX-verified feeder address, no criminal record signals, and no farm detection flags. Trust delegation produces a high effective wallet score even for fresh agent payment wallets. Sovereign-tier agents are suitable for the highest-risk autonomous operations – large-value lending, treasury management, governance participation with material financial consequences. Protocol teams can grant Sovereign agents the same execution permissions they would grant to established protocol participants.

Tier 4 – Trusted (600-799)

Trusted agents have a strong owner wallet, an available and generally clean feeder address, and no hard-cap signals from criminal record checks. The score may be below 800 because the owner wallet has moderate rather than extensive history, or because the agent wallet has minimal activity offset by partial trust delegation. Trusted agents are suitable for standard DeFi integrations – trading agents, yield optimisers, and automated compliance workflows – where the individual transaction risk is moderate and human monitoring is available as a backstop.

Tier 3 – Provisional (400-599)

Provisional agents show mixed signals. The owner wallet may have limited history, the feeder address may be unknown or unverified, or the agent wallet may be very fresh with insufficient trust delegation from the owner score to compensate. Provisional agents should not be granted unsupervised autonomous execution access for high-value operations. However, they are appropriate for lower-risk automated workflows with active monitoring – for example, read-only data queries, low-value token swaps, or agentic onboarding flows where individual transaction size is capped. DeFi protocols integrating Provisional agents should implement transaction volume limits and velocity monitoring as additional safeguards.

Tier 2 – Elevated Risk (200-399)

Elevated Risk agents have weak owner history, obfuscated feeder addresses, soft farm detection signals, or agent wallets that score poorly even after trust delegation. These agents should not be permitted autonomous financial execution. If a protocol needs to serve Elevated Risk agents – for example, in a permissionless DEX context – transaction size limits, velocity caps, and real-time monitoring should all be active. The FEEDER_UNKNOWN flag on an Elevated Risk agent is a particularly notable combination: it indicates both limited owner history and deliberate funding obfuscation, suggesting a higher likelihood of coordinated fraud activity.

Tier 1 – Untrusted (0-199)

Untrusted agents have active fraud signals, confirmed rug pull or honeypot history, confirmed farm detection, sanctioned address exposure, or blacklisted repeat offender status. These agents should not receive autonomous execution access under any circumstances. The score is not borderline – it reflects definitive fraud signals from immutable on-chain history. Untrusted agents attempting to access your protocol should be blocked at the access control layer before any transaction reaches the execution layer. Furthermore, DeFi teams running compliance programs may want to log Untrusted agent interaction attempts as part of their AML reporting, as these attempts represent potential fraud activity on record. For the full compliance context, see our MiCA Compliance for DeFi learn page.

How ChainAware Compares to Other Agent Trust Platforms in 2026

The agent trust scoring market emerged rapidly alongside ERC-8004’s mainnet launch in January 2026. Several platforms have moved quickly to stake positions in the space. Understanding the differentiation between them matters for DeFi protocol builders choosing integration partners.

RNWY is the most established competitor in the ERC-8004 space and uses a sophisticated review-quality analysis that detects coordinated fake review patterns. However, their core methodology solves fake reviews, not fake owners. ChainAware solves fake owners – a harder problem with higher-stakes implications for autonomous execution trust. Both signals are complementary; they are not substitutes for each other.

AXIS T-Score is entirely off-chain – it scores agent runtime performance across 11 behavioral dimensions rather than on-chain ownership identity. This makes it useful for evaluating how well an agent executes tasks, but irrelevant for trust decisions about the human behind the agent. For a protocol deciding whether to grant autonomous execution access, AXIS covers a different question than ChainAware does.

The feeder address, criminal record, and trust delegation signals are currently unique to ChainAware across all indexed agent trust platforms. Those signals require a database of over one year of on-chain pair history, a token audit data pipeline, and a predictive fraud model trained on 20M+ wallet personas – infrastructure that takes years to build and cannot be replicated quickly. Additionally, for more context on how ChainAware positions against broader analytics alternatives, see our Web3 Analytics Tools Comparison for DeFi Dapps in 2026.

The moat is the data, not the formula

ChainAware publishes the categories of signals that feed into the Agent Trust Score. However, the exact weights, thresholds, and model coefficients are not published – not because the methodology is proprietary for competitive reasons, but because publishing thresholds would allow bad actors to calibrate their behavior to stay just below each detection cap.

More importantly, the real moat is not the formula. The moat is the data. An operator who knows every weight and threshold in the Agent Trust Score formula still cannot change their on-chain history. A wallet that created a honeypot token in November 2025 cannot remove that event from the blockchain. A feeder address that funded rug pull operators throughout 2025 cannot alter its transaction graph. The formula can be known. The data cannot be changed. That asymmetry is what makes on-chain behavioral intelligence a durable trust infrastructure rather than a gameable reputation system.

Frequently Asked Questions

What chains does the Agent Trust Score cover?

ChainAware’s Agent Trust Score indexes ERC-8004 agents across Ethereum mainnet, BSC (BNB Chain), Base, and Avalanche C-Chain, with Mantle in progress. These five chains cover the majority of ERC-8004 registry activity. The owner wallet and feeder analysis draws on ChainAware’s broader behavioral intelligence database, which covers 8 blockchains total including Polygon, TON, TRON, and HAQQ.

How long does the Agent Trust Score API take to respond?

The Agent Trust Score API returns results in under 100ms for agents already in the ChainAware database. First-time scoring of a newly registered agent may take slightly longer as the owner and feeder addresses are resolved and scored. Pre-scoring of agents during indexing ensures that the vast majority of ERC-8004 agents in the registry return sub-100ms scores at query time.

Does the Agent Trust Score require any PII or KYC data?

No. The Agent Trust Score is derived entirely from public on-chain data. No personal information is collected, no identity verification is required, and no data is stored beyond what is already publicly available on the blockchain. This makes the score compatible with DeFi’s privacy-first ethos and compliant with GDPR and similar privacy regulations by design.

Can an agent improve its score over time?

Yes – through the owner wallet’s behavioral history, not through the agent wallet itself. As the owner wallet accumulates genuine on-chain experience, interacts with a broader range of protocols, and maintains a clean fraud probability score, the Reputation Score feeding into the Agent Trust Score improves. Trust delegation then carries that improved score to the agent wallet. However, criminal record signals (rug pull history, honeypot creation) are permanent hard caps – they do not improve over time because the underlying on-chain events are immutable.

What happens when an agent is transferred to a new owner?

ERC-8004 agents are ERC-721 NFTs and can be transferred between wallets. When ChainAware detects an ownership transfer, the Agent Trust Score recalculates using the new owner wallet’s behavioral history. This is intentional: the trust score tracks the current controlling entity, not the original registrant. Consequently, an agent cannot inherit a previous owner’s strong score after transfer – each new owner is scored from their own on-chain history.

How does Agent Trust Score integrate with the Prediction MCP?

The Agent Trust Score is available as a native tool through ChainAware’s Prediction MCP server. Any Claude-based agent can call agent_trust_score(chain_id, agent_id) as a natural language tool call, receiving the structured score and flags response without custom API integration code. For protocol teams building on the MCP stack, this means agent verification can be added to any existing MCP-connected workflow in minutes rather than days.

Is the Agent Trust Score different from the Wallet Reputation Score?

The Agent Trust Score uses the same 0-1000 scale and the same underlying Reputation Score formula as ChainAware’s Wallet Reputation Score. However, it applies that formula to multiple addresses simultaneously (owner wallet, agent wallet, feeder address) and combines them using trust delegation logic and fleet-level farm detection signals that do not exist in the standalone Wallet Reputation Score. The two scores are directly comparable on the same scale – a wallet Reputation Score of 750 and an Agent Trust Score of 750 represent the same trust tier.

How does ChainAware handle agents with no traceable feeder address?

When the feeder address cannot be determined – either because the owner wallet was funded through multi-hop paths that obscure the source, or through infrastructure (bridges, faucets) that does not produce an attributable single feeder – ChainAware applies a feeder-unknown penalty to the Agent Trust Score. This penalty reflects the information asymmetry: legitimate operators funded through normal CEX withdrawals produce traceable feeder paths; operators who route funds to obscure the source are doing so for a reason. The penalty is not a hard cap – a very strong owner wallet and clean criminal record can partially offset it. Nevertheless, unknown feeder remains a risk signal that appears in the API response as the FEEDER_UNKNOWN flag.

What does a DeFi credit scoring integration look like alongside Agent Trust Score?

For lending protocols specifically, Agent Trust Score and DeFi credit scoring serve complementary functions. The Agent Trust Score answers “should this agent be permitted to interact with my protocol at all?” – a gate decision. The DeFi credit score answers “given that this agent is permitted, what collateral ratio and interest rate tier should apply to its lending activity?” – a parameterisation decision. Running both checks in sequence gives lending protocols the most complete picture: a verified legitimate agent operating at its correct creditworthiness tier.

Further Reading

• Agent Trust Score – Complete Methodology – the full technical explanation of how the score is computed, including all five scoring layers and flag definitions
• Web3 Wallet Auditing Providers in 2026 – the complete landscape of wallet intelligence providers, from raw data to actionable predictions
• AI-Powered Blockchain Analysis for Crypto Security – how ChainAware’s fraud prediction model achieves 98% accuracy
• Rug Pull vs Pump and Dump – the fraud patterns that feed the Agent Trust Score criminal record database
• Blockchain Compliance for DeFi: KYT and AML Guide – regulatory context for DeFi protocol compliance in 2026
• DeFi Credit Score Platforms Compared – how to combine agent trust verification with borrower creditworthiness assessment
• Prediction MCP Setup Guide – add ChainAware behavioral intelligence to any Claude agent in minutes
• 32 Ready-Made Agents – pre-built Claude agents including agent verification, fraud detection, and compliance screening
• Web3 Analytics Tools for Dapps: Complete Comparison – where agent trust scoring fits in the broader DeFi analytics stack
• Blockchain Data Providers for AI Agents – the data infrastructure layer that feeds agent intelligence systems

ChainAware.ai is the Web3 Agentic Growth Infrastructure – behavioral intelligence for DeFi protocols, AI agents, and individual crypto users. 20M+ wallet personas, 98% fraud detection accuracy, <100ms API latency across 8 blockchains. Try free at chainaware.ai.

The post The First Step in Agentic Commerce Isn’t Integration. It’s Trust. first appeared on ChainAware.ai.

ChainAware was named in CB Insights’ AI Fraud Prevention Market Map alongside Chainalysis, Elliptic, and TRM Labs – and remains the only Web3 AI token across all 200+ companies in that list. The 32 sub-agents documented here are the operational engine behind that recognition: real, deployed tools that DeFi protocols, compliance teams, launchpads, DAOs, and AI agent developers use in production today. Every agent is open-source, MIT-licensed, and available at github.com/ChainAware/behavioral-prediction-mcp .

This article classifies all 32 agents into two functional categories – Fraud Tech and Growth Tech – and for each agent provides a precise description, concrete use case, and the specific trigger conditions that signal when a team needs it. Use this as your reference guide for selecting, combining, and deploying ChainAware’s agent suite.

In This Article

• Two Categories – Fraud Tech and Growth Tech
• The Complete Classification Table – All 32 Agents
• Fraud Tech Agents – 17 Agents, Complete Reference
• Growth Tech Agents – 15 Agents, Complete Reference
• How Agents Compose Into Pipelines
• Getting Started – Integration in Three Steps
• Frequently Asked Questions

Two Categories – Fraud Tech and Growth Tech

ChainAware’s 32 agents divide into two functional categories that reflect the platform’s core thesis: the same behavioral data that prevents fraud also drives growth. Both categories draw from the same underlying Prediction MCP tools and the same 20M+ wallet persona database. The distinction lies in what question each agent answers and what action it enables.

Fraud Tech agents answer: “Can we trust this wallet, contract, token, or transaction?” They protect protocols from losses, enforce AML compliance, prevent Sybil attacks, and screen counterparties before execution. Consequently, Fraud Tech agents operate primarily at the gate – before onboarding, before transactions, before token distributions, before listing decisions. Their outputs are verdicts: allow, block, flag, reject, or escalate.

Growth Tech agents answer: “Now that we know this wallet is legitimate, how do we convert it, retain it, and grow it?” They turn behavioral intelligence into personalized acquisition, onboarding, conversion, and retention decisions. Moreover, Growth Tech agents operate primarily post-gate – after a wallet passes initial screening, they determine how to engage it most effectively. Their outputs are recommendations: which product to surface, which message to send, which onboarding flow to show, which upsell to offer.

Furthermore, both categories share a fraud gate: every Growth Tech agent checks probabilityFraud before generating any recommendation and blocks output for high-risk wallets. This means the categories are not sequential stages but parallel layers – fraud protection runs continuously across every growth decision. For the foundational framework explaining why behavioral intelligence is essential for both fraud prevention and growth, see our Web3 Behavioral User Analytics guide .

The Complete Classification Table – All 32 Agents

The table below lists every agent with its category, primary MCP tool, supported networks, and core function. Agents are sorted by category, then by specificity – from broad-purpose agents to narrow specialists. Use this as your quick-reference lookup before reading the detailed descriptions that follow.

#	Agent	Category	Primary Tool	Networks	Core Function
1	fraud-detector	Fraud Tech	predictive_fraud	ETH BNB POLYGON TON BASE TRON HAQQ	Wallet fraud probability (98% accuracy) + 19 AML forensic flags
2	rug-pull-detector	Fraud Tech	predictive_rug_pull	ETH BNB BASE HAQQ	90.1% rug pull prediction – contract + deployer behavioral analysis
3	aml-scorer	Fraud Tech	predictive_fraud	ETH BNB POLYGON TON BASE TRON HAQQ	AML score (0-100) with full forensic flag breakdown
4	trust-scorer	Fraud Tech	predictive_fraud	ETH BNB POLYGON TON BASE TRON HAQQ	Trust score (0.00-1.00) = 1 − fraud probability. Composable building block
5	sybil-detector	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Batch Sybil detection – wallet farms, coordinated attacks, proxy voting fraud
6	governance-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	DAO voter tier (Core Contributor → Disqualified) + voting weight multiplier
7	counterparty-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Pre-transaction Safe / Caution / Block verdict in a single API call
8	compliance-screener	Fraud Tech	Orchestrator	Multi-chain via sub-agents	MiCA-aligned PASS / EDD / REJECT with full documented evidence trail
9	transaction-monitor	Fraud Tech	predictive_behaviour + predictive_rug_pull	ETH BNB BASE HAQQ SOL + fallback	Real-time ALLOW / FLAG / HOLD / BLOCK for autonomous agent pipelines
10	token-launch-auditor	Fraud Tech	predictive_rug_pull + predictive_fraud	ETH BNB BASE HAQQ	Launchpad listing audit → APPROVED / CONDITIONAL / REJECTED + safety badge
11	airdrop-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Batch airdrop eligibility – filters bots, ranks eligible wallets by reputation
12	rwa-investor-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	RWA investor suitability → QUALIFIED / CONDITIONAL / REFER_TO_KYC / DISQUALIFIED
13	gamefi-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	P2E bot farm and multi-account cheater detection + player tier classification
14	credit-scorer	Fraud Tech	credit_score	ETH	Crypto credit score (1-9) combining fraud probability + social graph analysis
15	lending-risk-assessor	Fraud Tech	predictive_behaviour + credit_score	ETH BNB BASE HAQQ SOL	Borrower risk grade (A-F) + recommended collateral ratio + interest rate tier
16	portfolio-risk-advisor	Fraud Tech	predictive_rug_pull + token_rank_single	ETH BNB BASE HAQQ	Portfolio rug pull scan → grade A-F + prioritized exit/reduce plan
17	agent-screener	Fraud Tech	predictive_fraud + predictive_behaviour + predictive_rug_pull	ETH BNB BASE HAQQ SOL + fallback	AI agent trust score (0-10) screening agent wallet + feeder wallet
18	wallet-auditor	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Complete 22-dimension Web3 Persona – fraud + behavioral + personalization
19	reputation-scorer	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Reputation score (0-1000) = experience × risk_capability × (1 − fraud)
20	wallet-ranker	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Global wallet rank from experience, total points, age, transaction count
21	whale-detector	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Whale tier (Mega / Whale / Emerging) + Active/Dormant status + domain
22	ltv-estimator	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	12-month revenue potential (USD range) from behavioral + risk signals
23	lead-scorer	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Lead score (0-100) + Hot/Warm/Cold/Dead + recommended outreach angle
24	wallet-marketer	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Hyper-personalized marketing message (max 20 words) from on-chain signals
25	platform-greeter	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Platform-specific welcome message (max 35 words) – different per platform
26	onboarding-router	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Onboarding flow decision – Beginner / Intermediate / Skip from real experience
27	defi-advisor	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Personalized DeFi product recommendations (3 tiers) by experience + risk
28	upsell-advisor	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Upgrade readiness (0-100) + next product + trigger event + conversion probability
29	cohort-analyzer	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Batch behavioral cohort segmentation – 8 cohorts + per-cohort strategy
30	token-ranker	Growth Tech	token_rank_list	ETH BNB BASE SOL	Token discovery by community strength – AI / RWA / DeFi / DeFAI / DePIN
31	token-analyzer	Growth Tech	token_rank_single + predictive_fraud	ETH BNB BASE SOL	Single-token deep-dive: community rank + top holder profiles + fraud screening
32	marketing-director	Growth Tech	Orchestrator (7 specialist agents)	All networks via sub-agents	Full-cycle campaign orchestrator → complete Marketing Campaign Brief

Fraud Tech Agents – 17 Agents, Complete Reference

ChainAware’s Fraud Tech agents protect Web3 protocols from the full spectrum of on-chain threats: wallet fraud, rug pulls, money laundering, Sybil attacks, governance manipulation, P2E cheating, and fraudulent AI agents. Together, they cover every point in the protocol lifecycle where malicious actors attempt to extract value – from the moment a wallet first connects to the moment a transaction executes. According to FATF’s Virtual Assets Recommendations , the compliance requirements for crypto asset service providers now demand pre-execution risk assessment that legacy forensic tools were never designed to deliver. ChainAware’s Fraud Tech agents fill that gap with predictive behavioral intelligence rather than reactive forensic lookup.

Moreover, these agents share a critical structural advantage over traditional blockchain forensics: they analyze behavioral patterns across 20M+ wallet personas rather than matching against static blocklists. Professional fraud operators deliberately evade blocklist-based tools by using fresh wallets and clean contract code. They cannot, however, mask their behavioral fingerprint – the pattern of on-chain activity that identifies an operator regardless of which specific address they use today. This is why ChainAware achieves 98% fraud detection accuracy on ETH where forensic tools frequently miss sophisticated operators. For the complete technical comparison, see our Forensic vs AI-Powered Analytics guide .

1. chainaware-fraud-detector

The flagship fraud detection agent calls predictive_fraud on any wallet address and returns a fraud probability score, wallet status (Not Fraud / Fraud / New Address), OFAC sanctions check, and 19 AML forensic flags covering mixers, darknet transactions, phishing wallets, fake token creation, money laundering patterns, cybercrime associations, and more. Accuracy reaches 98% on ETH and 96% on BNB, backtested against CryptoScamDB – the largest publicly available database of documented crypto fraud incidents. Coverage spans 7 networks: ETH, BNB, POLYGON, TON, BASE, TRON, and HAQQ.

Use Case: A DeFi lending protocol screens every wallet requesting a loan before processing the application. The team integrates chainaware-fraud-detector into its onboarding API – each new wallet receives a fraud probability score and forensic flag check in under one second. Wallets scoring above 0.70 are automatically declined. Wallets between 0.40 and 0.70 route to enhanced due diligence. Wallets below 0.20 pass to the standard lending flow. The same agent works equally well for exchange KYC pre-screening, NFT allowlist vetting, and airdrop participant verification.

When Is It Required: Deploy chainaware-fraud-detector whenever a protocol accepts wallet connections from unknown participants – particularly before any value transfer, credit extension, or whitelist grant. It is specifically required when a protocol falls under MiCA, AML5D, or equivalent regulation that mandates pre-onboarding risk assessment. Additionally, it is required before running any Growth Tech agent on a wallet – the fraud gate in chainaware-wallet-marketer and chainaware-ltv-estimator calls this agent’s underlying tool before generating any recommendation. For the complete implementation methodology, see our Fraud Detector guide .

2. chainaware-rug-pull-detector

Analyzes smart contracts, liquidity pools, and token launches for rug pull risk before any capital is deployed. The agent runs predictive_rug_pull on the contract address and predictive_fraud on the deployer wallet, combining both into a unified verdict. Critically, the deployer fraud score can escalate the overall verdict by one tier – a contract scoring 0.35 (Medium risk) paired with a deployer scoring 0.72 (High risk) produces a combined High Risk verdict. This escalation catches the most dangerous category of rug pulls: professionally deployed clean contracts by operators with documented fraud histories on other wallets. Accuracy on the PancakeSwap V2 dataset reaches 90.1%, covering $569M in documented rug pull losses from weeks 1-20 of 2026. Networks supported: ETH, BNB, BASE, HAQQ.

Use Case: A DEX launchpad reviews 50 new token submissions per week. Without automated screening, each review requires a developer to manually inspect contract code and trace the deployer wallet – a process taking 30-60 minutes per token. With chainaware-rug-pull-detector, the launchpad runs all 50 contracts in batch mode and receives a ranked risk table in minutes. Contracts scoring above 0.80 are automatically rejected. Contracts between 0.50 and 0.80 require manual review with specific red flags already identified. Contracts below 0.20 proceed to standard listing.

When Is It Required: Use chainaware-rug-pull-detector before listing any token on a DEX, before depositing LP into any new pool, before investing in any IDO or pre-sale, and before any yield vault strategy deploys capital into a new protocol. It is specifically required for launchpad teams that need a standardized, reproducible audit process rather than ad hoc developer reviews. It pairs with chainaware-token-launch-auditor when a full public-facing audit report with a safety badge is needed. For the detailed comparison against GoPlus, Token Sniffer, and Honeypot.is, see our Rug Pull Detection Tools guide .

3. chainaware-aml-scorer

Calculates a structured AML score (0-100) using a two-branch logic that separates forensic compliance from probabilistic fraud risk. If any forensic flag is present – mixer usage, sanctioned entity association, stolen funds link, darknet transaction, ransomware wallet interaction – the AML score is 0 regardless of the fraud probability score. This hard-zero rule reflects regulatory reality: a forensic flag requires human review and escalation regardless of the overall risk probability. When forensics are clean, the AML score equals (1 − probabilityFraud) × 100, providing a continuous risk gradient for compliance tiering. The agent returns the complete forensic breakdown alongside the score, producing output that is audit-ready for regulatory review under MiCA and equivalent frameworks.

Use Case: A crypto exchange onboards 500 new wallets per day and must document AML screening decisions for regulatory reporting. Previously, the compliance team ran manual checks on wallets flagged by a basic blocklist – a process that missed sophisticated operators and created a documentation backlog. With chainaware-aml-scorer, every onboarding wallet receives an automated AML report in under one second. Wallets scoring 0 (forensic flag detected) escalate to the compliance team with the specific flags identified. Wallets scoring 71-100 receive automated approval documentation. Wallets in the 41-70 range trigger enhanced due diligence with a specific set of additional checks, creating a complete and auditable compliance trail for every onboarded wallet.

When Is It Required: Deploy chainaware-aml-scorer for any platform falling under AML/CFT regulatory requirements – exchanges, OTC desks, lending protocols, and any DeFi platform accepting significant TVL from institutional wallets. It is also required when chainaware-compliance-screener is the orchestrating agent, since compliance-screener calls aml-scorer as one component of its structured MiCA-aligned report. See our MiCA Compliance guide for the full regulatory compliance stack.

4. chainaware-trust-scorer

Returns a single trust score using one formula: Trust Score = 1 − fraud_probability. The output ranges from 0.00 (confirmed fraud) to 1.00 (zero fraud probability). Designed as a composable building block rather than a standalone product, trust-scorer feeds into other calculations across the agent suite: reputation score uses it as the base fraud penalty, AML score uses it as the clean-forensics branch, governance vote weighting multiplies by it, and marketing campaign gates use it as a minimum threshold before message generation. Covers 7 networks via predictive_fraud. Response time is sub-100ms by design, making it the fastest agent in the suite.

Use Case: A developer building a custom reputation system for their DeFi protocol needs a standardized trust signal to combine with their own on-chain activity metrics. Rather than building a fraud detection model from scratch, they integrate chainaware-trust-scorer as the fraud component and combine it with their own activity score. The resulting composite score inherits ChainAware’s 98% fraud accuracy while adding protocol-specific activity signals that ChainAware’s general model does not capture. The trust score’s mathematical cleanliness – it is simply the complement of fraud probability – makes it easy to incorporate into any scoring formula.

When Is It Required: Use chainaware-trust-scorer whenever a custom scoring formula needs a standardized, high-accuracy fraud component – governance vote weighting, airdrop allocation, lending collateral ratios, and marketing campaign eligibility gates all benefit from incorporating the trust score as a fraud signal. It is the recommended starting point for teams building composite scores rather than using a pre-built agent, since its output is mathematically clean and directly interpretable.

5. chainaware-sybil-detector

Batch-screens wallet lists for Sybil attacks, coordinated voting fraud, and wallet farm operations. Beyond individual wallet scoring, the agent applies four pattern detection rules across the full submitted set: a cluster flag triggers when 10%+ of wallets share experience scores within ±0.2 points and were created in the same approximate period – the signature of a coordinated wallet farm. A fraud concentration flag triggers when 20%+ of voters show fraud probability above 0.25. A new wallet surge flag triggers when 30%+ of wallets have experience below 1.5. A uniform risk profile flag triggers when 60%+ share identical behavioral categories, indicating coordination rather than organic community diversity. Each wallet is classified as ELIGIBLE, REVIEW, or EXCLUDE, and the cleaned voter list is ready for Snapshot or on-chain governance integration.

Use Case: A DAO preparing a governance vote on a $2M treasury allocation notices unusual activity: 400 new wallets registered in the 48 hours before the vote, all with minimal transaction history. Running chainaware-sybil-detector on the full voter list identifies 312 of those 400 wallets as part of a coordinated new-wallet cluster, disqualifying them from the vote. The attack is neutralized before it reaches quorum. The cleaned voter list shows genuine community support from 89 ELIGIBLE voters, and the vote proceeds with integrity intact.

When Is It Required: Run chainaware-sybil-detector before any governance vote controlling significant treasury funds, parameter changes, or upgrade authority. It is specifically required before Snapshot votes for DAOs with public token distribution, before on-chain governance proposals reaching quorum thresholds, and before any delegation validation process where vote weight can be amplified through coordinated proxy delegation. For the complete governance protection framework, see our Governance Screeners guide .

6. chainaware-governance-screener

DAO voter screening with four-tier classification and voting weight calculation. The agent assigns each wallet to one of five tiers: Core Contributor (experience ≥ 8, fraud ≤ 0.10, protocols ≥ 5 → 2.0× multiplier), Active Member (experience ≥ 5, fraud ≤ 0.25, protocols ≥ 2 → 1.5×), Participant (experience ≥ 2, fraud ≤ 0.40 → 1.0×), Observer (new address or experience < 2 with low fraud → 0.5×), and Disqualified (fraud gate fails → 0.0×). Within each tier, the multiplier adjusts downward for elevated fraud probability. Three governance models are supported: token-weighted, reputation-weighted (ChainAware reputation score as direct weight), and quadratic (multiplier applies to square root of token balance).

Use Case: A DeFi protocol wants to implement reputation-weighted governance to counteract plutocracy – the tendency of token-weighted systems to concentrate governance power in the largest holders regardless of protocol engagement. Using chainaware-governance-screener in reputation-weighted mode, every voter’s influence is determined by behavioral quality rather than token balance alone. A Core Contributor holding 1,000 tokens has more governance weight than a dormant whale holding 100,000 tokens but showing no protocol engagement. The result is governance that rewards genuine contributors rather than passive large holders.

When Is It Required: Deploy chainaware-governance-screener for any DAO that needs to validate voter quality before a proposal goes live. It is particularly required for protocols implementing reputation-weighted or quadratic voting models, for DAOs with public token distributions vulnerable to Sybil accumulation, and for any governance system where a single bad-faith actor could acquire enough voting power to pass a malicious proposal. It works alongside chainaware-sybil-detector – the Sybil detector identifies coordinated wallet farms, while governance-screener classifies remaining legitimate voters by quality tier.

7. chainaware-counterparty-screener

Pre-transaction safety agent optimized for minimum latency and maximum decisiveness. A single predictive_behaviour call retrieves both the fraud probability and the behavioral context needed for ambiguous cases – eliminating the two-call pattern that adds latency to pre-transaction flows. The verdict logic applies decisive rules first (confirmed fraud or forensic flag → immediate Block; fraud probability ≤ 0.15 → immediate Safe) and contextual rules only for the 0.16-0.70 range. Transaction-type context adjusts the risk assessment: approve actions receive a 1.3× risk multiplier, bridge and liquidity actions 1.2×, stake actions 0.9×. Compact mode returns a single line for autonomous agent pipelines.

Use Case: A DeFi aggregator routes user transactions across multiple protocols and counterparties. Before executing any multi-hop route, the aggregator’s AI agent calls chainaware-counterparty-screener on every intermediate counterparty address. A Block verdict causes the agent to find an alternative route avoiding the flagged address. A Caution verdict triggers additional monitoring for the transaction. A Safe verdict allows execution to proceed normally. The entire screening adds under 200ms to the routing decision – negligible for a user experience that already involves multi-second blockchain confirmation times.

When Is It Required: Use chainaware-counterparty-screener immediately before signing any transaction with an unknown counterparty – particularly token approvals (highest risk action type), LP deposits (contract risk), bridge transactions (irreversible cross-chain exposure), and high-value transfers. For autonomous AI agents executing transactions without human review, this agent provides the fraud gate that substitutes for human judgment. It pairs naturally with chainaware-transaction-monitor: counterparty-screener handles the pre-transaction check on specific addresses, while transaction-monitor handles real-time pipeline risk scoring across sender, receiver, and contract simultaneously.

8. chainaware-compliance-screener

The most comprehensive compliance agent in the suite – a MiCA-aligned orchestrator sequencing AML scoring, fraud detection, and transaction risk assessment into a single structured Compliance Report with a three-tier verdict: PASS, ENHANCED DUE DILIGENCE, or REJECT. Unlike the individual specialist agents, compliance-screener is specifically designed to produce documentation: every signal, every flag, every threshold applied is recorded in the output, creating an audit trail that compliance officers can present to regulators. The verdict structure mirrors MiCA’s layered compliance approach – PASS wallets proceed normally, EDD wallets receive additional checks before service, REJECT wallets are declined with specific reasons documented.

Use Case: A crypto asset service provider (CASP) operating under MiCA needs to document its compliance process for every customer onboarding. Manual KYC combined with blockchain forensics produces reports taking hours per customer and lacking standardization. With chainaware-compliance-screener, every onboarded wallet receives an automated, structured Compliance Report in under 5 seconds – covering sanctions screening, AML forensic flags, behavioral fraud risk, and transaction pattern analysis. The report format is consistent across all wallets, making regulatory reporting systematic rather than ad hoc. EDD cases are automatically flagged with the specific signals that triggered the enhanced review requirement.

When Is It Required: Deploy chainaware-compliance-screener for any platform regulated under MiCA, AML5D, FinCEN guidance, or equivalent frameworks requiring documented pre-onboarding risk assessment. It is specifically required when a compliance team needs to demonstrate to regulators that their screening process is systematic, documented, and applied consistently – not selectively or manually. The agent is also the right choice for institutional DeFi platforms serving accredited investors where documented compliance is a prerequisite for institutional capital access. For the complete regulatory compliance cost comparison, see our MiCA Compliance guide .

9. chainaware-transaction-monitor

Real-time transaction risk scoring designed for autonomous AI agent pipelines rather than human compliance review. The agent screens sender, receiver, and contract address simultaneously, computes a composite risk score (0-100) using weighted contributions from each address, applies action-type multipliers (approve 1.3×, bridge and liquidity 1.2×, stake 0.9×, unknown 1.1×), and returns a machine-actionable ALLOW / FLAG / HOLD / BLOCK signal. Override rules immediately produce a BLOCK regardless of composite score whenever sender or receiver carries confirmed fraud status or any AML forensic flag. Compact mode returns a single-line signal for mempool monitoring and high-frequency agent pipelines where sub-50ms response is required.

Use Case: A DeFi trading bot executes 200+ transactions per day across multiple protocols. Without transaction monitoring, the bot has no way to detect when it is being routed through a fraudulent intermediary or interacting with a compromised contract. With chainaware-transaction-monitor as a pre-execution hook, every transaction is screened in under 100ms before signing. BLOCK signals cause the bot to abort the transaction and find an alternative path. FLAG signals execute but generate a compliance log entry for review. Over a 30-day period, the monitoring prevents the bot from executing 14 transactions with BLOCK-level counterparties – including two interactions with wallet addresses later confirmed as hack-related by blockchain investigators.

When Is It Required: Deploy chainaware-transaction-monitor for any autonomous AI agent executing blockchain transactions without per-transaction human approval. This specifically includes DeFi trading bots, yield optimization agents, automated treasury management systems, and any AI agent operating under the emerging ERC-8004 standard for on-chain agent identity. It is also required for any protocol needing ongoing post-onboarding transaction screening – complementing chainaware-fraud-detector (which handles one-time onboarding checks) with continuous monitoring of user activity. For the complete integration guide, see our Transaction Monitoring guide .

10. chainaware-token-launch-auditor

Launchpad listing audit agent combining rug pull detection on the contract with full fraud and behavioral analysis on the deployer wallet. The output includes a composite Launch Safety Score, a public-facing safety badge suitable for embedding on listing pages, and specific conditions the launchpad should impose – mandatory LP lock periods, restricted admin key permissions, or vesting schedule requirements. The three-tier verdict (APPROVED, CONDITIONAL, REJECTED) gives launchpad teams a standardized decision framework they can communicate publicly to investors. CONDITIONAL listings include explicit conditions that, if met, convert the listing to APPROVED.

Use Case: An IDO launchpad receives a new project application for a DeFi token on BNB. The applying team has a polished website, a detailed whitepaper, and a professionally written smart contract that passes standard code review. However, chainaware-token-launch-auditor detects that the deployer wallet has previously deployed three tokens on ETH, all of which experienced LP withdrawal events within 72 hours of launch – a behavioral signature of serial rug pull operations. The contract score is 0.28 (Medium) but the deployer score is 0.81 (Critical), producing a REJECTED verdict. The launchpad declines the listing. Three weeks later, the same team launches the token on an unscreened DEX, where it rugs within 36 hours.

When Is It Required: Run chainaware-token-launch-auditor before approving any token listing on a launchpad or DEX maintaining listing standards. It is specifically required for platforms displaying a safety badge or endorsement alongside listed tokens – without auditor-backed evidence, any safety claim creates legal and reputational liability. The agent is also required for any accelerator or incubator program vetting projects before providing funding or platform access. It works as a pre-listing screening gate for token sale platforms where retail investors rely on the platform’s due diligence.

11. chainaware-airdrop-screener

Batch airdrop eligibility engine that filters fraud wallets, bots, and Sybil clusters from token distribution lists, then ranks eligible wallets by ChainAware’s reputation formula for merit-based allocation. Five disqualification rules apply in order: fraud probability above 0.70 → HIGH FRAUD disqualified; confirmed fraud status → CONFIRMED FRAUD disqualified; new address with fraud above 0.40 → SUSPICIOUS NEW disqualified; new address with zero experience and no categories → BOT/FRESH disqualified; any AML forensic flag → AML FLAG disqualified. Surviving wallets receive a reputation score calculated as (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability) and are assigned allocation multipliers from 0.5× (Low Score) to 4× (Elite). When a token budget is provided, the agent calculates exact per-wallet token allocations ready to plug into a Merkle tree contract.

Use Case: A DeFi protocol distributes 10 million tokens across 5,000 wallet addresses collected through a six-week quest campaign. Without screening, ChainAware’s analysis of similar campaigns finds that approximately 84% of campaign participants are ghost wallets – addresses with zero real engagement that bot operators control mechanically. Running chainaware-airdrop-screener on the 5,000 addresses disqualifies 3,420 as bots, fraud, or suspicious new wallets. The remaining 1,580 eligible wallets are ranked by reputation score and receive allocations scaled from 0.5× to 4× of the base amount. The protocol distributes tokens to genuine community members, avoids immediate sell pressure from farming wallets, and creates a foundation of quality token holders.

When Is It Required: Run chainaware-airdrop-screener before every token distribution event – regardless of campaign size. It is specifically required for distributions above 100,000 USD equivalent where bot farming has high economic incentive, for any distribution including vesting where recipient quality affects long-term token price stability, and for governance token airdrops where recipient quality directly affects the quality of future governance participation. The agent pairs naturally with chainaware-sybil-detector (which identifies coordination patterns before disqualification) and chainaware-reputation-scorer (which provides the ranking formula for tiered allocations).

12. chainaware-rwa-investor-screener

Real World Asset investor suitability screening assessing three dimensions simultaneously: AML/fraud compliance (40% weight), investor sophistication via on-chain experience score (35%), and risk profile alignment against the RWA’s declared risk tier (25%). The composite Suitability Score (0-100) maps to four tiers: QUALIFIED (full access, standard caps), CONDITIONAL (reduced cap, enhanced monitoring), REFER_TO_KYC (on-chain profile insufficient, route to manual KYC), and DISQUALIFIED (fraud gate, AML flag, or confirmed fraud). Recommended investment caps are tied to experience level within each tier – a QUALIFIED Sophisticated investor has no cap, while a QUALIFIED Intermediate investor caps at $25,000. Three RWA risk tiers define minimum experience thresholds: conservative (≥ 2.0), moderate (≥ 4.0), aggressive (≥ 6.5).

Use Case: A tokenized real estate platform onboards investors for a $50M moderate-risk RWA offering. Traditional KYC takes 3-5 days per investor. The platform needs to process 2,000 investor applications in a two-week window before the offering closes. Chainaware-rwa-investor-screener processes all 2,000 wallets in batch mode in under 10 minutes, classifying 1,240 as QUALIFIED, 380 as CONDITIONAL, 210 as REFER_TO_KYC, and 170 as DISQUALIFIED. The 170 disqualified wallets are excluded immediately. The 1,620 QUALIFIED and CONDITIONAL wallets complete automated onboarding in minutes – dramatically reducing compliance cost and time-to-investment for legitimate investors.

When Is It Required: Deploy chainaware-rwa-investor-screener for any tokenized asset platform needing automated investor suitability assessment. It is specifically required when traditional KYC throughput is insufficient for the number of investors the platform needs to process, when the regulatory framework requires documented suitability assessment rather than just AML screening, and when the platform offers products across multiple risk tiers requiring different investor qualification standards. It complements chainaware-compliance-screener (which handles AML compliance) by adding the investor sophistication and product suitability dimensions that pure AML screening does not cover.

13. chainaware-gamefi-screener

Play-to-Earn bot farm and multi-account cheater detection for Web3 games. The agent screens wallets connecting to a P2E platform for bot signatures (coordinated transaction timing, uniform behavioral patterns, zero genuine game interaction history), multi-account cheating (same operator controlling multiple wallets extracting parallel rewards), and reward abuse patterns (wallets appearing across multiple P2E reward events in behavioral coordination). Legitimate players are classified into experience tiers for matchmaking and receive P2E reward eligibility scores scaling allocations by behavioral quality. The fraud gate disqualifies wallets above 0.70 fraud probability regardless of game-specific behavior.

Use Case: A P2E game launches a tournament with $100,000 in prize pool rewards. Within 48 hours, 40% of tournament participants are identified as bot farms – coordinated wallet clusters playing mechanically to extract rewards without genuine gameplay. Chainaware-gamefi-screener deployed at tournament registration identifies the bot wallets before they accumulate rewards. The disqualified wallets are excluded. Remaining players are classified into tiers from Beginner to Expert and receive reward multipliers (0.5× to 4×) scaled to their on-chain gaming experience. Prize pool distribution shifts from bot-dominated to skill-correlated, improving tournament integrity and the genuine player community’s experience.

When Is It Required: Run chainaware-gamefi-screener at every P2E tournament registration, every in-game reward event, and every NFT loot drop in a play-to-earn context. It is specifically required for any P2E game with real economic value at stake – when rewards are worth more than the cost of running bots, bot farms appear without exception. The agent is also required for scholarship programs in P2E games, where scholarship managers need to verify that scholar wallets are controlled by genuine individual players rather than farming operations controlling multiple scholarship slots simultaneously.

14. chainaware-credit-scorer

Returns a crypto credit score from 1 to 9 using ChainAware’s credit_score tool, combining fraud probability with social graph analysis of the wallet’s transaction network. Score 9 is Prime (highest creditworthiness, best lending terms). Score 1 is Very High Risk (decline lending). Currently supported on ETH only, where social graph data density is highest. The credit score is the simplest borrower signal in the suite – designed specifically as a composable building block that chainaware-lending-risk-assessor combines with experience score and risk appetite to produce a full Borrower Risk Grade.

Use Case: A DeFi lending protocol wants to offer differentiated interest rates based on borrower quality – lower rates for high-credit-score borrowers to attract and retain the best users, higher rates for lower-credit-score borrowers to compensate for elevated default risk. Chainaware-credit-scorer provides the credit signal driving the rate differentiation. Prime borrowers (score 9) receive the protocol’s best rate. High-Risk borrowers (score 1-2) are declined or required to over-collateralize at 200%+. The differentiation improves risk-adjusted revenue and creates a meaningful incentive for borrowers to maintain clean on-chain behavior over time.

When Is It Required: Use chainaware-credit-scorer as a component within chainaware-lending-risk-assessor for full borrower risk assessment, or standalone when a simple 1-9 credit rating is sufficient for the use case. It is specifically required for ETH-based lending protocols wanting a standardized credit signal compatible with the broader DeFi lending ecosystem. For multi-chain lending platforms, chainaware-lending-risk-assessor provides broader coverage by combining the credit score with behavioral signals from the full Prediction MCP toolset. See our Credit Score guide for the complete methodology.

15. chainaware-lending-risk-assessor

Full borrower risk assessment for DeFi lending protocols – combining fraud probability, on-chain experience score, risk appetite classification, and (on ETH) credit score into a Borrower Risk Grade from A to F with specific recommended collateral ratio and interest rate tier. Grade A borrowers (low fraud, high experience, appropriate risk profile) receive the best terms. Grade F borrowers are declined. The agent covers ETH, BNB, BASE, HAQQ, and SOLANA – enabling multi-chain lending platforms to apply consistent underwriting standards across all supported networks using behavioral signals rather than collateral value as the only risk proxy.

Use Case: A DeFi lending protocol currently applies a flat 150% collateralization ratio to every borrower regardless of on-chain history. This approach drives away high-quality borrowers who resent over-collateralization for loans they will clearly repay. With chainaware-lending-risk-assessor, the protocol offers Grade A borrowers 110% collateralization at the best rate, Grade B borrowers 130% at standard rates, and Grade C borrowers 160% at elevated rates. Grade D-F wallets are declined or required to provide significant over-collateral. Capital efficiency improves, quality borrower acquisition increases, and risk-adjusted returns improve across the loan book.

When Is It Required: Deploy chainaware-lending-risk-assessor for any DeFi lending or credit protocol wanting to move beyond collateral-only risk assessment. It is specifically required for undercollateralized or uncollateralized DeFi lending products, where behavioral risk signals are the primary protection against default. Additionally, it is required for any lending protocol seeking to compete on borrower experience by offering differentiated rates – flat-rate protocols cannot attract and retain the highest-quality borrowers who have better options elsewhere.

16. chainaware-portfolio-risk-advisor

Portfolio-level rug pull risk scan that evaluates every token in a submitted portfolio, aggregates risk into a Portfolio Risk Score (0-100) and grade (A-F), flags dangerous concentrations, and produces a prioritized exit/reduce rebalancing plan. The primary signal for each token is its rug pull probability from predictive_rug_pull. Supplementary community rank from token_rank_single enriches the risk assessment with holder quality data for the approximately 2,500-3,000 tokens covered by the pre-calculated index. Concentration flags alert when a single high-risk token represents more than 20% of portfolio value (Critical Concentration) or when multiple tokens share the same deployer (Cluster Risk).

Use Case: A DeFi investor holds 12 positions across ETH and BNB, total value $85,000. Three tokens have no community rank data and significant social media promotion – a combination warranting scrutiny. Running chainaware-portfolio-risk-advisor identifies two of those three tokens as High Risk (TRS 58 and 71), with deployer behavioral signatures consistent with previous rug pull operations. The agent produces a rebalancing plan: exit both High Risk positions immediately ($12,400 combined), reduce a Moderate Risk position to 5% of portfolio, and hold the remaining nine positions scoring Low Risk. The investor exits before the highest-risk position rugs two weeks later.

When Is It Required: Run chainaware-portfolio-risk-advisor before deploying significant new capital into any multi-token DeFi position, before any rebalancing decision in a portfolio containing tokens launched in the last 90 days, and as a regular monthly audit of any DeFi portfolio containing more than five positions. It is specifically required for protocols managing DAO treasuries or yield strategies on behalf of users, where portfolio risk is a fiduciary responsibility rather than a personal investment choice.

17. chainaware-agent-screener

The first dedicated AI agent trust scoring tool in the on-chain intelligence market. Screens two addresses simultaneously: the agent wallet (the address the autonomous agent uses to transact) and the feeder wallet (the address that funds the agent). The feeder wallet is typically the most revealing signal – a fraudulent feeder means the agent operates on behalf of a bad actor regardless of how clean the agent wallet appears. The output is a normalized Agent Trust Score from 0 to 10: 0 means confirmed or likely fraud, 1 means new address with insufficient data, and 2.0-10.0 is a normalized reputation score. When the agent wallet is a smart contract rather than an EOA, behavioral data is unavailable and the score is capped at 6.0 with a proxy calculation. This directly addresses the structural vulnerability in the ERC-8004 agent registry – 196,000+ registered agents with no behavioral trust signals attached to their on-chain identities.

Use Case: A DeFi protocol evaluating whether to accept automated interactions from third-party AI trading agents faces a core challenge: without agent trust scoring, the protocol cannot distinguish between a legitimate institutional trading bot and a fraudulent agent designed to manipulate protocol state. Running chainaware-agent-screener on each agent’s wallet and feeder wallet produces a trust score used as an access gate. Agents scoring 7.0+ receive full access. Agents scoring 4.0-6.9 receive limited access with lower transaction limits and no admin function access. Agents scoring below 4.0 or with Score 0 are blocked entirely. Score 1 (new feeder wallet) triggers a manual review before access is granted.

When Is It Required: Deploy chainaware-agent-screener whenever a protocol, DEX, lending platform, or DAO accepts or considers accepting automated interactions from third-party AI agents. As the agentic economy grows – with AI agents increasingly operating autonomously across DeFi, executing trades, managing positions, and participating in governance – the need for behavioral trust assessment of agents becomes as important as the need for behavioral trust assessment of human wallets. The agent is also required for ERC-8004 registry participants seeking to validate the trustworthiness of other registered agents before delegating tasks or sharing resources with them. For context on the growing agentic economy and its fraud implications, see our Web3 Agentic Economy guide .

Growth Tech Agents – 15 Agents, Complete Reference

ChainAware’s Growth Tech agents convert the same behavioral intelligence that prevents fraud into measurable protocol growth – higher conversion rates, better user retention, smarter acquisition spend, and more relevant product recommendations. The foundational insight driving this category is that 84% of wallets connecting to a typical DeFi protocol after a marketing campaign are ghost wallets – addresses with zero real engagement that farming bots and airdrop hunters control. Traditional Web3 growth tools cannot distinguish these ghost wallets from genuine users because they lack behavioral intelligence. Growth Tech agents solve this by treating each wallet’s on-chain history as a behavioral fingerprint that reveals its intentions, experience, risk appetite, and likely lifetime value – before the protocol spends a single dollar acquiring or engaging it.

Together, these 15 agents cover the complete user lifecycle: identifying high-value targets before acquisition (lead-scorer, ltv-estimator), personalizing the first moment of engagement (platform-greeter, onboarding-router), recommending the right products (defi-advisor, wallet-marketer), retaining users through their journey (upsell-advisor), and understanding the full user base through segmentation (cohort-analyzer, whale-detector). Furthermore, every Growth Tech agent runs a fraud gate internally – a wallet that fails the fraud check receives no marketing message, no personalized greeting, and no upsell recommendation. For the foundational framework on why behavioral intelligence outperforms demographic or web analytics approaches for Web3 growth, see our Web3 User Segmentation guide .

18. chainaware-wallet-auditor

The flagship intelligence agent delivers the complete 22-dimension Web3 Persona for any wallet address in under one second. A single predictive_behaviour call returns the full behavioral profile: fraud probability (98% accuracy), all 12 intention probabilities (Borrow, Lend, Trade, Gamble, NFT, Stake ETH, Stake Yield Farm, Leveraged Staking, Leveraged Staking ETH, Leveraged Lending, Leveraged Long ETH, Leveraged Long Game), experience score (0-10), risk capability (0-9), AML forensic flags, Wallet Rank, behavioral categories, protocol usage history, and ChainAware’s direct personalization recommendations. This is the broadest intelligence output in the suite – used when a protocol needs everything about a wallet rather than a specific signal. Coverage: ETH, BNB, BASE, HAQQ, SOLANA.

Use Case: A DeFi protocol’s product team wants to understand who is actually connecting to their platform before redesigning the UI. Using chainaware-wallet-auditor on a sample of 500 recent connecting wallets reveals that 62% have High Lend intention, 18% have High Trade intention, 11% are experienced DeFi power users with 8+ experience scores, and 9% are ghost wallets with zero meaningful history. This behavioral distribution tells the product team that their core user is a yield-seeking lender, not the active trader they assumed. The UI redesign prioritizes lending product visibility – a decision driven by behavioral data rather than assumption.

When Is It Required: Use chainaware-wallet-auditor when the use case requires the complete behavioral picture rather than a single signal – individual due diligence on high-value wallets, building a comprehensive user understanding before product decisions, and providing the full context that orchestrating agents like chainaware-marketing-director need to compose complete reports. The free Wallet Auditor at chainaware.ai/audit runs this agent for any address with no signup required – start there to understand the full output before integrating via API. See our Wallet Auditor guide for the complete usage guide.

19. chainaware-reputation-scorer

Calculates the deterministic ChainAware reputation score (0-1000) using the standard formula: (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability). A score of 1,000 represents the theoretical maximum – experience 10, risk capability 9, fraud probability 0.00. In practice, scores above 750 represent Elite wallets: expert DeFi users with aggressive risk profiles and clean fraud histories. Scores below 125 indicate either ghost wallets with no history or high-fraud-probability addresses. The score is deterministic – given the same MCP inputs, the formula always produces the same output, making it auditable and reproducible for governance and allocation purposes. Coverage: ETH, BNB, BASE, HAQQ, SOLANA.

Use Case: A DAO wants to create a community leaderboard that ranks members by contribution quality rather than token holdings. Using chainaware-reputation-scorer on all community wallets produces a ranked list where active DeFi power users with long track records rise to the top, while passive token holders with minimal protocol engagement remain at the bottom. The leaderboard displays publicly on the DAO’s governance portal, creating a visible quality signal that incentivizes genuine participation over passive holding. Top-ranked wallets receive additional governance weight, early access to new protocol features, and community recognition – none of which require manual review to assign.

When Is It Required: Use chainaware-reputation-scorer when a standardized, comparable quality metric is needed across a large set of wallets – governance leaderboards, airdrop tier allocation (used internally by chainaware-airdrop-screener), lending collateral ratios, and marketing campaign quality gates all benefit from the single-number reputation score. It differs from chainaware-wallet-ranker (which ranks by total points and transaction count) in that the reputation formula explicitly penalizes fraud probability – a wallet with high activity but elevated fraud risk scores lower than a wallet with moderate activity and a clean history.

20. chainaware-wallet-ranker

Returns global wallet rank from experience score, total points, wallet age, and transaction count across the 20M+ wallet network. The rank provides a comparable quality metric across wallets from different blockchains through the unified behavioral scoring model – a wallet’s experience score on ETH is directly comparable to one on SOLANA. Batch mode produces a ranked leaderboard sorted by total points descending, identifying the highest-quality wallets in any submitted list. Unlike reputation-scorer (which uses a specific formula), wallet-ranker reflects ChainAware’s internal composite scoring of each wallet’s overall on-chain quality without the explicit fraud penalty component.

Use Case: A DeFi protocol wants to identify its top 50 users for a VIP program offering fee discounts and early feature access. Running chainaware-wallet-ranker on all 12,000 addresses that have ever interacted with the protocol produces a ranked leaderboard. The top 50 wallets by total points become VIP members. Because wallet rank reflects genuine on-chain quality rather than just protocol-specific activity, the VIP list includes wallets that are highly engaged across DeFi broadly – users most likely to promote the protocol within their wider DeFi networks and generate the most valuable word-of-mouth acquisition.

When Is It Required: Deploy chainaware-wallet-ranker for community leaderboards, VIP tier identification, governance weight calculation, and token holder quality assessment. It pairs naturally with chainaware-whale-detector – whale-detector identifies high-value wallets by behavioral depth, while wallet-ranker produces the specific numerical rank for ordering and comparison purposes. For the complete framework on wallet quality signals, see our Wallet Rank guide .

21. chainaware-whale-detector

Classifies wallets into four whale tiers – Mega Whale (experience ≥ 9, total points ≥ 5,000, active categories ≥ 3), Whale (experience ≥ 7.5 and total points ≥ 2,000, or experience ≥ 7 with high protocol diversity), Emerging Whale (experience ≥ 5 and total points ≥ 500, or experience ≥ 6 with high stake and trade intent), and Not a Whale. Each tier also receives an Active or Dormant classification based on forward-looking intent signals: Active whales have at least one High intent probability; Dormant whales have high experience but all-Low intent – they were once significant participants but are not currently engaged. Domain classification further identifies the wallet’s primary area: Trading Whale, DeFi Whale, NFT Whale, Multi-Chain Whale, Yield Whale, or Multi-Dimensional Whale. Fraud gate excludes wallets above 0.30 fraud probability from any whale classification.

Use Case: A DeFi protocol is launching a new advanced yield product designed for sophisticated users. The marketing team needs to identify which existing wallets in their user base qualify as genuine whales – and specifically which whales are currently active vs. dormant. Running chainaware-whale-detector on all 8,000 wallets that have interacted with the protocol in the last 90 days identifies 23 Mega Whales, 87 Whales, and 214 Emerging Whales. Within those groups, 68% are Active and 32% are Dormant. Active Mega Whales receive direct personal outreach for the new product launch. Dormant Whales receive a re-engagement campaign. Emerging Whales receive nurture content designed to accelerate their progression to the next tier.

When Is It Required: Run chainaware-whale-detector before any VIP program launch, before direct outreach campaigns targeting high-value users, before governance voting weight design (where whales warrant different treatment than retail participants), and as a regular audit of any protocol’s most valuable users to identify when whales go dormant and need re-engagement before they migrate to a competitor. The domain classification adds a targeting layer – a protocol launching an NFT-adjacent feature should specifically target NFT Whales, while a new yield vault should target Yield Whales and DeFi Whales.

22. chainaware-ltv-estimator

Estimates 12-month revenue potential for any wallet as a USD range using a seven-step model. Step one derives the annual transaction rate from experience level (Beginner → 5 tx/year, Expert → 700 tx/year). Step two applies an intent multiplier from forward-looking signals (3+ High intents → 1.25×, all Low → 0.65×). Step three calculates average transaction value from wallet balance × platform share (configurable, defaults to 15%). Step four applies the fee rate (configurable, defaults to 0.1%). Step five applies a category multiplier from activity breadth (1 category → 1.0×, 5+ categories → 1.75× cap). Step six applies a risk multiplier from risk profile (Conservative → 0.70×, Aggressive → 1.40×). Step seven applies a retention factor from fraud probability (0.00-0.09 → 0.95, 0.51-0.70 → 0.20). The final estimate applies ±25% to produce a range. Hard reject conditions return $0 with no range for confirmed fraud, fraud above 0.70, or any AML forensic flag.

Use Case: A DeFi protocol’s growth team plans a user acquisition campaign with a $200,000 budget. Before spending, they run chainaware-ltv-estimator on 10,000 target wallet addresses from a purchased marketing list. Results reveal that 6,200 wallets have estimated 12-month LTV below $10 (Dormant tier), 2,800 wallets have LTV in the $10-$100 range (Low tier), 800 wallets have LTV in the $100-$1,000 range (Medium tier), and 200 wallets have LTV above $1,000 (High tier). Rather than spending the $200,000 uniformly across all 10,000 addresses, the team concentrates 80% of the budget on the 1,000 Medium and High LTV wallets. Expected ROI improves dramatically compared to uniform distribution.

When Is It Required: Use chainaware-ltv-estimator before any acquisition campaign to prioritize high-value targets, before VIP tier assignment to identify which wallets generate the most protocol revenue, and before marketing budget allocation decisions where targeting the right wallets determines whether the campaign generates positive ROI. It works alongside chainaware-lead-scorer – lead-scorer measures conversion probability, while ltv-estimator measures revenue magnitude. Combining both gives a complete acquisition prioritization signal: high-lead-score × high-LTV wallets deserve the most aggressive outreach investment.

23. chainaware-lead-scorer

Sales lead qualification engine returning a lead score (0-100), tier (Hot/Warm/Cold/Dead), conversion probability, and recommended outreach angle for any wallet. The scoring model weights five components: experience (35%), intent strength (25%), activity breadth (20%), risk appetite (10%), and fraud penalty (up to −10). Product context doubles the weight of the matching intent signal – a staking product doubles Prob_Stake, a cross-chain bridge doubles Prob_Bridge – making the score product-specific rather than generic. Hot leads (75-100) warrant immediate personalized outreach. Dead leads (0 or fraud-disqualified) are excluded from all campaigns entirely, preventing budget waste on wallets that would never convert.

Use Case: A DeFi yield aggregator launching on BASE wants to identify which ETH-based DeFi users are most likely to bridge and adopt the new platform. The growth team runs chainaware-lead-scorer on 25,000 ETH wallet addresses that have interacted with competing yield products, with product context set to “cross-chain yield aggregator on BASE.” The scoring returns 340 Hot leads (score 75+, high Prob_Bridge and Prob_Stake intent), 2,800 Warm leads (score 50-74), 15,000 Cold leads (score 25-49), and 6,860 Dead leads (below 25 or fraud-disqualified). The team focuses personalized outreach on the 340 Hot leads and runs automated campaigns for the 2,800 Warm leads. Acquisition cost per converted user drops significantly compared to the previous campaign that treated all 25,000 addresses identically.

When Is It Required: Run chainaware-lead-scorer before any acquisition outreach campaign, before direct sales team prioritization, and before budget allocation across different wallet segments. It is specifically required when a protocol launches a new product or feature and wants to identify existing wallet holders most likely to adopt it based on behavioral signals – rather than guessing based on past protocol interactions alone. See our Behavioral Analytics guide for the complete acquisition framework.

24. chainaware-wallet-marketer

Generates a hyper-personalized marketing message of maximum 20 words for any wallet, derived directly from its on-chain behavioral signals – no generic crypto copy, no templated language. Signal priority determines the message angle: Prob_Stake High leads with staking yield opportunity; Prob_Trade High leads with trading execution quality; Prob_Bridge High leads with cross-chain capability; Prob_NFT_Buy High leads with NFT feature; DeFi Lender category leads with lending/yield rates; experience above 7.5 leads with advanced power user features; experience below 2.5 leads with simple beginner-friendly onboarding. The message mirrors what the wallet actually does on-chain, making it feel personal rather than promotional. Fraud gate blocks message generation entirely for high-fraud-probability wallets.

Use Case: A DEX wants to run a re-engagement campaign targeting 5,000 wallets that connected once but never executed a trade. Running chainaware-wallet-marketer in batch mode on all 5,000 addresses produces 5,000 distinct messages – each derived from that specific wallet’s behavioral signals. A wallet with High Prob_Stake and DeFi Lender category receives: “Your lending habits earn yield. Our single-click vault automates it. Start here.” A wallet with High Prob_Trade and Active Trader category receives: “You trade fast. Our zero-slippage routing finds better fills. Try one swap.” A beginner wallet with experience below 2 receives: “New to DeFi? Earn your first yield in under two minutes. Start here.” The personalized messages achieve 3-4× higher click-through rates than the generic campaign the DEX ran previously.

When Is It Required: Use chainaware-wallet-marketer for any outbound campaign where personalization improves conversion – which is essentially every outbound campaign. It is specifically required when a protocol has a segmented user base with significantly different behavioral profiles, when re-engaging dormant users where a generic message will be ignored, and when the campaign budget is large enough that even a 2× improvement in conversion rate generates meaningful additional revenue. For the complete personalization framework, see our Why Personalization Matters guide .

25. chainaware-platform-greeter

Contextual welcome message engine generating platform-specific in-app messages of maximum 35 words at wallet connection. The same wallet receives a completely different message on Aave than on 1inch or OpenSea – because what matters to a DeFi lender visiting a lending platform differs fundamentally from what matters when that same wallet visits a DEX or an NFT marketplace. Platform type detection maps the wallet’s dominant behavioral signals to the most relevant platform angle. Returning users with protocol history receive “welcome back” framing with specific references to their history. First-time visitors with strong intent alignment receive “you know X, here’s what we do for X” framing. Low-experience first-timers receive simplified educational framing. Tone is configurable across friendly, professional, and bold to match brand voice.

Use Case: A lending protocol integrates chainaware-platform-greeter into its wallet connection event. When a DeFi Lender wallet with experience 8 and existing Aave positions connects, it sees: “Your lending positions are working – ETH supply rate is up 0.4% since your last visit. Check your health factor before rates move.” When a High Prob_Trade wallet connects for the first time, it sees: “You trade – here you can also earn on idle assets between swaps.” When a low-experience wallet connects for the first time, it sees: “New here? Deposit any token and earn interest automatically. No minimums.” Three different wallets, three different messages, all generated automatically at connection with zero manual configuration per user segment.

When Is It Required: Deploy chainaware-platform-greeter for any DeFi platform with diverse user types – a protocol serving both experienced DeFi power users and first-time users needs different first-moment experiences for each segment. It is specifically required when conversion analytics show a significant percentage of connecting wallets leaving without taking any action – a sign that the current generic landing experience does not resonate with the behavioral diversity of the connecting wallet population. The agent adds under 200ms to the wallet connection flow, negligible for user experience purposes.

26. chainaware-onboarding-router

Routes each connecting wallet to the correct onboarding experience based on verifiable on-chain experience rather than self-reported surveys or assumed user segments. Experience 0-2.5 → Beginner Tutorial (full guided walkthrough – this wallet needs hand-holding through every step). Experience 2.6-6 → Intermediate Guide (condensed tips that skip the absolute basics while still orienting the user to platform-specific features). Experience 6.1-10 → Skip Onboarding (power user, straight to the product – tutorials waste their time and signal that the platform doesn’t understand them). Secondary signals refine the route: a wallet with experience 5.5 that already uses the platform’s specific protocol category can skip most tutorials even though its overall score is technically Intermediate. New Address always routes to Beginner regardless of other signals.

Use Case: A DeFi platform’s user research team discovers that 23% of users who complete the full onboarding tutorial are experienced DeFi power users who were frustrated by being forced through beginner content. These users have 3× higher churn rates in the first week compared to users correctly identified as power users who skipped onboarding. Integrating chainaware-onboarding-router eliminates the mis-routing: power users (experience 6.1+) go directly to the product, intermediate users see a condensed orientation, and genuine beginners receive the full tutorial. First-week churn drops 31% as power users stop abandoning the platform out of frustration with irrelevant onboarding content.

When Is It Required: Deploy chainaware-onboarding-router for any platform with a multi-step onboarding flow and a diverse user base that includes both experienced DeFi users and newcomers. It is specifically required when product analytics show high drop-off during onboarding – a symptom that the current fixed onboarding experience is poorly matched to the actual experience distribution of the connecting wallet population. The agent works best in combination with chainaware-platform-greeter (which personalizes the first moment before onboarding begins) and chainaware-defi-advisor (which provides product recommendations post-onboarding). For the complete onboarding conversion analysis, see our DeFi Onboarding guide .

27. chainaware-defi-advisor

Personalized DeFi product recommendation engine with three product tiers calibrated to wallet experience and risk appetite. Tier 1 Safe Harbor covers Beginner and Conservative wallets: simple staking, stablecoin lending, savings vaults, fixed-rate lending. Tier 2 Yield Builder covers Intermediate and Moderate wallets: liquid staking, blue-chip LP pools, variable rate lending, multi-asset vaults. Tier 3 Yield Maximizer covers Experienced and Aggressive wallets: leveraged yield farming, options vaults (DOVs), concentrated liquidity CLMM active management, cross-chain yield arbitrage, and veToken strategy stacking. Intent signals boost recommendations within the tier: Prob_Stake High prioritizes staking products first; Prob_Trade High prioritizes LP pools and active liquidity. Protocol history adds a further targeting layer: a wallet that already uses Aave receives Aave-compatible product recommendations over generic alternatives.

Use Case: A DeFi aggregator platform connects 500 different wallets per day across its product suite. Without personalization, every wallet sees the same “Featured Products” section – typically the highest-APY products, which are also the highest-risk. Conservative beginners see leveraged products they don’t understand, and aggressive experts see beginner staking options that bore them. Integrating chainaware-defi-advisor personalizes the product menu for each connecting wallet: beginners see stablecoin lending and simple staking; power users see advanced leveraged strategies and CLMM management tools. First-session product interaction rates increase 2.4× across all experience tiers because every user sees products calibrated to their level.

When Is It Required: Use chainaware-defi-advisor for any multi-product DeFi platform where the right product for one user is actively wrong for another. It is specifically required when conversion analytics show significant variance in product adoption rates by user experience level – a sign that current product placement is suboptimal for at least one segment. For platforms launching new products, the agent identifies which existing wallet segments are most aligned with the new product’s requirements before the launch, enabling targeted pre-launch outreach to the highest-probability adopters. See our DeFi Platform Use Cases guide .

28. chainaware-upsell-advisor

Identifies the optimal next product to offer an existing user and the precise moment to offer it. Upgrade readiness score (0-100) combines experience headroom toward the next product tier (40% weight), intent alignment with the target product (35%), and risk appetite fit (25%). Score 80-100 → offer now, conversion probability above 65%. Score 60-79 → offer at the next behavioral trigger event. Score 40-59 → nurture first, offer after 1-2 more sessions. Score below 40 → do not upsell yet – the risk is churn rather than conversion. Trigger events are behavioral rather than time-based: a wallet ready for a staking upgrade gets the offer the next time it stakes or claims rewards, not on a fixed weekly cadence. A “What NOT to do” recommendation identifies the single upsell approach most likely to cause churn for each specific wallet – for example, “Don’t pitch leveraged products – this is a Conservative wallet and the complexity will cause churn.”

Use Case: A DeFi lending platform has 3,000 active users on its basic lending tier. The product team wants to introduce an advanced leveraged yield farming product and identify which users are ready to upgrade now vs. which need nurturing first. Running chainaware-upsell-advisor on all 3,000 users with the new product as context identifies 180 users with readiness above 80 (offer now), 620 users at 60-79 (offer at next trigger), 1,400 users at 40-59 (nurture first), and 800 users below 40 (do not upsell). The 180 “offer now” users receive immediate personalized outreach with specific trigger messaging aligned to their dominant intent signal. Within four weeks, 67% of the “offer now” group has upgraded – without wasting outreach budget on the 800 users who were not ready and would have churned if pushed.

When Is It Required: Deploy chainaware-upsell-advisor whenever a protocol launches a new product tier and wants to maximize adoption among existing users. It is specifically required for protocols with a tiered product structure where pushing the wrong product too early causes churn, for platforms with subscription-based models where upgrade timing significantly affects revenue, and for any DeFi protocol where the most valuable users are those engaging with multiple product tiers simultaneously. The trigger event recommendation is especially valuable – it replaces time-based upsell campaigns (which push users at arbitrary moments) with behavior-triggered campaigns (which engage users at the exact moment their intent signals indicate readiness).

29. chainaware-cohort-analyzer

Batch behavioral cohort segmentation for Web3 analytics teams. Classifies every wallet in a submitted list into one of eight behavioral cohorts: Power DeFi User (experience ≥ 7, DeFi Lender or Active Trader dominant, protocols ≥ 5), NFT Collector (NFT Collector dominant, experience ≥ 3), Yield Farmer (Yield Farmer dominant or Prob_Stake High with experience ≥ 5), Multi-Chain Explorer (Bridge User dominant or bridge-heavy protocol history), Active Trader (Prob_Trade High with experience ≥ 4), Casual User (experience 2-4.9, no dominant pattern), Dormant/Inactive (experience ≥ 2 but all intent signals Low), and New/Fresh Wallet (new address with clean fraud signals). Fraud exclusions – bots, confirmed fraud, AML flags, suspicious new wallets – are separated from behavioral cohorts entirely. Each cohort receives a specific engagement strategy recommendation, and the full report includes audience quality score, per-cohort statistics, and a three-priority action plan.

Use Case: A DeFi protocol planning its Q3 marketing budget wants to allocate spend across different user segments rather than running one generic campaign. Chainaware-cohort-analyzer on their 15,000-wallet user base reveals: 890 Power DeFi Users (6%), 1,200 NFT Collectors (8%), 2,100 Yield Farmers (14%), 800 Multi-Chain Explorers (5%), 3,400 Casual Users (23%), 2,800 Dormant wallets (19%), 1,600 New wallets (11%), and 2,210 excluded bots and fraud (15%). The budget allocation becomes data-driven: 35% to Yield Farmer acquisition for the new vault product, 25% to Casual User conversion, 20% to Dormant re-engagement, and 20% to New wallet onboarding. Each cohort receives a distinct message strategy rather than a generic campaign blasted to all 15,000 addresses.

When Is It Required: Run chainaware-cohort-analyzer before any marketing budget planning cycle, before product launch targeting decisions, and as a quarterly audit of user base composition to detect shifts in behavioral distribution. It is specifically required before an airdrop (to ensure token distribution aligns with cohort quality rather than farming behavior), before a governance token launch (to understand which community members qualify for each allocation tier), and before any significant UI redesign (to ensure the redesign serves the actual behavioral distribution rather than an assumed user persona).

30. chainaware-token-ranker

Discovers and ranks tokens by the behavioral quality of their holder community across five categories – AI Token, RWA Token, DeFi Token, DeFAI Token, DePIN Token – on ETH, BNB, BASE, and SOLANA. Community rank scores the aggregate behavioral strength of all token holders: wallet age, transaction history, protocol diversity, and experience scores across the 20M+ wallet network. A token whose holders are predominantly experienced, long-tenured, multi-protocol DeFi users ranks higher than a token with the same market cap but predominantly fresh wallets with minimal history. This ranking reflects genuine community quality – not just trading volume or price momentum, which can be manufactured. Supports sort by community rank, normalized rank, or holder count; category filtering; pagination; and name-based token search.

Use Case: An institutional DeFi fund wants to allocate capital to the top three AI tokens by community quality rather than market cap. Running chainaware-token-ranker for AI Token category on ETH and BNB returns a ranked list showing which AI tokens have the strongest holder bases of experienced, legitimate DeFi participants – and which have significant proportions of fresh wallets and farming addresses in their holder distribution. The fund identifies two tokens where community quality is significantly stronger than their market cap rank suggests – potential value opportunities where genuine community strength has not yet been reflected in price. Both tokens are added to the portfolio after individual deep-dives using chainaware-token-analyzer.

When Is It Required: Use chainaware-token-ranker for token portfolio research and selection when community quality is a meaningful signal, for DEX teams curating featured token listings based on genuine community strength rather than trading volume alone, and for any platform wanting to surface high-quality tokens to users before market price discovery catches up to community quality. It works as the first step in a two-step research process: token-ranker identifies the best candidates from a category, then chainaware-token-analyzer deep-dives each candidate’s specific holder composition. See our Token Rank guide for detailed methodology.

31. chainaware-token-analyzer

Deep-dives into a single token’s community rank and top holder profiles – returning each top holder’s wallet age, total transaction count, total points, and global rank across the 20M+ wallet network. Optional fraud screening on the top holders via predictive_fraud identifies whether the token’s largest positions are held by legitimate experienced wallets or by coordinated fraud networks disguising their concentration. The holder quality assessment computes average wallet age, average transaction count, and average global rank across the top holders, producing a Verdict (2-3 sentences on whether these are genuine power users or manufactured holders). Token-ranker identifies which tokens have the strongest community quality in aggregate; token-analyzer validates whether specific tokens actually back that aggregate signal with genuine individual holders.

Use Case: A crypto exchange is evaluating whether to list a new DeFi token. The community rank from chainaware-token-ranker shows the token in the top 20% of its category – strong enough to consider. Chainaware-token-analyzer deep-dives the top 20 holders: 14 have average wallet age above 800 days, high transaction counts, and global ranks in the top 10% of the 20M+ wallet network. However, three of the top 20 holders share a funding source and show coordinated acquisition patterns – signals of artificial holder concentration. The fraud screening confirms two of those three have elevated fraud probability. The exchange requires the team to reduce concentration before listing. Six weeks later, the concentration issue is resolved, and the token lists and performs well due to its genuinely strong community foundation.

When Is It Required: Run chainaware-token-analyzer before listing any token on an exchange or DEX with listing standards, before making significant portfolio allocation to a token where holder quality affects the investment thesis, and before any governance vote giving token holders significant power – understanding whether those holders are genuine community members or coordinated operators directly affects the legitimacy of governance outcomes. It is also required as part of due diligence for institutional crypto fund investments where holder composition is a material factor in the investment case.

32. chainaware-marketing-director

The orchestrator agent – a senior marketing strategist that delegates to seven specialist agents and synthesizes their outputs into a complete Marketing Campaign Brief. In batch mode (multiple wallets), the agent runs six sequential phases: segmentation via chainaware-cohort-analyzer, lead scoring and whale detection on the highest-potential wallets, per-cohort message generation via chainaware-wallet-marketer, upsell opportunity identification via chainaware-upsell-advisor, onboarding routing for new wallets, and executive campaign brief synthesis. In single-wallet mode, it runs five specialist agents simultaneously and returns a complete Wallet Marketing Profile including fraud risk, whale tier, lead score, personalized outreach message, platform welcome message, upsell path, and recommended onboarding flow. The Marketing Director represents the highest-level abstraction in ChainAware’s agent architecture – demonstrating what coordinated multi-agent intelligence delivers that no single specialist agent can replicate independently. It requires a platform description as input, using that context to make every generated message feel native to the specific protocol.

Use Case: A DeFi lending protocol is planning a growth push targeting 200 existing wallets that have connected but never borrowed. The growth lead does not have time to run each specialist agent separately and synthesize results manually. Running chainaware-marketing-director with the 200 wallet addresses and the platform description as input produces a complete Campaign Brief in one pass: 23 Hot leads requiring immediate personal outreach; 8 Mega and Whale wallets identified for VIP treatment; per-cohort message templates for the 6 behavioral cohorts represented in the wallet list; 31 wallets with upgrade readiness above 80 ready for a borrowing product offer; 18 new wallets routed to beginner onboarding; and 14 excluded as fraud or bots. The entire brief – segmentation, prioritization, messages, execution sequence – is ready for the growth team to execute.

When Is It Required: Use chainaware-marketing-director when a campaign needs the output of multiple specialist agents and the team does not have the resources to run them separately and synthesize results. It is specifically the right choice for time-sensitive campaigns where speed matters, for small growth teams needing a complete brief rather than raw intelligence, and for any campaign spanning multiple wallet segments requiring different strategies simultaneously. The agent is also the best entry point for teams new to ChainAware’s agent suite – a single Marketing Director run demonstrates the full capability range of the underlying specialist agents in one unified output. For the complete campaign planning framework, see our Web3 Marketing guide .

How Agents Compose Into Pipelines

The most powerful applications of ChainAware’s 32 agents emerge not from individual deployment but from composing them into pipelines – where the output of one agent becomes the input of the next. Every agent’s documentation includes a composability section mapping its natural connections to adjacent agents. Three core pipelines demonstrate the composability principle and cover the most common production deployments.

The Compliance Pipeline

The compliance pipeline sequences four agents: trust-scorer → aml-scorer → compliance-screener → transaction-monitor. Trust-scorer provides the fast first gate at under 50ms – any wallet below 0.30 trust score is immediately routed to enhanced review. AML-scorer adds forensic verification for wallets that pass the trust gate, checking all 19 forensic flag categories and producing the documented AML score needed for regulatory reporting. Compliance-screener orchestrates both signals plus transaction pattern analysis into the final PASS / EDD / REJECT verdict with full documented evidence trail. Transaction-monitor handles ongoing screening post-onboarding, flagging any transaction that exceeds risk thresholds after a wallet has been onboarded and approved.

Together, the four agents cover the complete compliance lifecycle from pre-onboarding screening through ongoing monitoring – the full stack required for MiCA-compliant operation. According to FATF’s Virtual Assets Recommendations , this kind of continuous monitoring is increasingly required rather than optional for regulated crypto asset service providers. Furthermore, the documented output from each agent in the pipeline creates the audit trail that regulators require – not just a screening decision, but the specific signals and thresholds applied to produce it.

The Growth Pipeline

The growth pipeline sequences six agents: cohort-analyzer → lead-scorer → whale-detector → wallet-marketer → onboarding-router → upsell-advisor. Cohort-analyzer segments the full wallet list and identifies fraud exclusions, producing the audience map for the campaign. Lead-scorer then ranks the highest-conversion targets within the highest-value cohorts. Whale-detector surfaces the VIP wallets within those cohorts for personal outreach. Wallet-marketer generates per-wallet personalized messages for the identified hot leads and whale wallets. Onboarding-router assigns new wallets in the cohort analysis to the correct first-time experience. Upsell-advisor identifies existing users ready for product upgrades, completing the full lifecycle from acquisition through retention.

Notably, chainaware-marketing-director runs this exact pipeline automatically – making it the recommended entry point for teams deploying the growth pipeline for the first time. The Marketing Director adds the synthesis layer that converts six separate agent outputs into a single actionable Campaign Brief, eliminating the manual work of combining results across multiple specialist runs.

The Token Intelligence Pipeline

The token intelligence pipeline sequences three agents: token-ranker → token-analyzer → rug-pull-detector. Token-ranker identifies the strongest tokens in a target category by community quality across ETH, BNB, BASE, or SOLANA – producing a shortlist of high-potential candidates. Token-analyzer then deep-dives each shortlisted token’s specific holder composition, validating whether the aggregate community quality score reflects genuine individual holders or manufactured concentration. Rug-pull-detector screens the contract address and deployer wallet for the tokens that pass both previous stages – confirming that the project behind the strong community is not itself a fraud risk.

The three agents together provide the complete due diligence stack for token investment decisions, exchange listing evaluation, and governance token selection. Moreover, they address the three distinct questions that token evaluation requires: which tokens have the strongest communities (token-ranker), are those communities genuinely strong or manufactured (token-analyzer), and is the contract itself safe (rug-pull-detector). Each question requires a different tool, and combining all three produces a confidence level in a token that no single tool delivers alone. For the complete framework on how behavioral intelligence applies to token research, see our Token Rank guide .

The Agentic Economy Pipeline

The agentic economy pipeline sequences two Fraud Tech agents with the transaction-monitor: agent-screener → counterparty-screener → transaction-monitor. As AI agents increasingly operate autonomously across DeFi – executing trades, managing positions, and participating in governance on behalf of humans – the need for agent-specific trust assessment becomes as important as wallet trust assessment. Agent-screener validates the trust score of any third-party AI agent before it is granted access to a protocol or given permission to interact with user funds. Counterparty-screener validates each specific address the agent will interact with before execution. Transaction-monitor provides continuous real-time risk scoring for every transaction the agent executes once granted access.

This pipeline addresses the structural vulnerability in the current ERC-8004 ecosystem – 196,000+ registered agents with no behavioral trust signals. ChainAware’s agentic economy pipeline provides the trust infrastructure that the registry itself lacks, making it the foundational security layer for any protocol accepting autonomous AI agent interactions. For the complete analysis of how AI agents are reshaping Web3 operations, see our Web3 Agentic Economy guide .

Getting Started – Integration in Three Steps

All 32 agents are available as open-source Claude Code agent definitions at github.com/ChainAware/behavioral-prediction-mcp . Integration requires three steps and no blockchain expertise. According to Anthropic’s Model Context Protocol documentation , MCP is rapidly becoming the standard integration layer for AI agent tool access – making ChainAware’s MCP-native delivery compatible with any LLM infrastructure that supports the standard.

Step one – register the Prediction MCP server in your Claude Code environment:

claude mcp add --transport sse chainaware-behavioral-prediction \
  https://prediction.mcp.chainaware.ai/sse \
  --header "X-API-Key: YOUR_KEY"

Step two – clone the repository and copy all 32 agent definitions into your project:

git clone https://github.com/ChainAware/behavioral-prediction-mcp.git
cp -r behavioral-prediction-mcp/.claude/agents/ your-project/.claude/agents/

Step three – invoke any agent directly from Claude Code:

claude --agent chainaware-fraud-detector
# or trigger from within Claude Code:
@chainaware-wallet-auditor

API keys are available at chainaware.ai/pricing . The free Wallet Auditor at chainaware.ai/audit demonstrates the full behavioral intelligence output with no API key or signup required – start there to understand the complete output before building your integration. Additionally, the free Fraud Detector at chainaware.ai/fraud-detector and Rug Pull Detector at chainaware.ai/rug-pull-detector demonstrate the Fraud Tech agent outputs with no setup. For the complete developer integration guide covering Claude Desktop, Cursor, and custom MCP client setups, see our Prediction MCP guide .

Frequently Asked Questions

What is a ChainAware sub-agent?

A ChainAware sub-agent is a pre-built Claude Code agent definition – a markdown file containing a name, description, role definition, decision logic, output format specification, and MCP tool references. When placed in a Claude Code project’s .claude/agents/ directory, the agent becomes invocable by name from any Claude Code session in that project. The agent calls ChainAware’s Prediction MCP tools (predictive_fraud, predictive_behaviour, predictive_rug_pull, credit_score, token_rank_list, token_rank_single) with the appropriate parameters, interprets the response according to its decision logic, and returns a structured output in the format defined in the agent file. All 32 agents are open-source under the MIT license at github.com/ChainAware/behavioral-prediction-mcp .

How do the 32 agents relate to the ChainAware Prediction MCP?

The Prediction MCP is the intelligence layer – the SSE endpoint at prediction.mcp.chainaware.ai/sse that exposes ChainAware’s six prediction tools as MCP-callable functions. The 32 agents are the application layer – pre-built Claude Code agents that call those tools with the right parameters, apply decision logic to the results, and return structured outputs ready for human or automated action. Any developer can call the raw MCP tools directly via the REST API for custom integrations. The agents provide a head start – 32 production-ready agent definitions covering the most common use cases, tested and maintained by ChainAware’s team. For the complete MCP integration guide, see our Prediction MCP guide .

Which agent should I start with?

Start with chainaware-wallet-auditor for the broadest view of what ChainAware’s intelligence produces – it returns the complete 22-dimension Web3 Persona in one call, showing every signal that the specialist agents use individually. The free Wallet Auditor at chainaware.ai/audit runs this agent for any wallet address with no setup required. Once you understand the full output, select the specialist agent matching your primary use case: fraud prevention teams start with chainaware-fraud-detector; launchpad teams start with chainaware-rug-pull-detector; compliance teams start with chainaware-aml-scorer; growth teams start with chainaware-cohort-analyzer for their existing user base; teams evaluating AI agent trustworthiness start with chainaware-agent-screener.

Can I modify the agent definitions for my specific use case?

Yes – all 32 agent definition files are open-source under the MIT license. Fork the repository, modify any agent’s decision thresholds, output format, or tool selection, and deploy your customized version alongside the standard agents. Common customizations include adjusting fraud probability thresholds for specific risk tolerances, adding platform-specific context to message templates in chainaware-wallet-marketer and chainaware-platform-greeter, and modifying the governance tier classification thresholds in chainaware-governance-screener to match specific DAO requirements. The only component that is proprietary and cannot be modified is the underlying Prediction MCP server and its trained ML models – the intelligence that powers the tool calls. Agent definitions, decision logic, and output formats are all freely modifiable.

What is the difference between Fraud Tech and Growth Tech agents?

Fraud Tech agents answer whether a wallet, contract, or transaction can be trusted – they produce verdicts (block, flag, allow, reject, qualify). Growth Tech agents answer how to engage a wallet that has passed trust assessment – they produce recommendations (which product to surface, what message to send, which onboarding flow to show). Both categories draw from the same 20M+ wallet persona database and the same Prediction MCP tools. However, every Growth Tech agent runs a fraud gate before producing any recommendation – a wallet that fails the fraud check receives no marketing message, no personalized greeting, and no upsell recommendation. This means the categories are parallel layers rather than sequential stages: fraud protection runs continuously through every growth decision, ensuring that behavioral personalization never extends to wallets that ChainAware’s models identify as fraudulent operators.

How accurate are ChainAware’s fraud detection models?

ChainAware achieves 98% fraud detection accuracy on ETH and 96% on BNB, backtested against CryptoScamDB – the largest publicly available database of documented crypto fraud incidents. The rug pull detection model achieves 90.1% accuracy, backtested on the PancakeSwap V2 dataset covering $569M in documented rug pull losses from weeks 1-20 of 2026. These accuracy figures measure the model’s ability to correctly identify fraudulent wallets and contracts before they commit their recorded offense – not accuracy on post-incident classification. The distinction matters: ChainAware’s models are designed to predict fraud before it executes, which is structurally harder than forensic classification of known fraud incidents. For the complete accuracy methodology and comparison against forensic approaches, see our Forensic vs AI-Powered Analytics guide .

Are the agents available on all blockchains?

Coverage varies by agent and underlying MCP tool. The predictive_fraud tool – used by fraud-detector, aml-scorer, trust-scorer, and counterparty-screener – covers the broadest network set: ETH, BNB, POLYGON, TON, BASE, TRON, and HAQQ. The predictive_behaviour tool – used by wallet-auditor, reputation-scorer, whale-detector, and the growth agents – covers ETH, BNB, BASE, HAQQ, and SOLANA. The predictive_rug_pull tool covers ETH, BNB, BASE, and HAQQ. Agents supporting networks not covered by their primary tool include automatic fallback logic – for example, chainaware-airdrop-screener falls back to predictive_fraud for POLYGON, TON, and TRON wallets. The classification table in this article lists exact network coverage per agent for quick reference.

Why did ChainAware build on Claude specifically?

Claude’s tool use and structured output capabilities make it particularly well-suited for the deterministic decision logic that fraud detection and compliance agents require. An agent applying five disqualification rules in strict order – stopping at the first failure – needs a model that follows logical sequences reliably without hallucinating intermediate steps. Additionally, Claude Code’s native agent support (the .claude/agents/ directory standard) makes deployment frictionless for teams already using Claude Code. Agents requiring faster, cheaper inference (chainaware-trust-scorer, chainaware-wallet-ranker) use Claude Haiku 4.5. Agents requiring richer analytical reasoning (chainaware-wallet-auditor, chainaware-cohort-analyzer, chainaware-marketing-director) use Claude Sonnet 4.6. The model selection is specified in each agent’s frontmatter and can be changed by forking the agent definition file. ChainAware’s Prediction MCP tools are model-agnostic – GPT-4, Gemini, and any other MCP-compatible model can call them directly via the REST API.

How does ChainAware’s intelligence relate to the CB Insights market map?

ChainAware was named in CB Insights’ AI Fraud Prevention Market Map in June 2026 – placed in the On-Chain Intelligence subcategory alongside Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, and Blockaid. CB Insights selected companies based on Mosaic health scores and equity funding recency, filtering out thousands of projects that did not meet the institutional bar. ChainAware’s position on the map validates the Fraud Tech agents (fraud-detector, aml-scorer, compliance-screener, rug-pull-detector, and transaction-monitor) specifically – these are the agents that deliver the on-chain intelligence capability CB Insights recognized. Beyond the map placement, ChainAware is the only company in the entire CB Insights list with a publicly traded token listed in CoinGecko’s AI category – a position that reflects the dual institutional and decentralized distribution model that the 32 agents are built to serve.

External Sources: ChainAware GitHub Repository · Anthropic Model Context Protocol · FATF Virtual Assets Recommendations · ERC-8004 Agent Registry · CB Insights AI Fraud Prevention Market Map

The post ChainAware.ai’s 32 Claude Sub-Agents – Fraud Tech and Growth Tech for the Agentic Economy first appeared on ChainAware.ai.

Web3 lost over $3.6 billion to fraud and exploits in the first three quarters of 2025 alone. Remarkably, 57.8% of those losses came not from smart contract bugs but from access-control failures – the humans and systems operating around the code, not the code itself. This pattern reveals the central challenge of Web3 trust in 2026: the attack surface is not one problem. It is five distinct problems, each requiring a fundamentally different solution.

Most teams pick one trust tool and assume they have coverage. They verify identity with KYC and assume that covers fraud risk. They run a smart contract audit and assume that covers rug pull risk. They check a Sybil score and assume that covers behavioral quality. Each assumption is wrong – because each of these tools addresses a different layer of the trust stack. This guide maps the complete five-category Web3 trust verification landscape, explains what each provider actually covers, and shows precisely where ChainAware addresses the attack surfaces that every other category leaves unprotected.

The Five Trust Problems in Web3

Trust in Web3 is not a single dimension – it is a layered stack of five distinct questions that no single provider answers completely. Conflating them leads teams to select the wrong tools, build false confidence in partial coverage, and leave entire attack surfaces unprotected.

• Identity Trust: Is this a real, unique human with verifiable identity?
• Behavioral Trust: Is this wallet genuinely active, non-Sybil, and behaviorally high-quality?
• Social Trust: Does the community vouch for this person’s credibility and track record?
• Token and Protocol Trust: Is this smart contract safe? Is this token’s community genuine, or a manufactured rug pull setup?
• Agent Verification: Is this AI agent wallet – and the wallet funding it – trustworthy before I allow autonomous interaction with my protocol?

Each question requires different data, different methodology, and different tools. Furthermore, passing one trust check says nothing about performance on the others. A wallet can pass KYC, hold a clean Sybil score, have positive Ethos vouches, and still carry a 0.87 fraud probability in ChainAware’s behavioral model – because each layer catches threats that the others are structurally blind to. For how behavioral intelligence layers into the broader Web3 intelligence stack, see our Web3 Wallet Auditing Providers guide.

Category 1: Identity Trust – KYC and Document Verification

Identity trust answers the most foundational question: is this a real, unique person with verifiable government-issued identity? KYC providers verify document authenticity, biometric liveness, sanctions and PEP exposure, and ongoing AML obligations. Their 2026 market data reveals the scale of the problem – Sumsub analyzed over 23,000 fraud attempts daily and found that 55% of crypto firms confirmed experiencing fraud at least once in 2025, while 15% were unsure whether it happened at all.

Sumsub – The Market Leader

Sumsub works with 8 out of 10 top global crypto exchanges and covers the complete verification lifecycle: document verification (14,000+ document types across 220+ countries), biometric face matching, liveness detection, AML/PEP screening, Travel Rule compliance, KYB for businesses, and ongoing transaction monitoring. Their April 2026 State of the Crypto Industry report found that 74% of crypto firms now prioritize verification accuracy over onboarding speed – a structural shift from the growth-at-all-costs approach that dominated 2021-2023. According to Sumsub’s 2026 research , crypto companies are entering a phase where operational discipline matters more than momentum.

Civic Pass – Blockchain-Native KYC

Civic provides blockchain-native KYC through Civic Pass – an on-chain credential issued after off-chain identity verification. Available in 190+ countries, Civic covers liveness checks, document KYC, watchlist and PEP screening, VPN detection, and email and phone verification. The key differentiator is portability: users verify once and reuse their Civic Pass across any integrated DApp without re-submitting documents. This verify-once model significantly reduces onboarding friction while maintaining compliance. Fractal ID offers a similar Web3-native multi-chain identity stack positioned as a lighter-weight alternative for DeFi-native teams.

The Structural Limitation of KYC

Every KYC provider shares one fundamental constraint: they require active user participation. Document uploads, face scans, and liveness checks create friction that reduces conversion and makes KYC unsuitable for fully permissionless DeFi protocols. More critically, KYC verification is a point-in-time snapshot – it confirms who a wallet belonged to at verification date but says nothing about that wallet’s subsequent behavioral risk. A wallet can pass KYC completely and still develop a 0.91 fraud probability the following month based on new behavioral patterns. This gap is precisely where ChainAware’s behavioral layer operates. For how KYC connects to the broader compliance picture, see our Predictive AI for KYC and AML guide and our MiCA Compliance guide.

Free – No Signup Required

Audit Any Wallet in 1 Second – Fraud Score, AML Status, Behavioral Profile

Paste any address and get fraud probability (98% accuracy), AML/OFAC status, experience level, 12 intention probabilities, and Wallet Rank. Free, sub-second, no account needed. ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, SOL.

Audit Any Wallet Free Wallet Auditor Guide

Category 2: Behavioral Trust – On-Chain Reputation and Sybil Resistance

Behavioral trust operates entirely on public on-chain data – no user action required, fully permissionless, privacy-preserving. Providers in this category analyze wallet transaction history to answer whether a wallet is a genuine, active participant or a bot, farmer, or coordinated Sybil attacker. Two distinct methodologies dominate this space.

Trusta Labs / TrustScan – AI/ML Graph Pattern Detection

Trusta Labs applies Graph Neural Networks (GCNs, GATs) and Recurrent Neural Networks (GRUs, LSTMs) to detect four specific Sybil attack signatures in wallet transaction graphs: star-like transfer patterns (hub-and-spoke funding), chain-like transfer patterns (sequential wallet funding), bulk operations (coordinated timing), and similar behavior sequences (identical transaction fingerprints across wallets). Founded by ex-Alipay AI leaders, Trusta has analyzed 570 million wallets and integrated into Gitcoin Passport (1.54 points per verified address) and Galxe. For the complete Sybil protection landscape comparison, see our Web3 Sybil Protection Systems guide.

Nomis, RubyScore, and ReputeX – Activity-Based Reputation

Nomis scores historical activity volume, protocol diversity, wallet age, and cross-chain engagement across 50+ chains – issuing output as a portable on-chain NFT attestation. RubyScore provides a simpler activity quality filter with faster integration, suitable for projects needing lightweight Sybil gating without deep analysis. ReputeX takes a fusion approach combining multiple behavioral paradigms, though production deployment evidence remains limited.

All behavioral trust providers share a critical structural limitation: they are reactive and binary. They describe past behavior and produce pass/fail gates. None predicts future behavior, none scores behavioral quality beyond activity volume, and none provides the downstream deployment layer that converts screened wallets into transacting users. ChainAware closes all three gaps simultaneously. For keeping airdrop and IDO distributions clean from Sybil wallets, see the Sybil-Resistant Token Distribution use case. For the full reputation score comparison including Nomis, Ethos, Cred Protocol, and UTU, see our Web3 Reputation Score Comparison.

Category 3: Social Trust – Community Vouching and Staked Endorsements

Social trust builds reputation through community mechanisms rather than on-chain transaction analysis. Where behavioral trust asks “what has this wallet done?”, social trust asks “what does the community say about this person?” These are orthogonal signals – a wallet can have strong behavioral scores and poor social reputation, or vice versa. Combining both provides significantly more robust trust assessment than either alone.

Ethos Network – Staked Social Proof-of-Trust

Ethos Network launched mainnet on Base in January 2025 and represents the most sophisticated social trust system in Web3. The core mechanism requires users to stake ETH when vouching for others – making trust claims financially consequential rather than costless clicks. Participants can also slash (penalize) others for proven bad behavior, reducing the voucher’s staked amount. Credibility scores derive from the platform’s most engaged and reputable members, creating a peer-weighted system rather than simple vote counting. Ethos.Markets launched alongside the main platform, allowing users to financially speculate on trust scores through an AMM using the LMSR algorithm. Additionally, a Chrome extension shows Ethos credibility scores directly on Twitter/X profiles – bringing social trust verification into ambient browsing. The project raised $1.75M pre-seed from 60 Web3 community angel investors.

The primary limitation of Ethos is coverage: it only scores wallets with established Ethos profiles. Anonymous wallets with no Ethos history return no signal – which describes the vast majority of wallets that connect to any DeFi protocol. Furthermore, Ethos measures social community trust among known participants, not the behavioral quality or fraud risk of a wallet. A highly vouched wallet can still carry significant fraud probability based on its transaction patterns.

Karma3 Labs / OpenRank – Algorithmic Trust Propagation

Karma3 Labs builds ranking and reputation infrastructure using the EigenTrust algorithm – originally designed to improve trust propagation in distributed systems and later applied to Google’s PageRank concept. Their $4.5M seed round came from Galaxy and IDEO CoLab. OpenRank enables developers to build personalized search, discovery, and recommendation systems on top of on-chain social graph data, with notable deployment for Farcaster social graph trust scoring. Where Ethos is community-driven (humans staking on humans), Karma3 is algorithm-driven (EigenTrust computing trust propagation through the social graph). According to Karma3 Labs’ documentation , the OpenRank protocol enables context-aware trust that adapts to different application requirements.

UTU Protocol – Relationship-Context Trust

UTU Protocol builds trust through a non-transferable reputation token (UTT) and staked endorsements, with emphasis on relationship context – a user’s trusted network’s opinions carry more weight than a stranger’s. The UTT cannot be traded, only earned through genuine trust endorsements that later prove correct. Africa DeFi focus and Internet Computer deployment distinguish UTU from the other social trust providers. All three social trust systems – Ethos, Karma3, and UTU – address a genuine trust dimension that on-chain behavioral analysis cannot capture: long-standing human relationships and community standing that extend beyond wallet transaction history.

Category 4: Token and Protocol Trust – Code Audits, Short and Long Rug Pulls

This category covers two entirely different trust problems that are commonly conflated. Smart contract code audits (CertiK, Hacken) verify whether the code is technically safe. Behavioral token trust tools (ChainAware) verify whether the operator behind the code and the community around the token are genuine. CertiK’s H1 2025 Hack3d report recorded $2.47 billion lost across 344 incidents – with wallet compromise the largest category and phishing the most frequent. This confirms that the most expensive 2026 threats live around the code, not inside it. Yet most teams invest entirely in code audits while ignoring behavioral token trust.

CertiK and Hacken – Smart Contract Code Audits

CertiK is the dominant smart contract audit and security monitoring platform with 5,000+ enterprise clients, $600B+ in assets secured, and 180,000+ vulnerabilities identified. Its Skynet platform delivers real-time on-chain incident monitoring and alerting. The Spoq formal verification engine uses AI-driven automation to mathematically prove system correctness – validated at peer-reviewed venues OSDI 2023 and ASPLOS 2026. According to CertiK’s platform documentation , Skynet Enterprise meets the transparency and risk visibility requirements of institutional participants and regulators. Hacken provides security audits and a TRUST Score framework evaluating protocols across transparency, security, code quality, and community metrics – their 2025 TRUST Report tracked $3.6B stolen, with 57.8% from access-control exploits.

Both CertiK and Hacken audit code at a specific point in time. Neither analyzes the behavioral history of the wallet that deployed the contract, the fraud profile of the wallets that provided liquidity, or the quality of the token’s holder community. These are not limitations of the audit providers – they are simply a different layer of the trust stack. The critical mistake is treating a clean CertiK audit as comprehensive protection when 95% of PancakeSwap pools end in rug pulls and 99% of Pump.fun tokens extract money from buyers – most of them with no code vulnerabilities whatsoever. For the complete rug pull detection landscape, see our Rug Pull Detection guide.

ChainAware Rug Pull Detector – Short Rug Pull Detection via Creator Chain Traversal

ChainAware’s Rug Pull Detector (see the complete Rug Pull Detector guide) addresses the behavioral layer that code audits structurally cannot reach. The core insight: experienced rug pullers deliberately pass code reviews. Their malicious intent is not in the contract – it is in the wallet that deployed it, the wallets that provided liquidity, and the behavioral history that accumulates before the exploit.

The methodology uses creator chain traversal – a recursive process that climbs the deployment chain until it finds the terminal human-controlled wallet:

Token Contract
  └── contractCreatorAddress
         ├── If human wallet → score with predictive_fraud (98% accuracy)
         └── If contract (factory / proxy / deployer)
                  └── creator of THAT contract
                         ├── If human wallet → score with predictive_fraud
                         └── If contract → continue traversal...
                                  └── ... until terminal human wallet found

Sophisticated rug pull operators use deployment layers – factory contracts, proxy deployers, script contracts – specifically to sever the visible link between their personal wallet history and the new token. A naive rug pull checker that looks only one level up the creator chain sees a clean contract address and reports Low Risk. ChainAware’s traversal climbs through every layer until it finds the human operator, then scores their full behavioral fraud history across 19 forensic categories.

The “New Wallet” Risk Signal

When traversal terminates at a wallet created days or weeks before the token deployment, this carries elevated risk even without active fraud indicators. Legitimate protocol developers operate from established wallets with meaningful DeFi history. A new wallet at the chain terminus scores “New Address” rather than “Not Fraud” – and that distinction matters because it means the operator deliberately created a fresh wallet to avoid being traced from prior exploits. No prior fraud record is itself the red flag when combined with brand-new wallet age and a token launch event.

Liquidity Provider Fraud Scoring – The Second Dimension

Beyond creator analysis, the Rug Pull Detector independently scores every liquidity event. The `liquidityEvent` array returns every add/remove liquidity transaction with the `from_address` scored for fraud probability. Consequently, this catches the pattern where a clean creator wallet deploys the token but mixer outputs or darknet-linked wallets provide the liquidity – making those wallets the actual economic actors who will drain the pool. Creator analysis and liquidity provider scoring together cover the behavioral attack surface that 20+ code-level risk indicators alone miss. The overall tool achieves 68% detection accuracy before pool collapse – a dynamic prediction that updates as new behavioral data arrives. For how this fits the complete token analysis workflow, see our Fake Token Identification guide.

ChainAware Token Rank – Long Rug Pull Detection via Community Quality Scoring

Short rug pulls drain liquidity and disappear quickly. Long rug pulls unfold differently – the team builds apparent traction over months or years through manufactured social followers, inflated trading volume, and partnership announcements, while the actual holder base consists predominantly of bots, farm wallets, low-quality airdrop farmers, and coordinated Sybil wallets. When the team exits, price collapses because genuine community never existed. The fraud was in the community quality, not the code – and therefore invisible to any audit.

Token Rank detects long rug pulls by computing the median Wallet Rank across every meaningful token holder. Lower median Wallet Rank means higher holder quality. A token with 50,000 holders but a median Wallet Rank dominated by near-zero scores – new, inactive, single-chain wallets – has a manufactured community. A token with 5,000 holders and a median Wallet Rank of 2-3 has a genuinely high-quality community of experienced DeFi participants who chose to hold. Token Rank covers 2,500+ tokens across Ethereum, BNB Smart Chain, and other networks, exposing `communityRank`, `normalizedRank`, `totalHolders`, and the `topHolders` list with individual wallet profiles. No code audit, no tokenomics review, and no social metric reveals this – because it requires behavioral analysis of every individual holder. Token Rank is therefore the only tool that catches long rug pulls before they execute. See the Wallet Rank learn guide for how the underlying scoring methodology works, and the complete methodology in our Wallet Rank guide.

68% Detection Accuracy Before Pool Collapse

ChainAware Rug Pull Detector + Token Rank – Catch What Code Audits Miss

Creator chain traversal to the terminal human wallet. Liquidity provider fraud scoring. Community quality analysis across all holders. Short rug pulls and long rug pulls – both detected before you lose capital. Free for individual checks. MCP-native for AI agents.

Check Any Token Free Rug Pull Detection Guide

Category 5: Agent Verification – Why Voting Fails and Creator Chain Works

AI agents now execute DeFi strategies, manage DAO treasuries, run compliance pipelines, and interact with protocols autonomously – with significant capital and without any human in the loop. Worldchain noted that by some estimates 80% of blockchain transactions are already automated. As the Web3 agentic economy scales from thousands to millions of autonomous agent wallets, verifying the trustworthiness of those agents before granting them protocol access has become a critical infrastructure requirement. Every other trust category was designed for human wallets. None addresses the specific challenge of agent wallet verification. For the broader context of how AI agents are reshaping Web3 operations, see the ChainAware For AI Agents overview, our Web3 Agentic Economy guide and our 12 Blockchain Capabilities for AI Agents guide.

Why ERC-8004 and Voting-Based Agent Trust Fails

ERC-8004 and similar proposals attempt to build agent trust through on-chain reputation voting – agents vouch for each other, accumulate endorsements, and build scores based on peer consensus. The mechanism borrows from social trust systems like Ethos Network. However, it fails structurally when applied to agents rather than humans.

The manipulation attack is trivial and undetectable. A malicious operator deploys 50 agent wallets at near-zero cost. Each one votes up every other wallet in the cluster. Within days, all 50 accumulate high trust scores with zero genuine behavioral history. They then simultaneously vote down legitimate competing agents to suppress rival scores. The entire trust signal is manufactured – there is no Sybil resistance at the voting layer, no requirement for prior behavioral history, and no economic cost sufficient to deter a well-funded operator.

The deeper structural problem: AI agents have no social friction. When Ethos Network requires staked ETH behind a vouch, a human who vouches fraudulently loses money and social standing. An AI agent operator who creates 50 voting wallets and cross-vouches loses nothing – the wallets are free, the stake can be minimal, and the cluster rotates after each manipulation cycle. Voting-based agent trust is therefore not just gameable; it is machine-speed gameable by the very entities it is supposed to screen.

The Correct Approach: Creator Chain Traversal + Feeder Wallet Analysis

Agent trust does not require voting. It requires exactly the same methodology as short rug pull detection – creator chain traversal to the terminal human wallet, combined with independent feeder wallet analysis. The logic is identical:

Agent Wallet
  └── Who deployed this agent's controlling contract?
         ├── If human wallet → score with predictive_fraud
         └── If contract (factory / multi-sig / deployer)
                  └── creator of THAT contract
                         ├── If human wallet → score with predictive_fraud
                         └── If contract → continue traversal...

Feeder Wallet (who funds this agent's operations)
  └── Score independently with predictive_fraud
  └── Check: mixer interactions, darkweb, money_laundering,
             phishing, stealing_attack, sanctioned, 14 other forensic categories

This approach is manipulation-proof for a fundamental reason: blockchain history is immutable. A malicious operator cannot retroactively clean their terminal human wallet’s record of honeypot deployments, mixer interactions, or fraud associations. They cannot make a 6-day-old feeder wallet appear to have 3 years of legitimate DeFi history. They cannot remove the `honeypot_related_address` flag from a wallet that previously funded exit scams. The historical record makes creator chain analysis structurally Sybil-resistant in a way that no voting mechanism – regardless of its design – can achieve.

The Feeder Wallet – The Most Important Agent Trust Signal

Feeder wallet analysis is particularly critical because it catches the attack pattern that creator chain analysis alone misses. A sophisticated operator creates a clean deployment wallet specifically for the agent – passing creator chain analysis – while funding operations from a compromised wallet that reveals their actual risk profile. Both checks are necessary. Together they close the attack surface that any single-wallet screening approach leaves open.

ChainAware chainaware-agent-screener – The Only Agent Verification Tool

The `chainaware-agent-screener` (see Security & Fraud Agents) is the only purpose-built AI agent trust verification tool in the Web3 market. It screens both the agent wallet and the feeder wallet simultaneously, producing an Agent Trust Score from 0 to 10 (0 = confirmed fraud, 1 = new/insufficient data, 2-10 = normalized reputation). The agent uses both `predictive_fraud` and `predictive_behaviour` MCP tools and deploys via git clone and an API key – no custom engineering required.

Example output for a high-risk agent (from live documentation):

AGENT SCREENING
Agent Wallet: 0xSuspectAgent... | Network: Base
Feeder Wallet: 0xFundingSource... | Network: Base

Agent Trust Score: 2.1 / 10 ⚠

Agent Wallet:
  Fraud verdict: Elevated risk (0.52)
  On-chain age: 6 days ⚠
  Behaviour: Unusual - rapid fund movement, no prior agent pattern

Feeder Wallet:
  Fraud verdict: HIGH RISK (0.81) 🛑
  AML flags: Mixer interaction (Tornado Cash equivalent)
  Connected to 2 confirmed exit scams

→ 🛑 Do not allow. Feeder wallet has confirmed fraud indicators.
  Block and report to your security team.

The agent handles natural language prompts: “Is this agent wallet safe? 0xAgent… on Ethereum”, “Screen these 5 AI agents before we allow them into our protocol: [list of agent+feeder pairs]”, or “Can I trust this agent? It wants to execute trades on my behalf.” The growing adoption of multi-agent frameworks including ElizaOS, Fetch.ai, and Coinbase AgentKit makes this verification capability increasingly critical – every protocol integrating third-party agent infrastructure now requires a trust layer to screen those agents before granting access. For the complete AI agent capability reference, see our AI Agents for Web3 roadmap and our Blockchain Data Providers guide.

32 MIT-Licensed Open-Source Agents – Deploy in Minutes

Agent Screener · Governance Screener · Fraud Detector · AML Scorer – All via git clone

Screen AI agent wallets and feeder wallets before granting protocol access. Manipulation-proof via creator chain traversal – not gameable by voting clusters. Works with Claude, GPT, and any MCP-compatible LLM. No custom build required. See the full Ready-Made Agents catalogue.

View Agents on GitHub Prediction MCP Guide

ChainAware’s Unique Position Across All Five Categories

Having mapped all five categories, ChainAware’s competitive position becomes precise. Across the five trust problems, ChainAware plays a distinct role in each – complementary in some, competing and extending in others, and uniquely positioned as sole provider in two.

Category 1 (Identity Trust) – Complementary

KYC providers verify identity at a point in time. ChainAware adds ongoing behavioral fraud prediction that operates continuously after verification – catching wallets whose risk profile changes after KYC completion. Additionally, ChainAware’s permissionless approach covers the DeFi protocols that KYC is unsuitable for entirely, providing behavioral trust coverage without requiring user participation. The two layers are additive: KYC for regulatory compliance, ChainAware for continuous behavioral risk monitoring.

Category 2 (Behavioral Trust) – Competing and Extending

ChainAware operates in the same on-chain, permissionless, privacy-preserving space as Trusta, Nomis, and RubyScore – but answers fundamentally richer questions. Trusta detects coordination graph patterns. Nomis scores activity volume. ChainAware adds 22-dimension behavioral profiles, 12 forward-looking intention probabilities, 19-category forensic fraud analysis, AML/OFAC screening, governance tier classification, and 32 deployable agents. Furthermore, ChainAware is the only provider with a growth deployment layer – converting screened traffic into transacting users rather than just producing eligibility scores. For the full behavioral intelligence comparison, see our Web3 Analytics Tools Comparison.

Category 3 (Social Trust) – Complementary

Ethos, Karma3, and UTU measure what the community says about known participants. ChainAware measures what blockchain history predicts about any wallet’s future behavior. These signals are orthogonal: a highly vouched wallet can have high fraud probability, and a wallet with zero Ethos profile can have excellent behavioral quality scores. Both signals together provide more robust trust assessment than either alone. The practical combination: Ethos credibility scores for known community participants with established social standing, ChainAware behavioral intelligence for every wallet regardless of social profile.

Category 4 (Token and Protocol Trust) – Partially Competing

CertiK and Hacken own the code audit layer – ChainAware does not compete with smart contract formal verification. However, ChainAware owns the behavioral token trust layer that code audits structurally cannot reach. Rug Pull Detector (creator chain traversal + liquidity provider fraud scoring = short rug pull detection) and Token Rank (median Wallet Rank across all holders = long rug pull detection) address attack surfaces where CertiK and Hacken have no tools. A complete protocol trust stack requires both: CertiK/Hacken for code safety and ChainAware for behavioral token trust.

Category 5 (Agent Verification) – Sole Provider

No other provider has built agent wallet trust verification. ERC-8004 and voting-based proposals are manipulable at machine speed. Creator chain traversal with feeder wallet analysis – the methodology ChainAware applies through `chainaware-agent-screener` – is the only manipulation-proof approach, and ChainAware is the only provider that has implemented it. As the agentic economy scales, this category will grow from a niche capability to foundational infrastructure – and ChainAware currently has no competition in it.

The Recommended Trust Stack for 2026

No single provider covers all five trust dimensions. Consequently, the most sophisticated protocols in 2026 layer multiple tools addressing different attack surfaces. The following combinations map to the most common protocol types.

Regulated VASPs and Centralized Exchanges

Sumsub for document KYC, Travel Rule, and KYB compliance (mandatory regulatory layer) + ChainAware for ongoing behavioral fraud prediction and transaction monitoring (continuous behavioral layer) + CertiK audit for any smart contracts in the stack (code layer). Together these cover all five trust dimensions except social trust, which becomes relevant for DAO-adjacent products.

Permissionless DeFi Protocols

CertiK or Hacken for pre-launch smart contract audit (code layer) + ChainAware Rug Pull Detector pre-launch screening of the deployer wallet and liquidity setup (behavioral token trust) + Trusta or Nomis for airdrop Sybil filtering (campaign gate) + ChainAware Wallet Rank and fraud probability at wallet connection (quality and safety gate) + ChainAware Growth Agents to convert screened wallets into transacting users (deployment layer). For the complete DeFi compliance framework, see our DeFi Compliance Tools guide.

DAOs with Treasury and Governance

ChainAware `chainaware-governance-screener` before every governance vote (behavioral Sybil detection + tier classification + voting weight multipliers – the only tool that does this) + Ethos credibility scores for known community members (social layer) + Hacken TRUST Score for ongoing protocol security assessment. Additionally, ChainAware Token Rank continuously monitors holder community quality – detecting whether a coordinated low-quality holder base is accumulating governance tokens for a long-term governance attack. For the governance attack surface in depth, see our Governance Screeners guide.

Protocols Integrating Third-Party AI Agents

ChainAware `chainaware-agent-screener` for every third-party agent requesting protocol access – screening both the agent wallet and feeder wallet before granting any permissions + `chainaware-transaction-monitor` for ongoing real-time scoring of every agent transaction (ALLOW / FLAG / HOLD / BLOCK pipeline action) + ChainAware fraud detector for the agent operator wallet if known. This creates a complete agent trust perimeter: pre-access screening, real-time transaction monitoring, and operator background verification. For how AI agents integrate with Web3 protocols at scale, see our Real AI Use Cases for Web3 guide.

Token Investors and Pre-Investment Due Diligence

ChainAware Rug Pull Detector on the token contract (creator chain traversal + LP fraud scoring = short rug pull risk) + ChainAware Token Rank on the token’s holder community (median Wallet Rank = long rug pull risk) + CertiK or Hacken audit status (code risk) together provide a three-dimensional token trust assessment that no single tool delivers alone. For how to identify fake tokens using these signals, see our Fake Token Identification guide.

ChainAware.ai – Behavioral Intelligence Across All Five Trust Layers

One Platform. Five Trust Dimensions. 32 Ready-Made Agents.

Free Wallet Auditor · Rug Pull Detector · Token Rank · Governance Screener · Agent Screener · Prediction MCP · Growth Agents. No annual contract. No procurement cycle. Active in minutes.

Free Wallet Audit Prediction MCP View Pricing

Frequently Asked Questions

What is the difference between KYC trust and behavioral trust?

KYC trust verifies that a wallet belongs to a real, identifiable person with verified government documents at a specific point in time. Behavioral trust analyzes what that wallet has done on-chain to predict future fraud risk and behavioral quality. Both are necessary because a wallet can pass KYC and subsequently develop high fraud probability, and a wallet can have strong behavioral quality scores without any KYC verification. The two layers address different attack surfaces: KYC for regulatory compliance and identity certainty, behavioral trust for ongoing fraud risk and quality assessment.

Can a smart contract audit replace rug pull detection?

No – and this is one of the most dangerous misconceptions in Web3 security. Smart contract audits verify code correctness at audit time. Rug pull detection verifies the behavioral risk of the human operator behind the code. Experienced rug pullers deliberately write clean, auditable code – their malicious intent is in their wallet’s history, not the contract. The creator chain traversal approach catches this by climbing through every deployment layer to find the terminal human wallet and score their full behavioral fraud history. A clean CertiK audit combined with a high-risk creator wallet is a warning sign, not a green light. Running both checks is the complete picture.

What is a long rug pull and how does Token Rank detect it?

A long rug pull unfolds over months or years. The team builds apparent community through manufactured holder counts, inflated trading volume, and partnership announcements – while the actual holder base consists of bots, farm wallets, and coordinated Sybil wallets with no genuine community intent. When they exit, the price collapses because no real community existed to support it. Token Rank detects this by computing the median Wallet Rank across all meaningful holders. A high holder count combined with near-zero median Wallet Rank scores – dominated by new, inactive, single-chain wallets – signals a manufactured community before the collapse. No code audit, tokenomics review, or social metric catches this because it requires behavioral analysis of the individual holder base, not the contract.

Why is ERC-8004 voting-based agent trust inadequate?

ERC-8004 and similar proposals are trivially manipulable because AI agents have no social friction or economic consequences for false vouching. A malicious operator deploys a cluster of 50 agent wallets at near-zero cost, cross-vouches them to inflate trust scores, and simultaneously downvotes legitimate competitors – all at machine speed. The manipulation cannot be distinguished from genuine vouching because agents produce no social record, no real-world identity damage, and no economic loss when participating in a trust manipulation scheme. Creator chain traversal with feeder wallet analysis solves this problem structurally – blockchain history is immutable, making it impossible to retroactively clean a terminal human wallet’s record of prior exploits, mixer usage, or fraud associations.

What does ChainAware provide that Ethos Network does not?

Ethos Network measures social community trust among known participants with established Ethos profiles. ChainAware measures behavioral intelligence for any wallet regardless of social profile. Practically, Ethos cannot screen anonymous wallets with no Ethos history – which describes most wallets connecting to any DeFi protocol. Furthermore, Ethos does not predict future behavior, does not provide AML/OFAC screening, does not detect token rug pull risk, and does not screen AI agent wallets. The two systems address orthogonal trust dimensions: Ethos for social standing among known community participants, ChainAware for behavioral risk assessment of any on-chain address.

How does ChainAware’s credit score relate to trust verification?

ChainAware’s credit score (1-9 trust score derived from AI analysis of on-chain inflows, outflows, fraud indicators, and social graph data) addresses financial trustworthiness specifically – answering whether a counterparty can be trusted to repay in undercollateralized lending contexts. This is a trust verification use case that no KYC provider, no Sybil detection tool, and no social trust platform addresses. KYC verifies identity but not creditworthiness. Behavioral reputation scores activity quality but not repayment reliability. ChainAware’s credit score is therefore a sixth trust dimension specifically relevant to DeFi lending protocols seeking to move beyond overcollateralized models. For the complete methodology, see our Web3 Credit Scoring guide.

What is the minimum setup to get meaningful trust coverage?

For most DeFi protocols, meaningful coverage starts with two free tools requiring zero engineering: the ChainAware Wallet Auditor for individual high-stakes wallet checks, and the Rug Pull Detector for any token or liquidity pool before depositing. Adding the free Web3 Behavioral Analytics pixel via Google Tag Manager provides population-level quality assessment of every wallet connecting to your DApp – revealing experience distribution, fraud rate, and intention profiles without any engineering sprint. For protocols needing automated coverage, the Prediction MCP connects any AI agent or LLM to all six intelligence dimensions in a single natural language tool call. For the complete integration reference, see our ChainAware Complete Product Guide.

External sources: Sumsub 2026 State of Crypto Industry Report · CertiK Platform Documentation · Karma3 Labs / OpenRank · Ethos Network · ChainAware Behavioral Prediction MCP – GitHub

The post Web3 Trust Verification Systems in 2026 – The Complete Five-Category Landscape first appeared on ChainAware.ai.