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.

ChainAware.ai appears in the On-Chain Intelligence subcategory alongside Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, and Blockaid. That placement represents meaningful institutional validation – CB Insights selects companies based on Mosaic health scores above 600 and equity funding recency since 2024, filtering out thousands of projects that do not meet the bar.

One additional data point makes ChainAware’s position unique across the entire 200-company map. ChainAware is the only Web3 AI token in the full list – and the only company in the On-Chain Intelligence category with a publicly traded token listed in CoinGecko’s AI category. Among 1,385 tokens in that category, ChainAware’s AWARE token is the single representative of on-chain intelligence and behavioral fraud detection.

This article explains what that combination means, why it matters for enterprise buyers, developers, and investors – and how ChainAware’s specific products produce outcomes that no other company on the map delivers.

What Is the CB Insights AI Fraud Prevention Market Map?

CB Insights is the institutional research and intelligence platform that tracks private company health scores, funding rounds, and competitive landscapes for 100,000+ technology companies. Its market maps represent the authoritative view of emerging technology categories – used by venture capital firms, corporate development teams, enterprise procurement departments, and regulatory bodies to identify leading vendors and benchmark competitive positioning.

The AI Fraud Prevention Market Map, published June 2, 2026, covers the companies building infrastructure to detect, prevent, and manage fraud in the AI era. That framing is deliberate and significant – it separates the legacy fraud prevention market (rules-based, human-reviewed, slow) from the emerging category of AI-native fraud prevention (predictive, automated, operating at agent speed).

Why This Map Exists Now

CB Insights publishes category maps when a market reaches sufficient maturity and investment volume to justify systematic mapping. The timing of the AI Fraud Prevention map reflects three converging forces that have made fraud prevention one of the most actively funded technology categories of 2026.

First, AI-generated fraud has scaled dramatically. Deepfake video scams, synthetic identity creation, and AI-powered phishing campaigns have collectively pushed AI-based fraud losses toward the $40 billion annual mark projected by industry analysts. Traditional fraud detection tools were built for human-speed fraud – they cannot detect AI-generated attacks operating at machine speed.

Second, the agentic economy has created entirely new fraud surfaces. AI agents transacting autonomously on behalf of humans do not carry passports, credit histories, or biometric signatures. Every identity and trust system built over the last 30 years assumes the actor is human. Agents need identity and trust infrastructure built specifically for how they operate – a gap that every major new crypto VC fund has identified as their primary investment thesis.

Third, stablecoin adoption has accelerated on-chain transaction volumes toward levels that require institutional-grade compliance infrastructure. According to CB Insights, stablecoin transaction volumes in 2025 grew to double-digit trillions – approaching Visa and Mastercard combined. That volume requires fraud detection, AML screening, and behavioral intelligence that scales with it.

CB Insights Map Structure

The map organizes 200+ companies into three primary sections, each with multiple subcategories:

• Agentic Trust Infrastructure – Agent observability and evaluation, Agent authentication and authorization (KYA), Agent runtime governance and oversight
• Digital Identity and Verifiable Credentials – Decentralized identity (DID), Passwordless authentication, Post-quantum identity, Know Your Customer (KYC), Biometric identity
• Fraud Detection and Prevention – Fraud orchestration and case management, Risk scoring and signals, AML compliance, AI-generated content detection, On-chain intelligence, Transaction monitoring, Bot detection, Graph analytics and network fraud, Account takeover (ATO) protection

ChainAware sits in the Fraud Detection and Prevention section, specifically in the On-Chain Intelligence subcategory – the most directly Web3-native category on the entire map.

The On-Chain Intelligence Category – Who Made the List

The On-Chain Intelligence subcategory contains eleven companies. Understanding each one – what they do, who they serve, and where they differentiate – establishes the competitive context in which ChainAware operates.

Chainalysis

Chainalysis is the dominant forensic intelligence platform for blockchain – built originally for law enforcement agencies including the FBI, DEA, and IRS. Its Know Your Transaction (KYT) product handles VASP compliance screening, and its investigation tools reconstruct transaction graphs across chains for evidence-grade fund flow analysis. Enterprise pricing ranges from $100,000 to $500,000 annually. Chainalysis is reactive by design: it traces where funds came from after transactions have occurred, which makes it essential for post-incident investigation but structurally unable to prevent fraud before execution. According to Chainalysis’s platform documentation , its clustering heuristics and entity attribution cover hundreds of major counterparties across multiple blockchains.

Elliptic

Elliptic serves a similar VASP compliance use case with a stronger European and institutional focus. Its blockchain analytics cover transaction monitoring, wallet screening, and sanctions compliance for exchanges, banks, and asset managers. Elliptic has expanded into DeFi protocol screening and NFT risk analysis – but remains fundamentally a forensic and compliance tool rather than a predictive intelligence platform.

TRM Labs

TRM Labs occupies the government and financial institution segment with the highest Mosaic score of any company in the On-Chain Intelligence category. Its platform serves FinCEN, OFAC, and major global banks – and has expanded into proactive threat intelligence that goes beyond pure reactive forensics. Spencer Bogart of Blockchain Capital invested in TRM Labs, citing the compliance infrastructure gap as one of the clearest institutional crypto needs.

Crystal Intelligence, Blockaid, and the Remaining Companies

Crystal Intelligence provides blockchain analytics and AML compliance with particular strength in European markets and cross-border transaction monitoring – covering 40+ blockchains. Blockaid approaches on-chain security from a different angle: transaction simulation and malicious dApp detection. Blockaid is now integrated into MetaMask, Coinbase Wallet, and Rainbow – but it protects at the transaction level rather than scoring the behavioral history of the parties behind transactions. Anchain.ai, CUBE AI, Merkle Science, NOTA BENE, and TestMachine occupy specialist positions serving government, institutional, and testing use cases across the category.

ChainAware.ai – The Behavioral Prediction Layer

ChainAware occupies a position in the On-Chain Intelligence category that no other company covers – behavioral prediction. While every other company answers “what has this wallet done or where did these funds come from?”, ChainAware answers “what will this wallet do next, and is this wallet likely to commit fraud before it acts?” That forward-looking prediction capability, combined with being the only Web3 AI token in the full 200-company CB Insights list, makes ChainAware uniquely positioned at the intersection of enterprise compliance and the decentralized token economy.

Why CB Insights Inclusion Matters for Enterprise Buyers

Enterprise procurement decisions for security and compliance infrastructure are significantly influenced by analyst validation. A security or compliance team evaluating on-chain intelligence vendors does not start with a Google search – they start with CB Insights, Gartner, Forrester, or IDC market maps. Inclusion in these maps is the difference between being considered and not being considered in enterprise vendor evaluations.

The Mosaic Score Gate

CB Insights selects companies based on its proprietary Mosaic score – a composite health measure incorporating funding recency, investor quality, web traffic, news sentiment, team quality, and patent activity. The AI Fraud Prevention map requires a Mosaic score above 600 and equity funding since 2024. Most projects in the blockchain space never appear on a CB Insights map because they fail either the Mosaic score threshold or the funding recency requirement. ChainAware’s inclusion confirms that its profile meets institutional investment standards – a signal that matters to the compliance officers, procurement teams, and CISOs who use CB Insights to shortlist vendors.

The Reference Check Effect

When a DeFi protocol’s compliance team receives a proposal from ChainAware, the first thing they do is verify the company’s credibility through third-party sources. The CB Insights listing now serves as that third-party validation – alongside CoinGecko’s AI category listing, the AWARE token on BSC, and ChainAware’s GitHub repository of open-source MIT-licensed agent definitions. Credibility signals compound. Each additional validation source reduces the friction of the enterprise sales cycle and increases the probability of converting enterprise interest into a signed API contract.

The CoinGecko AI Category – 1,385 Tokens, One Web3 AI Fraud Prevention Token

CoinGecko’s AI category currently lists 1,385 tokens – representing the full spectrum of AI-related blockchain projects, from Bittensor (decentralized AI compute) to Render (GPU network) to Virtuals Protocol (AI agent launchpad) to dozens of AI-themed meme coins. The category spans legitimate infrastructure projects, speculative tokens, and everything between.

Among these 1,385 tokens, ChainAware’s AWARE token is the only one building on-chain intelligence and behavioral fraud detection as its core product. None of the major forensic compliance companies – Chainalysis, Elliptic, TRM Labs, Crystal Intelligence – have tokens. None of Blockaid, Anchain.ai, Merkle Science, or NOTA BENE have tokens. They are pure SaaS companies with no token economy.

Why No Token Is the Default for Compliance Companies

Most on-chain intelligence companies avoid tokens for regulatory reasons – a tradeable token creates securities law complexity in most jurisdictions. Chainalysis, TRM Labs, and Elliptic have collectively raised over $1 billion in venture capital while deliberately remaining token-free. Their customers (banks, regulated exchanges, government agencies) cannot hold or use utility tokens as payment. ChainAware’s bifurcated model – enterprise API subscriptions for institutional clients plus the AWARE utility token for Web3 ecosystem participants – allows it to serve both audiences simultaneously without compromising either relationship.

The Unique Intersection

The combination of CB Insights validation and CoinGecko AI category listing creates a position that no competitor occupies. Companies on the CB Insights map without tokens serve institutional clients through SaaS contracts – their distribution is purely through enterprise sales cycles. Companies in the CoinGecko AI category without CB Insights validation are building token economies without institutional credibility. ChainAware sits at the intersection – credible enough for enterprise evaluation and token-native enough to participate in the decentralized economy it analyzes.

How ChainAware Differs From Every Other Company on the Map

Understanding ChainAware’s differentiation requires examining five dimensions where it diverges fundamentally from every other company in the On-Chain Intelligence category.

Dimension 1 – Prediction vs. Forensics

Every other company in the On-Chain Intelligence category is forensic – backward-looking by design. Chainalysis traces where funds came from. Elliptic reconstructs transaction graphs. TRM Labs identifies sanctioned counterparties. Crystal Intelligence monitors cross-border fund flows. All four describe the past. ChainAware predicts the future. Its behavioral ML models, trained on 20M+ wallet personas across 8 blockchains, produce probability scores for what a wallet will do next – not descriptions of what it has done. That prediction happens in milliseconds, before any transaction occurs, based on behavioral patterns that professional fraudsters cannot disguise by using clean contract code.

Dimension 2 – Fraud Tech and Growth Tech Combined

The CB Insights map treats fraud prevention as a purely defensive category – a cost center that organizations pay for to stay compliant and avoid losses. ChainAware reframes the category entirely by combining fraud prevention with growth intelligence in a single platform. ChainAware’s 20M+ wallet personas do not just tell a compliance team whether to block a wallet – they also tell a product team which content to show it, which features to surface, and which growth campaign to trigger. A wallet with high Lend intention and low fraud probability gets surfaced lending products automatically. A wallet with high fraud probability gets blocked before it enters the funnel. Both decisions come from the same behavioral intelligence layer.

Dimension 3 – MCP-Native Delivery for AI Agents

AI agents need behavioral intelligence delivered in the format they can consume – structured predictions via the Model Context Protocol (MCP), not raw blockchain data that requires further analysis. According to Anthropic’s Model Context Protocol documentation , MCP is rapidly becoming the standard integration layer for AI agent tool access. ChainAware’s Prediction MCP delivers complete behavioral profiles – fraud probability, all 12 intention scores, experience level, risk appetite, AML status – in a single structured response that any AI agent can act on without blockchain expertise. For how this works in practice, see our Prediction MCP guide .

Dimension 4 – Token-Native Economic Model

ChainAware’s AWARE token creates an economic flywheel that enterprise-only SaaS competitors cannot replicate. Token holders who stake AWARE unlock higher API rate limits and premium intelligence tiers. Developers who build integrations with ChainAware’s API earn AWARE rewards. As the platform’s wallet persona dataset grows – currently at 20M+ profiles – the intelligence quality improves, increasing the value of AWARE access.

Dimension 5 – The Free Entry Point

Chainalysis charges $100,000 to $500,000 annually. TRM Labs requires enterprise negotiations. Elliptic does not publish pricing. ChainAware’s Wallet Auditor delivers the complete Web3 Persona for any address – free, no signup, in under one second. Any developer, compliance officer, or investor can experience the full depth of ChainAware’s behavioral intelligence without a sales conversation. For the complete dimension-by-dimension breakdown, see our Wallet Auditor guide .

Predictive Intelligence vs. Forensic Intelligence – The Critical Distinction

The most important conceptual distinction in the On-Chain Intelligence category is between forensic and predictive intelligence. Understanding this distinction explains why the entire category is funded heavily – and why ChainAware’s predictive position is structurally different from the forensic majority.

What Forensic Intelligence Does

Forensic intelligence analyzes the complete history of blockchain transactions to reconstruct fund flows, identify sanctioned counterparties, and attribute addresses to known entities. It answers: “Where did these funds come from, and who has touched them?” This capability is essential for post-incident investigation. However, forensic intelligence is structurally reactive – it requires the fraud to have already happened, or at minimum for the fraudulent address to already appear in its entity database. A professional operator using a fresh wallet that has never appeared in Chainalysis’s database is invisible to forensic tools until they commit their first recorded offense.

What Predictive Intelligence Does

Predictive intelligence analyzes behavioral patterns – not just transaction histories – to forecast what a wallet will do next and what the probability of fraud is before any transaction executes. ChainAware’s behavioral ML models train on 20M+ wallet personas – learning the behavioral signatures that distinguish legitimate DeFi users from professional fraud operators, Sybil wallets, airdrop farmers, and governance attackers. A professional fraudster can use clean contract code. They cannot mask their behavioral pattern across 20M+ training examples. The model detects the operator, not just the incident. For the complete technical comparison, see our Forensic vs AI-Powered Analytics guide .

The 98% Accuracy Benchmark

ChainAware backtested its fraud detection model on CryptoScamDB – the largest publicly available database of documented crypto fraud incidents – achieving 98% prediction accuracy. The model correctly identified fraudulent wallets before they committed their recorded offense in 98 out of every 100 cases in the test set. For compliance teams operating under MiCA or similar frameworks, that accuracy level dramatically reduces the manual review burden. For the complete MiCA compliance stack, see our MiCA Compliance at 1% of Chainalysis Cost guide .

ChainAware Rug Pull Detector – 90.1% Prediction Accuracy

Rug pulls represent the most damaging category of DeFi fraud by absolute dollar value. ChainAware’s Rug Pull Detector – trained specifically on PancakeSwap V2 data – achieves 90.1% prediction accuracy, identifying high-risk tokens before the rug pull occurs rather than after investors have lost funds.

The PancakeSwap V2 Dataset

ChainAware trained and validated its rug pull detection model on PancakeSwap V2 transaction data from weeks 1 through 20 of 2026 – covering $569 million in documented rug pull losses across thousands of token launches. This dataset is the largest and most recent rug pull training corpus available in the public domain for BNB Chain tokens. The training methodology uses behavioral signals from the contract deployer wallet and all LP providers – not contract code analysis. Professional rug pull operators know exactly which code patterns trigger existing contract scanners, and they code around them. Their behavioral history across 20M+ wallet personas reveals the signature of serial rug operators regardless of how clean their current contract appears.

Rug Pull Detector vs. Competing Tools

GoPlus, Token Sniffer, and Honeypot.is all analyze contract code – detecting known patterns of mint functions, blacklisting mechanisms, sell restrictions, and honeypot logic. These tools catch common scams that reuse known code patterns. They do not catch professional operators who deploy clean code specifically to evade code scanners. ChainAware’s Rug Pull Detector catches what code scanners miss – the experienced operator with a history of rugging who deploys a technically perfect contract but whose behavioral fingerprint across 20M+ personas identifies them as high risk. For the complete comparison, see our Best Web3 Rug Pull Detection Tools guide .

The Agentic Economy and Why It Needs a New Fraud Layer

The CB Insights AI Fraud Prevention Market Map was explicitly timed to coincide with the emergence of the agentic economy – the structural shift from human-operated financial systems to AI-agent-operated ones. Understanding this shift explains why the on-chain intelligence category is the fastest-growing by funding momentum in 2026.

Agents Are Not Humans

AI agents transacting on behalf of humans operate 24/7, across all time zones simultaneously, at machine speed, without the cognitive friction that slows human decision-making. An AI agent does not hesitate before a suspicious transaction – it executes at the speed of the LLM inference cycle. This eliminates the natural fraud prevention that human decision-making provides. Consequently, AI agents need external fraud intelligence to substitute for the human judgment they lack. ChainAware’s Prediction MCP delivers that intelligence in the format agents can consume – structured behavioral profiles via natural language queries, sub-second response, no blockchain expertise required. For integration details, see our 12 Blockchain Capabilities Any AI Agent Can Use .

Haun Ventures’ $1B Thesis – Word for Word

Katie Haun’s Haun Ventures $1 billion fund announcement, published May 4, 2026, contains the most precise description of ChainAware’s product from any institutional source: “Every supporting layer will need to be rearchitected for this world: fraud prevention, credit, insurance, identity, privacy, provenance, reputation, and verification all require native versions designed for how agents transact.” That sentence describes ChainAware’s product roadmap. Haun Ventures is not alone – Dragonfly Capital closed $650 million, a16z crypto closed $2.2 billion, ParaFi Capital raised $125 million – every major fund closing in 2026 has identified the same gap that ChainAware is building into.

The Market Signal – $6B+ in VC Funding Points at the Same Gap

The $6 billion+ deployed into crypto and Web3 infrastructure during the first five months of 2026 is the strongest institutional signal the sector has seen since 2021 – but with a fundamentally different thesis. The 2021 cycle was driven by speculation on token appreciation. The 2026 cycle is driven by infrastructure investment in the trust, compliance, and intelligence layers that the agentic economy requires.

The Fund Closing Timeline

Dragonfly Capital’s $650 million fourth fund closed February 17, 2026. ParaFi Capital’s $125 million raise closed in March 2026, focused on stablecoins, tokenization, and on-chain financial products. Haun Ventures announced $1 billion on May 4, 2026. a16z crypto’s $2.2 billion fifth fund announced May 5, 2026 – bringing its total crypto-focused assets to $9.8 billion. Blockchain Capital is actively raising $700 million. Paradigm’s rumored $1.5 billion includes an AI-plus-crypto thesis. Total confirmed capital: over $4.5 billion closed in the first five months of 2026, with another $2.2 billion in process. Every fund thesis identifies the same three investment areas: new financial infrastructure, new assets and markets, and the agentic economy.

ChainAware as Growth Tech – The Revenue Dimension of On-Chain Intelligence

The CB Insights map positions fraud prevention entirely as a defensive category. ChainAware’s growth tech layer reframes on-chain intelligence as a revenue-generating capability – where the same behavioral data that prevents fraud also drives conversion, retention, and user acquisition efficiency.

The 84% Ghost Wallet Problem

ChainAware’s analysis of 9,999 unique wallet addresses from a major Web3 marketing campaign found that 84% were ghost wallets: zero real engagement, zero meaningful transaction history, zero likelihood of converting into active protocol users. Every dollar spent acquiring ghost wallets is waste – the acquired “user” will never transact, never provide liquidity, never participate in governance, and never generate fee revenue. ChainAware’s growth intelligence layer converts this waste into signal. Before running a campaign, protocols can screen target wallet lists through the Fraud Detector and Wallet Auditor – removing ghost wallets, Sybil clusters, and airdrop farmers from the acquisition pool before spending budget on them. For the complete framework, see our DeFi Onboarding guide .

The 12 Intention Scores as Growth Signals

ChainAware’s 12 behavioral intention scores – Borrow, Lend, Trade, Gamble, NFT, Stake ETH, Stake Yield Farm, Leveraged Staking, Leveraged Staking ETH, Leveraged Lending, Leveraged Long ETH, Leveraged Long Game – are not just risk signals. They are growth signals that tell a protocol exactly which products to surface to each connecting wallet. A wallet with High Lend intention should see lending products featured first. A wallet with Low Experience should see simplified onboarding. Neither wallet needs to self-identify their interests – the behavioral history already tells the protocol everything it needs to know. For the complete growth deployment architecture, see our User Segmentation guide .

Full Competitive Landscape – CB Insights Map Breakdown

The full CB Insights AI Fraud Prevention Market Map covers 200+ companies across six major sections. Understanding the complete map reveals where ChainAware’s behavioral intelligence layer fits within the broader fraud prevention ecosystem – and which categories represent potential integration partners rather than competitors.

Agentic Trust Infrastructure – A Partnership Category

The Agentic Trust Infrastructure section covers agent observability and evaluation (Arize, LangChain, Patronus AI), agent authentication and authorization (xAembit, Arcade, AuthMind, Skyfire), and agent runtime governance (Ciphero, HUMAN, Witness AI). ChainAware’s Prediction MCP is a natural integration layer for all three subcategories – adding on-chain behavioral fraud detection to agent monitoring, authentication, and governance workflows that these platforms currently lack.

Digital Identity – Complementary, Not Competing

The Digital Identity section covers decentralized identity (DID), passwordless authentication, post-quantum identity, KYC, and biometric identity. Companies like Humanity Protocol, Billions, Self, and zkMe provide proof-of-personhood and verifiable credentials – confirming that a wallet is controlled by a unique human. DID systems answer “is this wallet controlled by a unique person?” ChainAware answers “is this person’s behavior consistent with fraud – and what will they do next?” These questions are complementary, not overlapping. For how ChainAware integrates with DID systems, see our Blockchain Compliance guide .

AML Compliance – The Enterprise Complement

The AML compliance subcategory includes Amlyze, Comply Advantage, Fiverity, Hawk AI, Natech, and Sphinx – all providing transaction monitoring and AML reporting for regulated financial institutions. ChainAware’s AML screening and behavioral fraud detection complement these platforms rather than replacing them. Enterprise AML systems provide regulatory reporting, case management, and audit trails. ChainAware provides the pre-execution risk signal that determines which transactions require closer AML review. For the complete DeFi compliance stack, see our DeFi Compliance Tools guide .

How to Use ChainAware’s Intelligence Products Today

All three ChainAware intelligence products are available without signup, without wallet connection, and without a sales conversation. The free tier delivers the complete product – not a limited preview.

Rug Pull Detector

Navigate to chainaware.ai/rug-pull-detector . Paste any ERC-20 or BEP-20 token contract address. The detector returns a rug pull probability score, a breakdown of the risk factors identified, and a behavioral assessment of the contract deployer and LP providers. Results are available in under 3 seconds. No account required. Use it before buying any new token – especially on BNB Smart Chain where the $569 million PancakeSwap V2 dataset gives the model its highest accuracy.

Fraud Detector

Navigate to chainaware.ai/fraud-detector . Paste any wallet address. The detector returns fraud probability (98% accuracy), AML status, OFAC screening result, and a behavioral summary. Covers ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, and SOL. Results are available in under 1 second. No account required. Use it to screen wallets before approving DeFi protocol interactions and to verify team wallet addresses published by new token projects.

Wallet Auditor

Navigate to chainaware.ai/audit . Paste any wallet address. The Wallet Auditor returns the complete 22-dimension Web3 Persona: fraud probability, all 12 intention scores, experience level, risk appetite, AML status, OFAC screening, Wallet Rank, wallet age, transaction count, and balance. For the complete guide, see our Wallet Auditor guide .

API Access and Prediction MCP

For teams integrating ChainAware intelligence at scale, the REST API provides full access to all intelligence products at volume. The Prediction MCP server at prediction.mcp.chainaware.ai/sse delivers complete behavioral profiles to any MCP-compatible AI agent in under 1 second. API documentation is available at swagger.chainaware.ai.

Frequently Asked Questions

What is the CB Insights AI Fraud Prevention Market Map?

The CB Insights AI Fraud Prevention Market Map, published June 2, 2026, identifies 200+ companies building identity, trust, and fraud prevention infrastructure for the AI era. CB Insights selects companies based on Mosaic health scores above 600 and equity funding since 2024. ChainAware appears in the On-Chain Intelligence subcategory – alongside Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, and Blockaid – as the only Web3 AI token in the full list.

Why is ChainAware the only Web3 AI token in the CB Insights list?

Most on-chain intelligence companies – Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, Blockaid – are pure SaaS businesses with no publicly traded token. They serve regulated institutional clients who cannot hold utility tokens, and they avoid tokens for regulatory complexity reasons. ChainAware’s bifurcated model – enterprise API subscriptions for institutional clients plus the AWARE utility token for Web3 ecosystem participants – allows it to appear in both institutional and decentralized discovery channels simultaneously.

How does ChainAware’s 90.1% rug pull accuracy compare to other tools?

GoPlus, Token Sniffer, and Honeypot.is analyze contract code – they do not publish accuracy statistics because they report risk flags rather than probability scores. ChainAware’s 90.1% accuracy is a backtested performance metric on the PancakeSwap V2 dataset covering $569 million in documented rug pulls from weeks 1 through 20 of 2026. The key distinction is that ChainAware’s model analyzes behavioral history of the contract deployer and LP providers – catching professional operators who deploy clean code to evade code scanners. For detailed methodology, see our Rug Pull Detection guide .

What is the difference between ChainAware and Chainalysis?

Chainalysis is a forensic compliance platform designed for law enforcement and regulated exchanges – it traces where funds came from after transactions have occurred, with enterprise pricing from $100,000 to $500,000 annually. ChainAware is a predictive behavioral intelligence platform designed for DeFi protocols, AI agents, and compliance teams – it predicts fraud before transactions execute, with a free tier and accessible API pricing. The two are complementary: Chainalysis provides post-incident forensics; ChainAware provides pre-execution fraud prevention. For the complete cost comparison, see our MiCA Compliance at 1% of Chainalysis Cost guide .

How does the Prediction MCP work for AI agents?

ChainAware’s Prediction MCP server is accessible at prediction.mcp.chainaware.ai/sse. Any MCP-compatible AI agent – Claude, GPT, or any other LLM – can connect to the MCP and query behavioral profiles via natural language. The agent sends a query such as “What is the fraud risk and behavioral profile of 0x2f71…?” and receives a structured response containing fraud probability, all 12 intention probabilities, experience level, risk appetite, AML status, and Wallet Rank – all pre-computed, in under one second. According to Anthropic’s MCP documentation , MCP is becoming the standard for AI agent tool access. For the integration guide, see our Prediction MCP guide .

Can ChainAware detect governance attacks before they execute?

Yes – governance attack detection is one of ChainAware’s most differentiated capabilities. DAO governance attacks typically use Sybil wallet clusters – coordinated addresses that each hold small token amounts and vote together to achieve disproportionate governance influence. ChainAware’s behavioral model detects these clusters by identifying wallets that share funding sources, exhibit synchronized transaction timing, and demonstrate consistent co-voting behavior across multiple governance proposals. For the complete governance attack detection framework, see our Web3 Governance Screeners guide .

How does ChainAware’s behavioral intelligence help with MiCA compliance?

MiCA (Markets in Crypto-Assets Regulation) requires crypto asset service providers operating in the EU to implement transaction monitoring, AML screening, and customer risk assessment. ChainAware’s Fraud Detector and AML screening cover the pre-execution risk assessment requirement – delivering 98% accurate fraud probability and real-time AML/OFAC screening for every wallet interacting with a MiCA-covered service. According to FATF’s Virtual Assets Recommendations , transaction monitoring requirements increasingly mandate real-time screening capabilities. For the complete implementation guide, see our DeFi Compliance Tools guide .

What makes ChainAware’s position in CoinGecko’s AI category strategically valuable?

CoinGecko’s AI category receives millions of views monthly from users specifically searching for AI-related blockchain investments and infrastructure. Being the only on-chain intelligence and behavioral fraud detection project among 1,385 tokens creates a discovery advantage that pure enterprise SaaS competitors cannot replicate. A developer researching AI-native blockchain tools who browses the CoinGecko AI category finds ChainAware as the only fraud intelligence and behavioral scoring option – without competition from Chainalysis, Elliptic, or TRM Labs who have no token presence. The combination of institutional validation from CB Insights and retail discovery via CoinGecko creates a dual-channel visibility that no competitor in either ecosystem can match.

External Sources: CB Insights AI Fraud Prevention Market Map · CoinGecko AI Category · Anthropic Model Context Protocol · FATF Virtual Assets Recommendations · Chainalysis Platform

The post ChainAware.ai Named in CB Insights AI Fraud Prevention Market Map – The Only Web3 AI Token in the List first appeared on ChainAware.ai.

Every DeFi growth team eventually learns the same expensive lesson. They invest in campaigns. Wallets show up. And then most of those wallets leave without transacting. The team debates: was it the product? The onboarding? The audience targeting? The fees?

The real answer is usually simpler and more uncomfortable: getting traffic is a solved problem. You can buy all the wallets you want. The question nobody’s growth platform answers is what those wallets do after they arrive – and why most of them leave without converting.

In 2026, five platforms dominate the Web3 growth conversation: Blockchain-Ads, Addressable, Safary, Slise, and ChainAware.ai. They are frequently mentioned together. They are rarely compared accurately. This article fixes that – with a framework built around the three stages of the Web3 growth funnel, and an honest verdict on which platform wins each one.

In This Article

• The Three Stages of the Web3 Growth Funnel
• 5 Platforms at a Glance
• Blockchain-Ads: Paid Acquisition at Scale
Addressable: Web2-to-Web3 Attribution
• Safary: Analytics, Attribution & Community
• Slise: Programmatic Display for Web3 Publishers
• ChainAware.ai: Predictive Intelligence + In-Dapp Conversion
• Head-to-Head Comparison Table
• Which Platform Wins Each Use Case
• The Traffic Trap: The Hard Truth Web3 Teams Learn Too Late
• Conclusion: Two Different Problems Require Two Different Tools
• FAQ

The Three Stages of the Web3 Growth Funnel

To compare these platforms meaningfully, you need to understand where in the funnel each one operates. Web3 growth happens in three stages – and most platforms only cover the first one.

Stage 1 – Find the Right Wallets (Pre-Click)

This is the advertising layer. You build audiences from on-chain wallet data and push ads or campaigns to those wallets across the web: crypto media, social platforms, display networks. Blockchain-Ads, Addressable, and Slise all operate primarily here. The job is getting qualified wallets to your landing page or Dapp door.

Stage 2 – Understand Who Just Arrived (Post-Click, Pre-Connect)

When a wallet hits your website or Dapp, you know almost nothing about them yet. They haven’t connected. They’re browsing. This is where most growth stacks go completely dark. Safary and Addressable have partial tools here. ChainAware’s Behavioral Analytics fills this gap properly: you know in real time whether the visitor is an experienced DeFi user, a newcomer, a whale, or a potential fraud risk – before they connect a wallet. For the full methodology behind this layer, see the Web3 User Analytics learn guide.

Stage 3 – Convert the Wallet Inside the Dapp (Post-Connect)

The wallet has connected. They’re inside your product. This is the moment that matters most – and every platform except ChainAware has left the building. ChainAware’s Growth Agents are the only tools in this entire comparison that operate at the point of connection: personalizing the experience, routing the user, and acting on real-time behavioral intelligence to maximize conversion. No other platform on this list has any presence at Stage 3. See the Growth Agents learn guide for the full agent catalogue.

This framework is not a minor technical distinction. It is a strategic fault line that determines which tool you actually need – and whether the traffic you’re buying will ever convert.

5 Web3 Growth Platforms at a Glance (2026)

Platform	Core Category	Primary Stage	Key Differentiator
Blockchain-Ads	Performance Ad Network	Stage 1	Wallet-level targeting across 37+ chains, 9,000+ sites
Addressable	Web3 Marketing Intelligence	Stage 1-2	Web2Web3 attribution bridge, 23M wallet-to-social matches
Safary	Analytics + Community	Stage 1-2	“Google Analytics for Web3” + elite growth operator network
Slise	Programmatic Display	Stage 1	Ad inventory inside Web3-native publisher dApps and wallets
ChainAware.ai	Predictive Intelligence + Growth	Stage 1-2-3	The only platform operating at the point of conversion inside the Dapp

Blockchain-Ads: Paid Acquisition at Scale

What it is: Blockchain-Ads is a performance ad network built specifically for Web3, operating as a unified DSP/DMP/SSP stack. Advertisers build audiences from wallet behavior – token holdings, DeFi activity, NFT ownership, transaction history – and run display, video, and native ads across 9,000+ websites and apps spanning 37+ blockchains.

How it works: The platform uses a “Web3 cookie” technology that anonymously links device IDs to wallet addresses when users interact with partner publishers and data providers. This allows targeting specific wallet profiles – not just “crypto users” broadly – wherever they browse across the open web, including mainstream sites outside the crypto vertical.

Real results: Coinbase onboarded 31,000 new traders in 60 days through Blockchain-Ads, at an average CPA of $20.08. Binance reported 19.8x ROAS on an APAC campaign, acquiring over 4,600 new traders in 30 days. These are the best-published numbers in the Web3 ad network space.

Clients: Coinbase, Binance, Crypto.com, OKX. The client list reads like a who’s who of Web3 brands with substantial paid acquisition budgets.

Pricing model: CPA, CPM ($1.25-$2.25 for infrastructure campaigns), CPC ($0.30-$0.50), and first transaction ($10-$13). Minimum budgets typically start at $10,000/month for full-funnel campaigns.

Where it stops: Blockchain-Ads delivers wallets to your door. What happens after the click is entirely outside its scope. There is no analytics, no onboarding intelligence, no in-Dapp personalization, and no fraud screening at the point of connection.

Best for: Established Web3 protocols with significant acquisition budgets who need scale and reach across 37+ chains. Token launches, exchange user acquisition, DeFi TVL growth campaigns.

Addressable: Web2-to-Web3 Attribution

What it is: Addressable is a Web3 marketing intelligence platform that links on-chain wallet data with off-chain social and web behavior. The platform’s core capability is bridging the attribution gap between Web2 ad spend (X/Twitter, Reddit, display) and Web3 on-chain conversions – letting growth teams finally answer the question: “which campaign drove which on-chain actions?”

How it works: Addressable maintains a database of 23 million wallet-to-social profile matches across 7 blockchains. Advertisers target wallet cohorts (e.g., “wallets that have bridged to Base” or “users who hold more than 10 ETH”) through connected ad channels – X Ads, Reddit Ads, and display networks – then track the full funnel from ad click through to on-chain conversion. Their attribution platform tracks 450+ daily metrics across Web2 and Web3.

Retargeting: Addressable launched wallet-based retargeting in 2025 – the ability to re-engage wallets that visited but didn’t connect, or connected but didn’t convert, across X, Reddit, and crypto-native platforms. Their analysis of 245 campaigns found that wallet owners are 7× more likely to transact than generic click traffic, and retargeting typically reduces cost-per-wallet by an additional 40%.

Clients: Coinbase, Polygon, eToro, Polkadot, Algorand. Strong in established DeFi protocols and chains running multi-channel campaigns.

Where it stops: Addressable’s intelligence ends when the wallet connects to the Dapp. The platform can tell you which campaign drove a wallet to connect, but it has no capabilities inside the Dapp itself – no onboarding personalization, no real-time behavioral intelligence at the point of interaction, no fraud screening.

Best for: Growth teams running paid campaigns across X/Twitter, Reddit, and display who need Web2-style attribution applied to Web3 conversions. Ideal for protocols that already have a multi-channel paid acquisition strategy and want to close the measurement loop back to on-chain actions. According to Addressable’s own research, CPW (Cost Per Wallet) is the north-star metric that separates high-efficiency campaigns from wasted spend.

Safary: Analytics, Attribution & Community

What it is: Safary occupies a unique dual position in the Web3 growth ecosystem: it is simultaneously a marketing attribution platform (“Google Analytics for Web3”) and the leading community for crypto’s top growth operators. The two sides reinforce each other – the community generates insights that improve the platform, and the platform gives community members tools they use daily.

The platform: Safary’s attribution and analytics tools let Web3 teams measure marketing CAC, channel ROI, and customer LTV across Web2 and Web3 channels. The platform recently expanded to sync X followers with on-chain data – showing wallet balances, assets held, and protocols used by a protocol’s Twitter audience – and enables direct messaging and conversion tracking against those profiles. One line of code on your website unlocks the core analytics capabilities.

The community: Safary Club is an invitation-only network of 250+ crypto growth leaders from protocols including Berachain, Magic Eden, Ledger, dYdX, and CoinMarketCap. Members meet weekly to analyze growth metrics, reverse-engineer tactics, and share playbooks. The club runs an annual certification cohort – the only structured Web3 growth education program of its kind – and hosts the Safary Summit at ETHDenver. The community component is genuinely differentiated: no other platform on this list offers it.

Where it stops: Safary is an analytics and intelligence platform – it tells you what happened and helps you understand your audience. It does not run ads, execute retargeting campaigns, personalize the in-Dapp experience, or screen for fraud at the point of connection. It is a measurement and intelligence tool, not an execution platform.

Best for: Growth teams who want to understand their marketing performance across all channels and want access to a peer network of crypto’s best growth operators. Particularly strong for teams building community-led growth strategies alongside paid acquisition. See safary.club for the community details.

Slise: Programmatic Display for Web3 Publishers

What it is: Slise is a programmatic ad network where Web3-native publishers – wallets, tools, DeFi dashboards, blockchain games, and infra products – monetize their audiences by embedding Slise’s ad code. Advertisers (DeFi protocols, exchanges, token projects) target those audiences using on-chain wallet data, reaching users while they actively engage with Web3 products.

How it works: The key insight behind Slise is that the best place to advertise to an active DeFi user is not a crypto news site – it’s inside the Web3 tool they’re actually using. A user checking their portfolio in a DeFi dashboard or managing assets in a multi-chain wallet is in an active, high-intent state. Slise monetizes that moment for the publisher and makes it available to advertisers. The platform uses only public blockchain data, with no third-party cookie dependency – a genuine privacy advantage as cookie deprecation continues to reshape digital advertising.

Publisher clients: Ledger, OKX, Revolut, Moonpay, MetaMask ecosystem, 1inch, Chiliz – large Web3 brands whose users represent high-quality advertising inventory. Y Combinator and Binance Labs-backed.

Important clarification: Slise places ads within Web3-native publisher interfaces – not inside competitor DeFi protocols. The publisher inventory is wallets, portfolio trackers, blockchain explorers, and Web3 tools, not DeFi applications advertising against themselves. The distinction matters: the advertiser is buying inventory from publishers who have opted in to monetize their user base.

Where it stops: Slise is a display ad network – its role ends when the user clicks the ad. No attribution beyond the click, no analytics about user quality, no in-Dapp capabilities, no fraud screening.

Best for: Protocols wanting to reach active Web3 users through premium native publisher inventory at lower CPMs than Blockchain-Ads. Particularly effective for wallet infrastructure companies, Web3 games, and Layer-1/Layer-2 chains targeting active on-chain participants across the broader ecosystem. According to Slise’s case studies, clients from gaming to infra to DeFi protocols have used the platform for user acquisition campaigns.

ChainAware.ai: Predictive Intelligence + In-Dapp Conversion

What it is: ChainAware.ai is the Web3 Agentic Growth Infrastructure – the behavioral intelligence layer that operates across all three stages of the growth funnel. It is the only platform in this comparison with tools at Stage 2 (understanding visitors before they connect) and Stage 3 (converting wallets inside the Dapp). As we covered in depth in The Web3 Agentic Economy, the protocols that deploy agentic infrastructure in 2026 operate at structurally different economics and conversion rates than those relying on traffic alone.

The data layer: ChainAware maintains behavioral profiles on 14M+ wallets across 8 blockchains – not just transaction history, but predictive intelligence: fraud probability (98% accuracy), experience level, risk willingness, behavioral categories, predicted next actions (Prob_Trade, Prob_Stake, Prob_Bridge, etc.), AML status, and Wallet Rank. This predictive layer is what separates ChainAware from every other platform in this comparison.

Stage 1 – Acquisition (What ChainAware Adds)

ChainAware’s Web3 Behavioral Analytics and Token Rank give growth teams the ability to score inbound traffic by quality – not just volume. Instead of measuring how many wallets connected, teams measure what kind of wallets connected: their Wallet Rank distribution, experience levels, and fraud probability profile. This tells you whether a campaign is acquiring the right users before you’ve committed weeks of budget to it.

Stage 2 – Visitor Intelligence (Where Others Go Dark)

When a wallet lands on your website but hasn’t connected yet, every other platform on this list is blind. ChainAware’s pixel – installed via Google Tag Manager in minutes – begins profiling visitors as soon as a wallet address can be associated with the session. The Behavioral Analytics dashboard shows aggregate intelligence across 8 dimensions: intentions, experience, risk willingness, protocol history, top protocols used, fraud probabilities, Wallet Rank distribution, and wallet age. This is the behavioral baseline that tells you not just how many people are visiting, but who they are and what they’re likely to do. Free starter plan, no engineering required. Full guide here.

Stage 3 – In-Dapp Conversion (What Only ChainAware Does)

This is the decisive differentiator. ChainAware’s Growth Agents operate at the moment a wallet connects to your Dapp – the most important moment in the entire funnel. In under 100ms, the agent knows:

• Is this wallet experienced or a newcomer? → Route to the right onboarding flow
• Is this wallet a fraud risk? → Gate before they access sensitive features
• What is this wallet’s predicted intention? → Surface the most relevant product feature first
• Is this wallet a whale? → Trigger VIP treatment automatically
• Is this a reward hunter? → Apply appropriate friction before showing incentives

The result: DeFi protocols using ChainAware’s Growth Agents report onboarding completion improvements from 35% to 62-67%, Day-30 retention improvements from 28% to 47-51%, and re-engagement click-through improvements of 340% from wallet-personalized campaigns versus mass messaging. These are the conversion metrics that no amount of traffic spend can generate without the intelligence layer operating at the point of connection. For the full architecture behind this routing logic, see the Agentic Onboarding Personalisation use case.

MCP Integration for AI Agents: ChainAware is also the only platform with a published Model Context Protocol (MCP) server – meaning any AI agent (Claude, GPT, or custom LLM) can query behavioral intelligence, fraud scores, AML screening, wallet ranking, and growth automation in natural language, without custom API integration. 12 open-source agent definitions on GitHub. Full documentation at the Prediction MCP learn guide and the For AI Agents overview. API key at chainaware.ai/mcp.

Free tools: Wallet Auditor (full behavioral profile, free, no signup), Fraud Detector (98% accuracy, free), Token Rank (holder quality scoring, free).

Best for: DeFi protocols, GameFi platforms, NFT marketplaces, and Web3 applications that want to convert the traffic they’re already acquiring – not just buy more of it. Also the definitive choice for any team deploying AI agents in their growth or compliance stack.

Free – No Signup Required

See Who’s Actually Visiting Your Dapp

ChainAware Behavioral Analytics aggregates the behavioral profile of every wallet connecting to your platform – experience levels, intentions, risk scores, fraud probabilities, Wallet Rank distribution. Google Tag Manager setup, no code changes, free starter plan.

Get Started Free Audit Any Wallet Free

Head-to-Head Comparison Table: All 5 Platforms (2026)

Capability	Blockchain-Ads	Addressable	Safary	Slise	ChainAware.ai
Wallet-level ad targeting	Best-in-class	Strong		On-chain data	Via MCP / Agents
Web2 attribution (X, Reddit, Display)		Core capability	Partial
On-chain attribution	OCMA tracking	End-to-end	CAC/LTV		Via pixel
Visitor analytics (pre-connect)		Partial (User Radar)	Basic		Full behavioral
In-Dapp personalization					Growth Agents
Fraud detection at connection					98% accuracy
AML / compliance screening					OFAC + AML
Predictive behavioral intelligence		Historical only	Historical only		Predictive AI
AI agent / MCP integration		API only	API only		Native MCP
Community / knowledge network			250+ leaders
Free tools			Basic free tier		Wallet Auditor, Fraud Detector, Token Rank
Minimum budget	~$10K/mo	Demo required	Free + paid	Custom	Free → MCP plans

Which Platform Wins Each Use Case

“I want to run large-scale paid acquisition campaigns”

→ Blockchain-Ads is the clear choice if budget is not a constraint. The scale (37+ chains, 9,000+ sites), the targeting depth (wallet-level behavioral audiences), and the published case study ROI (19.8x ROAS for Binance) make it the dominant paid acquisition platform in Web3. Addressable is a strong alternative if your campaigns run primarily on X/Twitter and Reddit and you need cross-channel attribution.

“I want to close the attribution loop between my ad spend and on-chain results”

→ Addressable. If you’re running Twitter campaigns, Reddit ads, or display, and you want to know which specific creative drove which on-chain wallet connections and conversions, Addressable’s Web2Web3 attribution bridge is built for exactly this. No other platform on this list closes this loop as completely.

“I want to understand my existing users and benchmark my marketing performance”

→ Safary or ChainAware Behavioral Analytics depending on whether your priority is community and benchmarking (Safary) or deep behavioral intelligence on your own Dapp visitors (ChainAware). Safary’s community gives you access to what’s working across 250+ protocols. ChainAware’s Behavioral Analytics gives you the definitive answer on who exactly is visiting your platform and why they’re not converting.

“I want to reach active Web3 users on premium inventory without crypto media CPMs”

→ Slise. For protocols that want their ads seen by users who are actively engaged with Web3 tools – not just browsing crypto news – Slise’s publisher network of wallets, portfolio trackers, and Web3 infrastructure apps delivers high-intent inventory at competitive CPMs.

“I want to convert more of the traffic I’m already acquiring”

→ ChainAware. If you’re already running Blockchain-Ads or Addressable campaigns and wallets are showing up but not transacting, the problem is not at the traffic layer – it’s at the conversion layer. ChainAware’s Growth Agents are the only tool in this comparison that operates at the moment of conversion, inside the Dapp, in real time.

“I want to screen out fraud and reward hunters before they cost me money”

→ ChainAware. Fraud detection, AML screening, and reward-hunter identification are exclusive to ChainAware in this comparison. According to TRM Labs’ 2026 Crypto Crime Report, illicit crypto volume reached $158 billion in 2025. None of the other four platforms have any capability to screen for this at the point of user onboarding.

“I want my AI agents to have access to real-time wallet behavioral intelligence”

→ ChainAware MCP. This use case is exclusive to ChainAware. No other platform on this list publishes an MCP server or provides native AI agent integration. Any LLM agent can call ChainAware’s fraud detection, AML scoring, behavioral prediction, and wallet ranking tools in natural language. API key at chainaware.ai/mcp. Open-source agents on GitHub.

The Traffic Trap: The Hard Truth Web3 Teams Learn Too Late

Every DeFi growth team discovers the same thing eventually, and usually only after they’ve paid for the lesson. Traffic is a solved problem. You can buy wallets. Blockchain-Ads will deliver them. Addressable will attribute them. Slise will reach them in premium inventory. Safary will help you measure the quality.

But none of those platforms can answer the question that actually determines whether a protocol grows: what happens to those wallets inside your Dapp?

The structural reality of DeFi onboarding in 2026 is brutal. Based on ChainAware’s analysis across DeFi protocols: for every 200 visitors who reach a protocol, around 10 will connect their wallet – and only 1 will actually transact. Teams are spending their entire acquisition budget to fill a funnel that converts at 0.5%.

The problem is not the traffic. The problem is what happens after the wallet connects:

• A first-time DeFi user and a whale see the exact same onboarding flow. The newcomer is confused. The whale is bored. Both leave.
• A reward hunter and a genuine long-term user get the same incentive offer. The reward hunter drains the program. The genuine user gets diluted.
• A high-fraud-risk wallet and a clean wallet receive the same trust level at connection. The fraud risk exploits it.
• A wallet with high staking intent lands on a trading-first interface. The mismatch kills conversion before a single pixel of the product is seen.

This is not a traffic problem. It is a conversion intelligence problem. And it can only be solved by a platform that operates inside the Dapp, at the moment the wallet connects, with real-time behavioral knowledge of who that wallet is and what they’re likely to do next.

That is what ChainAware’s Growth Agents do. And it is why the ROI on conversion intelligence often exceeds the ROI on additional traffic spend by a significant margin: you’re not buying more wallets, you’re converting the ones you already paid to acquire.

According to McKinsey’s 2026 State of AI report, personalization at the individual user level consistently generates 5-8× better conversion rates than segment-level personalization – and segment-level is 3-4× better than no personalization at all. Web3 has been operating without personalization entirely. That’s the opportunity ChainAware’s Growth Agents unlock.

Agentic Growth Infrastructure

Stop Buying Traffic You Can’t Convert

ChainAware Growth Agents operate at the moment a wallet connects to your Dapp. Real-time behavioral intelligence, personalized onboarding routing, fraud screening, whale detection – all in under 100ms. The only platform that works at Stage 3.

See Growth Agents Book Free Consulting Call

Conclusion: Two Different Problems Require Two Different Tools

The honest answer to “which Web3 growth platform should I use?” is: it depends which problem you’re trying to solve. And the most important thing is recognizing that getting traffic and converting traffic are two completely different problems – with different solutions.

For paid acquisition at scale: Blockchain-Ads is the market leader, full stop. The client list, the published case study ROI, and the targeting depth across 37+ chains make it the default choice for protocols with meaningful acquisition budgets.

For multi-channel attribution: Addressable is the most complete solution for teams running across X/Twitter, Reddit, and display – and needing to close the measurement loop back to on-chain actions.

For analytics, measurement and growth community: Safary is the most useful combination of tooling and peer intelligence in the market – especially for teams that want to benchmark their growth approach against 250+ top Web3 protocols.

For Web3-native display inventory: Slise delivers high-intent ad placements within Web3 publisher products – wallets, tools, and infrastructure apps – at competitive CPMs without cookie dependency.

For conversion intelligence and in-Dapp growth: ChainAware.ai is in a category of its own. It is the only platform that operates inside the Dapp, at the moment that matters, with real-time predictive behavioral intelligence on every connecting wallet. It is also the only platform with free tools (Wallet Auditor, Fraud Detector, Token Rank), AML and fraud screening, and native MCP integration for AI agents.

The most sophisticated DeFi growth teams in 2026 use both: one of the first four for acquisition and attribution, and ChainAware for conversion intelligence and compliance. The protocols that discover this combination early – and stop treating traffic spend as a substitute for conversion intelligence – are the ones compounding their growth while their competitors keep asking why wallets aren’t transacting.

The traffic was never the problem. It was never the solution either.

Frequently Asked Questions

What is the best Web3 growth platform in 2026?

There is no single best platform – the right answer depends on where in the funnel your problem is. For paid acquisition at scale, Blockchain-Ads leads. For Web2-to-Web3 attribution, Addressable. For analytics and growth community, Safary. For Web3-native display inventory, Slise. For in-Dapp conversion intelligence and fraud screening, ChainAware.ai – the only platform that operates after the wallet connects. Most high-performing protocols use Blockchain-Ads or Addressable for traffic acquisition alongside ChainAware for conversion.

How is ChainAware.ai different from Blockchain-Ads or Addressable?

Blockchain-Ads and Addressable are advertising and attribution platforms – they operate before and during the click. ChainAware operates after the click, inside the Dapp, at the moment the wallet connects. ChainAware’s Growth Agents personalize the in-Dapp experience in real time based on each wallet’s behavioral profile. No other platform on this list has any capability at this stage of the funnel. ChainAware also provides fraud detection, AML screening, and AI agent (MCP) integration – capabilities none of the other platforms offer.

What does “in-Dapp conversion” mean and why does it matter?

In-Dapp conversion means personalizing what a user sees and experiences after they’ve connected their wallet – not before. It matters because DeFi conversion rates are structurally poor (typically 0.5-5% of wallet connections actually transact), and the reason is almost never the traffic quality. The reason is that all users see the same generic experience regardless of their skill level, intentions, or risk profile. ChainAware Growth Agents solve this by identifying each connecting wallet’s profile in under 100ms and routing them to the appropriate experience, incentive, or content – driving the conversion improvements documented across protocols using the platform.

Can I use ChainAware.ai together with Blockchain-Ads or Addressable?

Yes – and this is the recommended approach for mature DeFi growth teams. Blockchain-Ads or Addressable handles acquisition: getting high-quality wallets to your Dapp. ChainAware handles conversion: ensuring those wallets have a personalized experience that matches their profile when they arrive. The two layers are complementary and non-competing. Running both means you’re optimizing the entire funnel, not just the top of it.

Does ChainAware.ai have free tools?

Yes. ChainAware offers three completely free tools with no account required: the Wallet Auditor (full behavioral profile of any wallet in 30 seconds), the Fraud Detector (98% accuracy fraud probability for any wallet), and Token Rank (holder quality scoring for any token). The Behavioral Analytics starter plan for Dapps is also free via Google Tag Manager. None of the other platforms in this comparison offer comparable free access.

What is MCP and why does it matter for Web3 growth?

Model Context Protocol (MCP) is the open standard introduced by Anthropic that allows AI agents to call external tools in natural language. ChainAware is the only Web3 growth platform with a published MCP server – meaning any AI agent (Claude, GPT, or custom LLM) can query behavioral intelligence, fraud scores, AML screening, and wallet ranking without custom API integration code. As covered in detail in The Web3 Agentic Economy, the protocols deploying agentic growth infrastructure in 2026 will have structural cost and performance advantages over those that don’t. ChainAware’s MCP server is the infrastructure layer that makes this possible. According to a16z’s State of Crypto 2025 report, the infrastructure window for agentic protocols is open now – and will compound over multiple years.

ChainAware.ai – Web3 Agentic Growth Infrastructure

The Complete Growth Stack for DeFi Protocols

Behavioral Analytics · Growth Agents · Fraud Detection · AML Screening · Wallet Rank · Token Rank · MCP for AI Agents. 14M+ wallets profiled across 8 blockchains. The only platform that converts the traffic you’ve already acquired.

Audit Any Wallet Free Fraud Detector Free Get MCP API Key

The post Web3 Growth Platforms Compared: Blockchain-Ads vs Addressable vs Safary vs Slise vs ChainAware.ai (2026) first appeared on ChainAware.ai.

Last Updated: 2026

Most DeFi protocols measure success by wallet connections. That is the wrong metric.

Based on ChainAware.ai’s analysis across DeFi protocols, the real funnel looks like this: for every 200 visitors who reach your protocol, around 10 will connect their wallet – and only 1 will actually transact. You are spending your entire acquisition budget to fill a funnel that converts at 0.5%. The problem is not your traffic. It is what happens after the wallet connects.

Industry data confirms the pattern is structural. CoinLaw’s 2025 Web3 Wallet Statistics reports that only 5-10% of users become repeat dApp users within 30 days of initial use, and retention beyond 7 days remains below 20%. A March 2026 UX analysis published on Medium found that 65% of users drop off after their very first interaction – not after a bad week, not after a failed trade, but after the first session. The same analysis notes that 70% of DeFi users never return after completing even one transaction.

The core problem is that DeFi onboarding treats every wallet the same. A seasoned DeFi veteran with four years on-chain and a 19,000-transaction history sees the same tutorial, the same interface, and the same messaging as a wallet created two weeks ago that has never used a lending protocol. That mismatch – between who the user actually is and how the product speaks to them – is where the 99.5% drop-off happens.

This article explains what that mismatch looks like in practice, which AI agents solve which part of the problem, and how to deploy them – from the onboarding moment through to long-term retention.

In This Guide

• The Real Funnel: Where Your Budget Actually Goes
• Why Generic Onboarding Fails Every Wallet Type
• The 5 Onboarding Personas (with Real Wallet Behavior)
• The Onboarding Router Agent: Right Flow for Every Wallet
• Growth Agents: From Connection to First Transaction
• Transaction Monitoring Agent: Protect the Users Who Do Convert
• Fraud Detector: Stop Farming the Funnel Before It Starts
• Wallet Auditor: Know Who You’re Onboarding in 30 Seconds
• Agent-by-Agent Examples: Real Protocol Scenarios
• The Economics of Personalized Onboarding
• How to Deploy: 4-Step Implementation Guide
• FAQ

The Real Funnel: Where Your Budget Actually Goes

Before discussing solutions, it is worth understanding the funnel precisely – because most protocols are measuring the wrong stage.

Source: ChainAware.ai analysis across DeFi protocols, 2026.

There are two distinct bottlenecks, not one:

Bottleneck 1: Visitor → Connect (95% drop-off). Most visitors never connect their wallet at all. This is a trust, messaging, and first-impression problem. People don’t understand the value proposition quickly enough or don’t trust the product enough to take the first step.

Bottleneck 2: Connect → Transact (90% drop-off). Nine out of ten wallets that connect never execute a single transaction. This is where onboarding actually fails. The product shows a generic experience to every wallet – the same tutorial, the same feature layout, the same CTAs – regardless of whether the wallet belongs to a DeFi veteran or a complete beginner. Most wallets leave because the product never made it obvious why they specifically should do something right now.

Most protocols focus on Bottleneck 1 (traffic and acquisition) while ignoring Bottleneck 2. The real leverage is at Bottleneck 2 – because fixing it costs almost nothing compared to acquiring more traffic.

Why Generic Onboarding Fails Every Wallet Type

The root cause of Bottleneck 2 is simple: every wallet is treated as if it were the median wallet. But there is no median Web3 user.

Consider two wallets that connect to the same DeFi lending protocol on the same day:

• Wallet A: 4 years old, 8,000 transactions, active on Aave, Compound, and Uniswap, predicted high borrowing intent, Wallet Rank in the top 5%.
• Wallet B: 3 weeks old, 12 transactions, only used a DEX once, no lending history, predicted low DeFi intent.

Both wallets see the same homepage. Both get the same “How it works” modal. Both receive the same onboarding email sequence if they drop off. This is the equivalent of a bank showing a first-time saver the same product brochure as a hedge fund portfolio manager.

Wallet A needs none of the basics – it needs to see collateral ratios, liquidation mechanics, and why this protocol’s rates beat Aave. Wallet B needs to understand what overcollateralized lending means before it can evaluate anything else. The same product presentation fails both of them in opposite directions: it insults the expert and overwhelms the beginner.

According to McKinsey’s 2025 personalization research, companies that get personalization right generate 40% more revenue from those activities than average players. In DeFi, where acquisition costs are extreme and retention is structurally poor, personalization at the onboarding moment is not a nice-to-have – it is the primary lever for unit economics.

ChainAware.ai’s Web3 Behavioral Analytics and the Onboarding Router Agent solve this by reading the behavioral profile of every connecting wallet in real time – and routing them into the right experience before they ever see your product. For the complete architecture behind this routing layer, see the Agentic Onboarding Personalisation use case.

The 5 Onboarding Personas (with Real Wallet Behavior)

Based on ChainAware.ai’s behavioral data across 14M+ wallet profiles, connecting wallets fall into five distinct onboarding personas. Each requires a fundamentally different first experience.

Persona 1: The Power Trader (Wallet Rank 1-20, Experience Level 4-5)

This wallet has years of on-chain history, thousands of transactions across multiple chains, and deep protocol expertise. It has used Uniswap, Aave, GMX, and likely several cross-chain bridges. It is not here to learn – it is here to evaluate whether your protocol offers something specific it does not already have.

What this wallet needs from onboarding: Competitive rate comparison, collateral efficiency metrics, liquidation protection features, API/integration capabilities. Skip all introductory content. Go straight to the technical differentiation.

What kills conversion for this persona: Tutorial modals it has to dismiss. “What is DeFi?” explainers. Anything that assumes beginner-level knowledge. Every second spent on content it already knows is a second in which it decides this product is not built for users like it.

See how ChainAware’s Wallet Auditor profiles this persona in 30 seconds.

Persona 2: The Yield Farmer (Experience Level 3-4, High Staking/Lending Intent)

An experienced DeFi user whose on-chain history shows consistent yield-seeking behavior – staking, lending, liquidity provision. This wallet understands the mechanics but is always comparing APYs across protocols. It is mid-funnel by nature: it knows what it wants, but it evaluates multiple options before committing capital.

What this wallet needs from onboarding: Immediate APY visibility, vault comparisons, auto-compound mechanics, historical yield charts. The first screen should answer: “Why is your yield better than where my capital currently sits?”

What kills conversion: Hiding the yield data behind a “Learn More” button. Making it connect before showing rates. Friction at the point of comparison.

Persona 3: The DeFi Curious (Experience Level 2-3, Mixed Intent)

This wallet has been in Web3 for 6-18 months. It has used a DEX, maybe bridged assets once, and holds a few tokens. It understands wallets and transactions but has not yet used a lending or staking protocol. It is exploring but can be lost easily by complexity.

What this wallet needs from onboarding: A clear, jargon-free explanation of what your protocol does and what the risk is. A small “try it” action with low stakes – a small deposit, a simulation, a no-commitment preview. Social proof from wallets with similar profiles who have transacted successfully.

What kills conversion: Showing liquidation ratios and collateralization parameters before explaining what the product does. Making the first action feel high-stakes.

Persona 4: The Web3 Newcomer (Experience Level 1, Wallet Age Under 90 Days)

This wallet is new. It has fewer than 20 transactions, a short history, and no complex protocol interactions. It may have been directed here from a social campaign or influencer post. It is curious but fragile – the slightest friction or confusion will send it away permanently.

What this wallet needs from onboarding: Maximum simplicity. One clear action. An educational layer that appears on demand, not by default. A sense that the product is safe and that others like it have succeeded here.

What kills conversion: Everything that was built for Persona 1. Wallet connection flows that require understanding of gas. Unexplained approval transactions.

Persona 5: The Airdrop Farmer (Low Wallet Rank, Low Predicted Trust, High Volume of Recent New Wallets)

This is not a real user. It is a wallet – or more commonly, a coordinated cluster of wallets – that connects to capture points, tokens, or incentives with no intention of ever transacting or generating value for the protocol. Based on ChainAware’s fraud detection data, airdrop farmers can represent 20-40% of wallet connections during incentive campaigns.

What this wallet needs from onboarding: Nothing. It should be identified before onboarding begins and excluded from incentive programs, or shown a friction layer that genuine users pass through easily but farmers do not.

Why it matters: Every airdrop farmer that receives an incentive dilutes the reward pool for genuine users, distorts your engagement metrics, and consumes onboarding resources that should be allocated to real users. See how the Fraud Detector and Rug Pull Detector identify this persona at connection time.

The Onboarding Router Agent: Right Flow for Every Wallet

The Onboarding Router Agent is the first AI agent in the ChainAware stack – it fires the moment a wallet connects and determines which of the five personas is connecting, then routes that wallet into the corresponding onboarding experience.

How It Works

When a wallet connects to your Dapp, ChainAware’s behavioral engine – backed by 14M+ wallet profiles across 8 blockchains – runs a full behavioral analysis in under 100 milliseconds. The output is a complete persona classification: experience level (1-5), risk willingness, protocol history, predicted intentions, Wallet Rank, and predicted fraud probability.

The Onboarding Router Agent reads this classification and triggers the corresponding onboarding flow in your frontend. This can be implemented via Google Tag Manager (no-code), via the Prediction MCP API, or directly via ChainAware’s Growth Agent infrastructure.

Example: DeFi Lending Protocol

A lending protocol implements the Onboarding Router Agent with four distinct flows:

• Expert flow (Persona 1-2): Connects → immediately sees the rates dashboard, collateral calculator, and historical performance. No tutorial. One-click deposit flow.
• Mid-level flow (Persona 3): Connects → sees a simplified “here’s what you earn” explainer with a small-deposit simulation. A single “Start with $50” CTA. Tutorial available on demand via a “?” icon.
• Newcomer flow (Persona 4): Connects → sees “Welcome to your first DeFi experience” onboarding modal. Three-step guided flow. Smaller minimum deposit threshold. Video walkthrough available.
• Farmer/risk flow (Persona 5): Connects → incentive eligibility check runs. Wallet below Wallet Rank threshold is shown standard product but excluded from incentive allocation automatically.

Result in practice: Before implementation, 10 wallets connected per 200 visitors, 1 transacted. After Onboarding Router Agent deployment, the same traffic produced 10 connections but 3-4 transactions – because each user now saw a product experience calibrated to their actual knowledge and intent. For the full methodology behind this result, see the SmartCredit.io case study: 8x engagement, 2x conversions.

Example: GameFi Platform

A GameFi platform uses the Onboarding Router Agent during a token launch event. Without routing, the incentive campaign attracts thousands of wallet connections – but 60% are airdrop farmers with no gaming intent. With routing, the agent identifies farmers at connection time (low Wallet Rank, new wallets, high fraud probability) and limits incentive eligibility to wallets above a minimum Wallet Rank threshold. Genuine players receive a streamlined onboarding experience. Farmer wallets receive a standard flow with no incentive allocation. Player retention on week 2 improves significantly because the reward pool is no longer diluted.

Example: NFT Marketplace

An NFT marketplace routes connecting wallets based on their NFT transaction history. Wallets with significant NFT protocol history (Persona 1-2 NFT variant) see the collector-tier homepage: upcoming drops, rarity analytics, floor price trends. Wallets with no NFT history but high DeFi experience see a “New to NFTs?” bridge experience explaining value mechanics. Wallets under 30 days old see a simplified discovery interface with curated beginner collections. Three flows, one codebase, the Onboarding Router Agent handles the logic.

For more on Web3 User Segmentation and how behavioral data drives Dapp growth, see the full guide.

Growth Agents: From Connection to First Transaction

The Onboarding Router Agent gets users into the right flow. Growth Agents keep them moving through it – from connection all the way to a completed first transaction and beyond. Full documentation on the agent catalogue is available at the Growth Agents learn guide.

Growth Agents are ChainAware’s automated, wallet-aware engagement layer. They analyze each wallet’s behavioral profile and deliver personalized in-app content, re-engagement messages, and conversion nudges – automatically, without requiring manual campaign setup for each user segment.

What Growth Agents Do at Each Stage

Stage: Connected but not transacted (the 90% you are losing)

A wallet connects and leaves without transacting. The Growth Agent fires a re-engagement sequence calibrated to the wallet’s persona:

• For the Power Trader: “You checked our rates last Tuesday. Since then, the USDC lending rate moved from 6.2% to 7.8%. Your current Aave position earns 5.1%. Log in to migrate.” – Specific, data-driven, no fluff.
• For the Yield Farmer: “Your connected wallet holds 2.4 ETH in idle staking. Our vault currently offers 9.4% APY on ETH. One click to deposit.” – Directly referenced on-chain holdings as context.
• For the DeFi Curious: “Welcome back. A lot of new users start with a $20 deposit to see how the protocol works. There is no minimum and you can withdraw anytime.” – Low-stakes, encouraging, no jargon.
• For the Newcomer: “We noticed you connected but didn’t complete your first action. Here’s a 2-minute video showing exactly what happens when you deposit. You are in control at every step.” – Reassurance and education.

Stage: First transaction completed – driving repeat engagement

A wallet transacts for the first time. The Growth Agent shifts from activation to retention. Based on the wallet’s revealed behavior, it personalizes the next suggested action:

• Power Trader who just deposited: immediately surfaces leveraged position options, auto-compounding vaults, and governance participation.
• Yield Farmer who staked: shows projected earnings over 30/90/180 days, suggests portfolio diversification across vault types, invites to yield optimization newsletter.
• First-time user who made a small deposit: sends a milestone congratulation, shows earnings accruing in real time, suggests their next small step at a natural pace.

Stage: At-risk of churn – win-back before they leave

A wallet has not interacted in 14+ days. The Growth Agent reads its current on-chain behavior across other protocols (via Prediction MCP) and detects if it has moved assets elsewhere. If yes, a targeted win-back message fires: “We noticed you moved capital to [competing protocol]. Our current rate on the same asset is now X% higher. Here’s a one-click migration.”

Example: Exchange Onboarding Growth Campaign

A decentralized exchange runs Growth Agents on all new wallet connections for a 30-day period. Prior to Growth Agents, the conversion from connected to first trade was 8%. After deployment – with persona-specific messaging, rate-specific nudges, and idle-asset detection – conversion to first trade rises to 19%. Day-30 retention of those who did transact improves by 31% because the Growth Agent continues delivering relevant value rather than generic newsletters.

For the complete breakdown of how Growth Agents power Dapp growth, see Web3 Business Intelligence: How Behavioral Analytics Drive Growth in 2026 and the Behavioral User Segmentation guide.

Transaction Monitoring Agent: Protect the Users Who Do Convert

Getting a wallet to transact is hard. Losing it to fraud, exploitation, or a bad actor transaction is catastrophic – not just for the user, but for the protocol’s reputation and TVL. The Transaction Monitoring Agent runs 24/7 on every transaction that flows through your Dapp, flagging suspicious activity in real time before it causes damage.

What It Does

The Transaction Monitoring Agent monitors every on-chain transaction connected to your Dapp and applies ChainAware’s predictive fraud model – the same engine that powers the Fraud Detector – to score each transaction as it occurs. When a transaction exceeds a configurable risk threshold, the agent fires an alert via Telegram or webhook, and can optionally trigger an automatic response (shadow ban, transaction block, rate limit).

This is distinct from AML screening. AML checks whether a wallet’s historical funds came from illicit sources – it is backward-looking. The Transaction Monitoring Agent predicts whether a wallet is about to commit fraud – it is forward-looking. For a detailed comparison, see Crypto AML versus Crypto Transaction Monitoring: What’s the Difference and Why You Need Both.

Example: DeFi Lending Protocol Under Flash Loan Attack

A lending protocol is targeted by a coordinated flash loan manipulation. Several wallets – all with high predicted fraud probabilities – begin executing rapid deposit-borrow-withdraw cycles designed to drain the liquidity pool. Without the Transaction Monitoring Agent, the attack completes before any human reviewer can respond. With it, the agent detects the anomalous transaction pattern within the first cycle, fires a Telegram alert to the security team, and automatically rate-limits the flagged wallets. The attack is neutralized at 3% of potential maximum damage.

Example: NFT Marketplace Wash Trading Detection

An NFT marketplace notices artificial volume inflation on certain collections. The Transaction Monitoring Agent identifies the pattern: the same wallets are buying and selling assets between each other at escalating prices, with no genuine change of ownership intent. The agent flags these wallets, the marketplace team reviews the alert within minutes, and the wash-trading cluster is shadow-banned before the artificial floor prices can mislead genuine buyers.

Example: Stablecoin Payment Protocol

A crypto payments protocol uses the Transaction Monitoring Agent as its primary fraud defense for incoming stablecoin payments. Every payment is scored in real time. Payments from wallets with predicted fraud probabilities above a configurable threshold are flagged for manual review before settlement confirmation. Legitimate payments (the vast majority) settle instantly. Suspicious payments are held pending a 2-minute review window. Fraud losses drop by over 80% compared to the prior rule-based system.

The Transaction Monitoring Agent integrates via Google Tag Manager – the same GTM container you likely already use for analytics. For the complete integration guide, see ChainAware Transaction Monitoring Agent: Complete Guide to 24×7 Dapp Fraud Protection.

Fraud Detector: Stop Farming the Funnel Before It Starts

The Onboarding Router Agent and Growth Agents work on genuine users. The Fraud Detector’s job is to identify the wallets that should never enter the onboarding funnel in the first place – before they consume resources, distort metrics, or extract incentives.

What It Does

The Fraud Detector runs a predictive fraud analysis on any wallet address, returning a fraud probability score (0-1) and a status classification: Safe, Watchlist, or Risky. The model achieves 98% accuracy on Ethereum and is trained on ChainAware’s behavioral dataset of 14M+ profiles. Unlike AML tools that check against known blacklists, the Fraud Detector predicts fraud probability for wallets with no prior fraud record – catching first-time fraudsters before they act. For the complete methodology, see the Fraud Detector learn guide.

Example: Incentive Campaign Eligibility

A DeFi protocol runs a 30-day liquidity mining campaign, offering token rewards for wallet connections and first deposits. Without fraud screening, 35% of participating wallets are Sybil accounts or airdrop farmers – clusters of new wallets with no genuine DeFi intent, created specifically to extract rewards. With the Fraud Detector screening all connecting wallets, farmer wallets (Risky status, low Wallet Rank, wallet age under 14 days) are automatically excluded from reward eligibility. The same incentive budget now flows exclusively to genuine users – improving D30 retention of reward recipients from 12% to 41%.

Example: Token Distribution Pre-TGE

A protocol approaching Token Generation Event uses the Fraud Detector to screen its whitelist. Of 8,000 whitelist applications, 1,200 (15%) return Risky or Watchlist status. The team reviews the flagged wallets, removes confirmed Sybil accounts, and reallocates their allocation to the waitlist. The TGE proceeds with a significantly cleaner holder distribution – which positively impacts Token Rank and long-term token stability. For how Token Rank reflects holder quality, see the Token Rank complete guide.

The Fraud Detector is free to use at chainaware.ai. For the complete technical guide, see ChainAware Fraud Detector: The Complete Guide to Predictive Crypto Fraud Detection.

Wallet Auditor: Know Who You’re Onboarding in 30 Seconds

The Wallet Auditor is the atomic unit of ChainAware’s behavioral intelligence system – and the fastest way to understand a specific wallet before or during the onboarding process. It generates a complete behavioral profile in seconds: experience level, risk willingness, predicted intentions, AML status, protocol history, wallet age, transaction volume, and Wallet Rank. The full parameter list is documented at the Wallet Auditor learn guide.

When to Use the Wallet Auditor in Onboarding

Manual partner vetting: Before entering into any business relationship, LP arrangement, or integration partnership with another protocol or individual, audit their wallet. A Power Trader counterparty with 4 years of clean on-chain history is a very different risk profile from a 3-week-old wallet with a Watchlist fraud status. See the complete Wallet Auditor guide for the full vetting workflow.

KOL due diligence: Before paying an influencer or KOL for a promotional campaign, audit their wallet. If their on-chain history shows no genuine DeFi engagement – or worse, a Watchlist status – their audience is unlikely to contain genuine DeFi users. You are paying for reach to an audience that will not convert.

B2B onboarding: When another protocol or DAO wants to integrate with yours, the Wallet Auditor gives you an instant behavioral profile of their treasury wallet – revealing their actual on-chain sophistication and risk profile before contract negotiations begin.

Customer support context: When a user contacts support about a failed transaction or unexpected behavior, audit their wallet immediately. Knowing whether they are an expert or newcomer changes how support should respond – and reveals whether the issue is user error, a protocol bug, or a fraud attempt.

Agent-by-Agent Examples: Real Protocol Scenarios

The following scenarios show how multiple agents work together to solve end-to-end onboarding problems for specific protocol types.

Scenario 1: DeFi Lending Protocol – Full Stack Deployment

Problem: 200 visitors per week, 10 connect, 1 transacts. Incentive campaign attracted farmers. Post-transaction retention at day 30 is 15%.

Agent stack deployed:

• Fraud Detector at connection: screens all connecting wallets, excludes Risky status from incentive eligibility (removes ~25% farmer traffic from reward pool).
• Onboarding Router Agent: classifies remaining wallets into 4 persona flows. Expert wallets see rates dashboard immediately. Beginners see guided 3-step flow.
• Growth Agents: fire re-engagement messages to wallets that connect but don’t transact within 48 hours. Persona-specific rate alerts, idle asset nudges, and milestone messaging.
• Transaction Monitoring Agent: runs 24/7 on all protocol transactions. Fires Telegram alerts on anomalous activity. Auto-rate-limits flagged wallets.

Outcome (90-day measurement): Connect-to-transact rate improves from 10% to 28%. Day-30 retention of transacting users improves from 15% to 34%. Incentive budget efficiency improves by 3x (same budget, 3x genuine recipients).

Scenario 2: Decentralized Exchange – Reducing First-Swap Drop-Off

Problem: Users connect wallets but leave without executing a first swap. The interface is complex. Newcomers are confused by slippage settings and gas estimation.

Agent stack deployed:

• Onboarding Router Agent: identifies Newcomer wallets (Experience Level 1-2) and activates a simplified swap interface with pre-set slippage defaults, gas estimation tooltips, and a “Swap $10 to see how it works” CTA.
• Growth Agents: send a “your first swap is waiting” re-engagement message to wallets that connected but did not complete a swap within 24 hours – including a link back to the simplified interface.
• Fraud Detector: flags wallets connecting via known VPN endpoints or from suspicious transaction clusters – these are excluded from the simplified interface and shown the standard UI to reduce manipulation risk.

Scenario 3: Yield Aggregator – Whale Activation

Problem: High-value wallets (Wallet Rank top 5%) connect during market volatility events but don’t deposit. The protocol’s messaging is optimized for retail, not institutions.

Agent stack deployed:

• Onboarding Router Agent: detects high Wallet Rank, high experience, high balance wallets and routes them to an “Institutional” landing experience: audit reports, smart contract security links, TVL history, team contact for large-deposit support.
• Growth Agents: send a direct “book a call with our BD team” message to whales that connected but did not deposit within 48 hours. High-value personalization: references the specific asset type the wallet holds and current yield opportunity.
• Wallet Auditor: used manually by the BD team to profile each high-value prospect before the call – enabling a genuinely informed conversation about the wallet’s specific holdings and risk profile.

For more on whale detection and high-value user strategies, see Web3 Business Intelligence and the ChainAware Complete Product Guide.

Scenario 4: NFT Marketplace – Launch Day Onboarding

Problem: A major collection launch drives a traffic spike. Server load is high, new wallets are connecting from social channels, and the team cannot manually review who is genuine vs. farming.

Agent stack deployed:

• Fraud Detector: screens all connecting wallets. Wallets with Risky status or Wallet Age under 7 days are rate-limited (can browse but cannot purchase in the first hour of the drop). This prevents Sybil attacks on limited supply drops.
• Onboarding Router Agent: identifies experienced NFT collectors (NFT protocol history, high Wallet Rank) and routes them to an early-access queue with a 5-minute head start on the general public.
• Transaction Monitoring Agent: monitors all purchases for wash-trading patterns. Flags wallets buying and selling between addresses they control. Alerts fire in real time to the platform team.

The Economics of Personalized Onboarding

Personalized onboarding is not a UX project. It is a financial decision. The numbers make this clear.

The Cost of the Status Quo

At a 0.5% visitor-to-transaction rate, a protocol spending $10,000/month on traffic acquires roughly 1,000 visitors, 50 connected wallets, and 5 transacting users. The effective cost per transacting user is $2,000. This is economically viable only if the average transacting user generates more than $2,000 in lifetime protocol revenue – a bar that the vast majority of DeFi users do not clear.

What Personalized Onboarding Changes

If the Onboarding Router Agent and Growth Agents improve connect-to-transact rate from 10% to 25%:

• The same 1,000 visitors → 50 connected wallets → now 12-13 transacting users (up from 5)
• Cost per transacting user drops from $2,000 to approximately $770
• No additional traffic spend required – the improvement comes from better conversion of existing traffic

If the Fraud Detector removes 25% of farming traffic from incentive programs, the same incentive budget now covers 33% more genuine users.

If the Transaction Monitoring Agent prevents one significant fraud event per quarter, the savings in recovered TVL or avoided reputational damage typically exceed the entire annual cost of the full agent stack by a substantial margin.

According to Gartner’s research on personalization ROI, organizations that invest in behavioral personalization achieve 2-3× better unit economics on marketing spend. In DeFi, where acquisition costs are high and the competitive landscape is intense, this efficiency gap determines which protocols survive the next market cycle.

For a deeper look at Web3 marketing ROI and how to measure campaign quality beyond vanity metrics, see Web3 Marketing Analytics: Measure ROI & Optimize Campaigns 2026.

How to Deploy: 4-Step Implementation Guide

Step 1: Baseline Your Current Funnel

Before deploying any agents, establish your baseline. Install ChainAware Web3 Behavioral Analytics via Google Tag Manager (free, no engineering required). Run it for 14 days. Your dashboard will show you the experience distribution, intention profile, and Wallet Rank distribution of your current user base. This is your “before” state – the data that tells you which persona mix you are actually attracting and where the onboarding mismatch is largest.

Step 2: Deploy the Fraud Detector at Connection

Add fraud screening to your wallet connection event in GTM. Every connecting wallet is scored immediately. Configure your threshold: wallets with probabilityFraud above 0.7 are flagged as Risky and excluded from incentive programs automatically. This one step typically recovers 20-35% of incentive budget from farming wallets – often paying for the entire agent stack from day one.

Step 3: Implement the Onboarding Router Agent

Based on your 14-day baseline, design your persona flows. You do not need to build all five immediately – start with two: an Expert flow and a Beginner flow. The Onboarding Router Agent classifies every connecting wallet and triggers the corresponding GTM tag (which controls which frontend experience loads). As you validate the impact, add the remaining persona flows progressively. For developer teams, the Prediction MCP learn guide covers direct API integration for more granular routing logic.

Step 4: Activate Growth Agents and Transaction Monitoring

Once the routing layer is in place, activate Growth Agents to handle wallets that connect but do not transact within 48 hours. Configure re-engagement messages by persona – your analytics baseline already tells you which persona represents your largest drop-off opportunity, so start there. In parallel, deploy the Transaction Monitoring Agent on your primary transaction flows. GTM integration takes under an hour. Configure your Telegram alert webhook and set your risk threshold. The agent runs 24/7 from that point forward with no maintenance required.

For the complete business deployment guide, see How to Use ChainAware.ai as a Business. For AI agent integration via MCP for developers, see 12 Blockchain Capabilities Any AI Agent Can Use.

Frequently Asked Questions

What is the difference between the Onboarding Router Agent and Growth Agents?

The Onboarding Router Agent fires at the moment of wallet connection and routes the user into the right initial experience – it determines what the user sees first. Growth Agents fire after connection and manage the ongoing engagement sequence – re-engagement messages, conversion nudges, retention flows. They work together: the Router Agent gets the user into the right flow, Growth Agents keep them moving through it.

Does deploying these agents require engineering resources?

Not for the no-code path. Behavioral Analytics, Fraud Detector screening, Onboarding Router Agent flows, and Transaction Monitoring Agent can all be configured via Google Tag Manager without changes to your Dapp’s codebase. For protocols that want deeper integration – custom routing logic, API-level personalization – the Prediction MCP provides a developer API. For the MCP integration guide, see 12 Blockchain Capabilities Any AI Agent Can Use.

How does the Transaction Monitoring Agent differ from AML screening?

AML screening checks a wallet’s historical funds against known illicit sources – it is backward-looking. The Transaction Monitoring Agent predicts whether a wallet is likely to commit fraud in its next transaction – it is forward-looking. Both are necessary. AML catches known bad actors; the Transaction Monitoring Agent catches new fraud patterns that have not yet been flagged. For a full comparison, see Crypto AML versus Crypto Transaction Monitoring.

What blockchains are supported?

ChainAware.ai currently supports 8 blockchains including Ethereum, BNB Chain, Base, Polygon, and others. The 14M+ wallet profile dataset spans all supported chains. Check chainaware.ai for the current supported chain list.

How quickly does the Onboarding Router Agent classify a wallet?

The behavioral classification runs in under 100 milliseconds – fast enough to route the user before the first page render completes. The user experience is seamless: the right flow loads as if it was always the default.

What if a wallet is too new to have behavioral data?

New wallets (under 30 days, fewer than 10 transactions) are classified as Newcomer persona by default and routed into the beginner flow. Their fraud probability is also scored – very new wallets with patterns matching known Sybil clusters receive a Watchlist or Risky flag regardless of transaction history. New wallet age itself is a meaningful signal: a very new wallet connecting during an incentive campaign is statistically likely to be a farmer.

Can I use these agents for a token launch or TGE?

Yes – the TGE use case is one of the highest-impact applications. Fraud Detector for whitelist screening, Onboarding Router Agent for tiered access (experienced holders vs. new community members), and Transaction Monitoring Agent for launch-day wash trading detection. For the token quality dimension of a TGE, also see Token Rank and its role in assessing holder quality post-launch.

Is the Wallet Auditor available for free?

Yes – the Wallet Auditor is free at chainaware.ai. Run it on any wallet address and receive a full behavioral profile in seconds. For enterprise integration (automated auditing of all connecting wallets at scale), see ChainAware Enterprise plans. See the complete Wallet Auditor guide.

ChainAware.ai – Web3 Agentic Growth Infrastructure

Stop Losing 99% of Your Visitors.
Deploy the Full Onboarding Agent Stack.

Behavioral Analytics · Onboarding Router Agent · Growth Agents · Transaction Monitoring Agent · Fraud Detector · Wallet Auditor. The complete stack to turn 1-in-200 into 1-in-20. GTM integration, no engineering required. Free to start.

Get Started Free
View Live Analytics Demo
Full Product Guide

The post DeFi Onboarding in 2026: Why 90% of Connected Wallets Never Transact (And How AI Agents Fix It) first appeared on ChainAware.ai.

Last Updated: 2026

The fastest-growing Web3 protocols in 2026 aren’t hiring bigger teams. They’re deploying more agents.

This isn’t a future prediction. It’s a structural shift already underway. DeFi protocols are replacing compliance officers with AML agents that screen every transaction in real time. Growth teams are being augmented – and in some cases replaced – by wallet marketing agents that generate personalized campaigns for 100,000 users simultaneously. Customer success managers are giving way to onboarding routers that detect a new wallet’s experience level in milliseconds and serve the right first experience automatically.

Welcome to the Web3 Agentic Economy.

This article defines the shift, explains why Web3 is uniquely suited for agentic infrastructure, maps the seven core agent roles replacing human functions in DeFi, and shows exactly which ChainAware agents power each role – with real examples of how protocols are deploying them today. We also address the risks honestly, because uncritical automation in financial systems is how catastrophic failures happen.

If you’re building a Web3 protocol, DeFi product, or AI agent pipeline in 2026, this is the strategic context you need to operate in.

What Is the Web3 Agentic Economy?

The Web3 Agentic Economy describes the emerging economic model in which AI agents – not human employees – serve as the primary operators of blockchain protocols, DeFi products, and on-chain financial systems.

In a traditional protocol, a team of humans handles critical functions: compliance officers review suspicious transactions, growth marketers run campaigns, fraud analysts investigate anomalies, customer success teams onboard new users, and treasury managers monitor large holder positions. Each function requires expertise, operates on human timescales (hours, days), and costs significant ongoing salary.

In an agentic protocol, these functions are executed by AI agents: autonomous software programs that observe on-chain data, make decisions based on behavioral models, execute actions (approve, flag, route, message, alert), and improve their performance over time without manual intervention. They operate at machine speed – sub-100ms for most decisions – and at machine scale – millions of wallets simultaneously.

The transition is being enabled by two converging technologies. First, large language models (LLMs) have reached the capability threshold where they can reason about complex, multi-step financial decisions with high accuracy. Second, Model Context Protocol (MCP) – the open standard introduced by Anthropic – has solved the tool integration problem, allowing any AI agent to call blockchain intelligence APIs, databases, and analytics systems in natural language without custom integration work. For the complete infrastructure overview of how AI agents interact with blockchain data, see the ChainAware For AI Agents overview.

The result is what economists would recognize as a factor substitution at the infrastructure layer: human labor in protocol operations is being substituted by agent capital. This is not a gradual process. The protocols that build agentic stacks in 2026 will operate at fundamentally different cost structures and response speeds than those that don’t – and the gap compounds over time.

According to McKinsey’s analysis of generative AI’s economic potential, financial services is one of the sectors with the highest automation potential – with compliance, fraud detection, and customer engagement among the top functions. Web3 sits at the intersection of financial services and fully digitized data, making it the ideal first sector for full agentic deployment.

Why Web3 Is Uniquely Built for AI Agents

Web2 companies struggle to deploy AI agents at scale because their data is fragmented, partially digitized, and locked in proprietary silos. A customer’s purchase history is in one database, their support tickets in another, their email behavior in a third. Building agents that can act across all of these requires enormous integration work, and the data quality is often poor.

Web3 has none of these problems. Three structural properties make blockchain the ideal operating environment for AI agents:

1. Fully digitized from day one. Every transaction, every protocol interaction, every asset movement is recorded on-chain automatically. There is no paper trail to digitize, no legacy system to integrate with. The data exists in a machine-readable format that AI agents can query directly. A wallet’s entire financial history – every DEX trade, every lending position, every bridge transaction – is available in a single on-chain query.

2. Transparent and verifiable. Unlike Web2 behavioral data, which can be fabricated, corrupted, or biased by the platform collecting it, blockchain data is cryptographically verified. An agent can trust that vitalik.eth made 19,972 transactions over 3,730 days because the blockchain is the source of truth, not a company’s analytics database. This makes agent decisions more reliable and auditable.

3. Programmable by design. Smart contracts are machine-readable agreements that execute automatically when conditions are met. AI agents don’t need to negotiate with human counterparts or work through bureaucratic approval processes – they interact directly with protocol logic. An agent that detects a suspicious large withdrawal can automatically trigger a smart contract circuit breaker, not file a ticket for human review.

These three properties mean Web3 didn’t need to be retrofitted for AI agents. It was architected in a way that makes agentic operation a natural evolution. The protocols that recognize this earliest will gain the most durable competitive advantages. See our AI-Powered Blockchain Analysis guide for the technical foundations this is built on.

7 Human Roles Being Replaced by AI Agents in Web3

The agentic transition in Web3 is not about wholesale elimination of human judgment. It is about substituting human execution of repetitive, data-intensive, high-volume decisions with agents that make those decisions faster, more consistently, and at lower cost. Here are the seven core functions already undergoing this transition.

Role 1: Compliance Officer → Transaction Monitoring Agent

Traditional compliance in Web3 requires humans to review flagged transactions, maintain sanctions lists, file Suspicious Activity Reports (SARs), and stay current with evolving regulations across multiple jurisdictions. A senior crypto compliance officer costs $120,000-$200,000 per year and can meaningfully review perhaps 50-100 cases per day.

A transaction monitoring agent screens every transaction in real time – 24/7, across all blockchains – cross-referencing against OFAC SDN lists, mixer interactions, known fraud addresses, and behavioral AML models. It auto-approves clean transactions in under 100ms, escalates medium-risk cases for human review with a pre-written analysis report, and auto-blocks high-risk transactions with documented justification for regulators. Volume processed: unlimited. Cost: a fraction of one compliance officer salary.

This is exactly the function ChainAware’s aml-scorer and fraud-detector agents power – read the full regulatory context in our Blockchain Compliance for DeFi guide. The full catalogue of compliance and fraud agents is documented at the Security & Fraud Agents learn guide.

Role 2: Fraud Analyst → Fraud Detection + Rug Pull Detection Agents

Human fraud analysts in Web3 work reactively: they investigate after something goes wrong. By the time a human identifies a fraud pattern, analyzes wallet history, checks network connections, and issues a warning, the damage is done. Blockchain transactions are irreversible. Post-incident documentation doesn’t help the users who lost funds.

The fraud-detector agent operates predictively – assessing fraud probability before a transaction executes. The rug-pull-detector agent monitors new protocol deployments and token contracts continuously, flagging behavioral patterns that match historical rug pull signatures before users deposit funds. According to TRM Labs’ 2026 Crypto Crime Report, $158 billion in illicit crypto volume was processed in 2025 – the vast majority of which could have been intercepted with predictive behavioral screening that didn’t exist at scale. It exists now. See our Forensic vs AI-Powered Blockchain Analysis comparison for the accuracy difference.

Role 3: Growth Marketer → Wallet Marketing + Onboarding Router Agents

Web3 growth teams spend enormous budgets on campaigns that acquire the wrong users. The fundamental problem: they can’t tell the difference between a high-LTV power trader and a zero-retention airdrop farmer until weeks after acquisition. By then, the CAC is sunk and the user is gone.

The wallet-marketer agent generates personalized engagement campaigns for each wallet based on behavioral profile: experience level, risk tolerance, protocol preferences, predicted intentions. The onboarding-router agent instantly classifies a new wallet and routes it to the right first experience – expert users go straight to the pro dashboard, newcomers get guided tutorials, high-risk wallets get additional verification before access. Our Web3 User Segmentation guide documents protocols achieving 35% → 62% onboarding completion and 40% → 22% churn reduction using these agents.

Role 4: Security Analyst → Trust Scorer + Reputation Scorer Agents

Security analysts in Web3 protocols spend most of their time doing the same thing: evaluating whether a counterparty, user, or protocol is trustworthy enough to interact with. This involves checking wallet history, looking for red flags, assessing track records. It’s time-consuming, inconsistent across analysts, and doesn’t scale.

The trust-scorer agent returns a forward-looking trust probability (0-100%) in under 100ms for any wallet – enabling tiered access decisions at login time. The reputation-scorer agent builds a holistic on-chain reputation profile that captures community standing, governance behavior, and protocol interaction quality over time. Together, they replace the judgment calls that security analysts make manually – consistently, at scale, and with full audit trails.

Role 5: Investment Research Analyst → Token Analyzer + Analyst Agents

Crypto fund research teams spend 3-5 days manually evaluating each new protocol: reading whitepapers, analyzing tokenomics, checking on-chain metrics, assessing team credibility. At 50+ new protocols per week in a bull market, this is humanly impossible to do thoroughly.

The token-analyzer agent evaluates whether a token’s volume is genuine or wash-traded, assesses holder distribution and concentration risk, and flags behavioral patterns that match historical failures. The analyst agent synthesizes all ChainAware data into narrative investment committee reports. What takes a human team 3 days takes an agent pipeline 2 hours – for all 50 protocols simultaneously. For methodology, see our Wallet Rank Guide and Token Rank explainer.

Role 6: Customer Success Manager → Onboarding Router + Wallet Marketer Agents

Customer success in Web3 has always been an impossible problem: users are pseudonymous, there’s no support ticket system, and CSMs have no behavioral data on who their users are. Most protocols don’t even know which users are at risk of churning until they’re already gone.

The onboarding-router agent ensures every user gets the right first experience, dramatically reducing the most common churn trigger: confusion in the first session. The wallet-marketer agent monitors behavioral signals that predict churn – declining activity, shift in protocol preferences, whale exit preparation – and triggers automated re-engagement before the user leaves. This is the entire customer success function running autonomously. See our Behavioral User Segmentation guide for the segmentation logic underpinning these agents.

Role 7: Treasury / Risk Manager → Whale Detector + Wallet Ranker Agents

Protocol treasury managers spend significant time monitoring large holder positions – watching for signs that a whale is preparing to exit, tracking concentration risk, stress-testing liquidity against large withdrawal scenarios. This is reactive work that human managers can only do during business hours.

The whale-detector agent monitors all significant holders 24/7, identifying unusual activity patterns that historically precede large exits – and alerting the team before execution, not after. The wallet-ranker agent provides continuous quality scoring across the entire user base, enabling treasury teams to understand their protocol’s actual user composition, not just its headline TVL number. Our Web3 Business Intelligence guide covers the analytics layer these agents surface.

Agent-by-Agent Examples: When to Use Which

Understanding which agent to deploy for which situation is the practical heart of building an agentic Web3 stack. Here are concrete, real-world scenarios for each ChainAware agent.

fraud-detector – When to use it

Use fraud-detector any time a wallet is about to receive meaningful trust – before approving a large withdrawal, before granting governance rights, before allowing leverage access, before processing a crypto payment. The agent returns a fraud probability score and behavioral red flags in under 100ms.

Example 1: A DeFi lending protocol deploys fraud-detector at the borrow initiation point. Any wallet requesting a loan above $10,000 is automatically screened. Wallets with fraud probability above 15% are required to complete additional verification. Wallets above 40% are automatically declined with a documented reason for regulatory records. Result: fraud losses reduced 78% in the first quarter.

Example 2: A crypto payment processor uses fraud-detector to screen every incoming USDC payment before releasing goods. The agent’s 98% accuracy means near-zero false positives for legitimate customers while catching the fraud cases that previously slipped through blocklist-only screening. Try it yourself: ChainAware Fraud Detector – free.

aml-scorer – When to use it

Use aml-scorer for regulatory compliance screening – any situation where you need to demonstrate Know Your Transaction (KYT) compliance to regulators. Returns sanctions status, mixer interactions, AML risk score, and documentation suitable for regulatory filing.

Example: A regulated crypto exchange operating under MiCA requirements deploys aml-scorer for every withdrawal above €1,000. The agent auto-generates the KYT documentation required by their compliance program, flags cases requiring SAR consideration, and maintains an audit trail for regulators. Cost: 95% less than manual compliance review. Speed: real-time vs 2-5 day human review cycles.

transaction-monitoring-agent – When to use it

Use the Transaction Monitoring Agent for continuous, real-time screening of all protocol activity – not just individual wallet checks but ongoing behavioral monitoring across your entire user base. Detects structuring patterns, velocity anomalies, and coordinated suspicious activity that single-wallet checks miss.

Example: A DEX notices a cluster of wallets executing high-frequency small swaps across multiple accounts – a classic structuring pattern for AML evasion. The transaction monitoring agent identifies the coordinated behavioral pattern across wallets and flags the cluster for review. A human analyst would have seen individual transactions as normal; the agent sees the network pattern. Learn more about our Transaction Monitoring Agent.

rug-pull-detector – When to use it

Use rug-pull-detector before recommending any new protocol, token, or liquidity pool to users. Also use it for ongoing monitoring of protocols where your users have deposited funds.

Example 1: A DeFi aggregator deploys rug-pull-detector as a pre-listing gate. Any new protocol must pass behavioral screening before appearing in their interface. Protocols where developer wallet patterns match historical rug pull signatures are automatically excluded, with the reason documented. Users trust the aggregator more; fewer support escalations from users who lost funds.

Example 2: A portfolio management agent monitors all active LP positions daily using rug-pull-detector. When a protocol’s behavioral pattern shifts – treasury wallet suddenly becomes active, team allocation moves, liquidity lock approaches expiry – the agent alerts users before they can be caught in an exit.

wallet-ranker – When to use it

Use wallet-ranker whenever you need to assess overall user quality – token distributions, governance weighting, acquisition channel evaluation, anti-Sybil screening, and lending credit assessment. Wallet Rank (0-100) is the single best predictor of user LTV in Web3. Read the full methodology: ChainAware Wallet Rank Guide.

Example 1 – Token distribution: A protocol distributes governance tokens to 50,000 early users. Instead of equal distribution (which rewards Sybil farmers equally with genuine users), they use wallet-ranker to weight allocations: Rank 70+ receives 5× allocation, Rank 30-70 receives 1× allocation, Rank below 30 receives 0.1× allocation. Result: 90% of tokens go to Rank 50+ users; post-TGE selling pressure reduced 60%.

Example 2 – Acquisition channel ROI: A growth agent scores every inbound wallet from each marketing channel using wallet-ranker in real time. Discord outreach average rank: 68. Twitter campaign average rank: 25. The agent automatically shifts 70% of the ad budget to Discord-style community channels and away from Twitter mass campaigns. Same total spend, 3× the quality of acquired users.

wallet-marketer – When to use it

Use wallet-marketer to generate personalized engagement content for any wallet – re-engagement campaigns, feature announcements, educational content, governance proposals. The agent analyzes behavioral profile and generates messaging that resonates with that specific wallet’s interests, experience level, and predicted intentions.

Example: A protocol has 80,000 wallets that connected but haven’t transacted in 30 days. Instead of one mass email (which gets 2% open rate), they deploy wallet-marketer to generate segmented messaging: expert DeFi traders receive yield optimization content, NFT collectors receive upcoming drop announcements, newcomers receive simplified tutorials. Result: 340% improvement in re-engagement click-through rate. See our Web3 Marketing Analytics guide for measurement methodology.

onboarding-router – When to use it

Use onboarding-router at the moment any new wallet connects to your product for the first time. The agent classifies the wallet’s experience level, primary activity focus, and risk profile in under 100ms – enabling dynamic routing to the right onboarding flow before the user sees a single screen.

Example: A DeFi protocol has three user types: beginners who need guided education, intermediate traders who need feature discovery, and experts who need immediate access to advanced functionality. Previously, all three saw the same onboarding – and 65% dropped off in the first session. After deploying onboarding-router, each type sees a tailored first experience. Overall onboarding completion: 35% → 67%. Day-30 retention: 28% → 51%.

growth-agents – When to use them

ChainAware’s Growth Agents coordinate the full acquisition-to-retention lifecycle: scoring inbound users, routing them appropriately, monitoring engagement signals, triggering re-engagement at the right moment, and continuously reporting segment economics to growth teams. They are the operational layer that makes behavioral segmentation actionable at scale, not just analytically interesting.

Example: A GameFi protocol deploys Growth Agents across their entire user funnel. Acquisition agent scores every new wallet and reports channel quality daily. Onboarding agent routes users to beginner, intermediate, or expert game tracks. Retention agent monitors play patterns and triggers personalized re-engagement when activity drops. Treasury agent monitors whale player positions and alerts the team before large asset withdrawals. Four agents. Zero additional headcount. Protocol LTV per user up 2.8× in 90 days. Learn more about our Growth Agents.

whale-detector – When to use it

Use whale-detector for protocols where a small number of large holders represent disproportionate TVL or revenue risk – which is almost every DeFi protocol.

Example: A lending protocol’s top 50 holders represent 73% of total deposits. The whale-detector agent monitors all 50 continuously, flagging when any of them shows unusual activity: increased wallet-to-wallet transfers, new bridge transactions, shifting collateral ratios. When Whale #3 starts moving assets in patterns that historically precede large withdrawals, the protocol has 6-48 hours warning to adjust liquidity reserves – rather than discovering the withdrawal in the transaction log after it executes.

trust-scorer – When to use it

Use trust-scorer for tiered access control – adjusting feature access, leverage limits, withdrawal caps, or governance rights based on a wallet’s forward-looking trust probability. Unlike fraud detection (which screens for bad actors), trust scoring enables positive discrimination toward trustworthy users.

Example: A derivatives protocol offers three leverage tiers: 5×, 20×, and 50×. Instead of requiring all users to complete KYC for high leverage (which 60% abandon), they use trust-scorer: Trust 85+ → 50× automatically, Trust 60-85 → 20× with soft verification, Trust below 60 → 5× or full KYC for higher access. Conversion to high-leverage trading up 40%. KYC abandonment down 70%.

reputation-scorer – When to use it

Use reputation-scorer for community quality decisions: governance weight, grant allocation, ambassador identification, DAO membership gating. Reputation score captures community standing and constructive participation – metrics that wallet rank and trust score don’t fully cover.

Example: A DAO receives 400 grant applications. Instead of reading 400 applications manually (weeks of work), the governance agent runs reputation-scorer on every applicant wallet automatically, producing a ranked shortlist of the 30 applicants with the strongest on-chain track records. Human reviewers focus on the top 30. Process time: days → 2 hours.

token-analyzer – When to use it

Use token-analyzer before listing, partnering with, or building yield strategies around any token. Surfaces whether volume is genuine vs wash-traded, holder concentration risk, and behavioral quality of the community.

Example: A yield aggregator evaluates 20 new liquidity pools per week for inclusion in their strategies. Token-analyzer automatically screens each pool: genuine vs wash-traded volume, holder quality, smart money presence, and concentration risk. Pools with more than 40% wash-traded volume or whale concentration above 60% are automatically excluded. Human review time reduced from 3 days to 45 minutes per week.

The Infrastructure Layer: What Agents Need to Operate

AI agents are only as capable as the data and tools they can access. An agent that can reason brilliantly but has no access to real-time behavioral data produces confident-sounding but empty outputs. The infrastructure layer – the behavioral data, prediction models, and tool APIs – is what separates agents that actually improve protocol operations from agents that generate plausible-sounding noise.

For Web3 agents specifically, the infrastructure requirements are:

Behavioral data at wallet level. Not just transaction counts or balance – full behavioral profiles including risk willingness, experience level, protocol preferences, interaction history, and predictive scores. ChainAware maintains this for 14M+ wallets across 8 blockchains, updated continuously.

Prediction models, not just data retrieval. Raw blockchain data is available to anyone. The intelligence is in the models that interpret it: what does this transaction pattern predict about future behavior? Is this wallet likely to churn, to commit fraud, to become a power user? ChainAware’s ML models, trained on years of on-chain behavioral data, provide this predictive layer at 98% fraud prediction accuracy.

Agent-native tool interfaces. This is where MCP changes everything. Before MCP, connecting an agent to blockchain intelligence required writing custom API client code, maintaining schemas, handling authentication – all of which is developer work, not agent work. With ChainAware’s MCP server, any LLM agent can call fraud detection, AML scoring, wallet ranking, and behavioral analytics in natural language. The agent reads the tool description and knows how to call it. See our complete MCP Integration Guide for technical setup, and the Prediction MCP learn guide for the full tool reference.

Real-time inference. Protocol operations can’t wait for batch processing. When a user is in the middle of a withdrawal flow, the fraud check needs to complete in under 100ms – or the UX breaks. ChainAware’s inference latency is sub-100ms for all agents, enabling truly real-time agentic decision-making at transaction points.

This stack – behavioral data + prediction models + MCP tool access + real-time inference – is what ChainAware calls Agentic Growth Infrastructure. It’s the layer that sits between your AI agent (Claude, GPT, or custom LLM) and the blockchain behavioral intelligence it needs to act intelligently on your protocol’s behalf.

The Economics: Agent Stack vs Human Team

The economic case for agentic Web3 operations is not subtle. Here is a direct comparison for a mid-sized DeFi protocol handling $50M-$500M TVL:

The human team cost estimate is conservative – it excludes benefits, recruitment, training, management overhead, and the opportunity cost of senior founders spending time on operational functions instead of product. The agent stack cost covers ChainAware MCP subscription, LLM API costs, and basic infrastructure.

The performance comparison is equally stark. Human compliance processes 50-100 cases per day; the agent processes unlimited cases in real time. Human fraud analyst catches patterns within days; the agent catches them before execution. Human growth marketer sends one campaign to all users; the agent sends 100,000 personalized messages simultaneously. For Web3 credit scoring context, see our Web3 Credit Scoring guide – the same behavioral models power creditworthiness assessments.

This doesn’t mean eliminating all humans. It means redirecting human judgment to where it’s genuinely irreplaceable: strategic decisions, edge case review, regulatory relationship management, and product direction. The agent handles the execution volume; the human handles the exceptions and strategy.

Multi-Agent Protocol Architecture: Three Real Deployments

The most powerful applications of agentic infrastructure come from multiple agents working in coordination – each calling different ChainAware capabilities, passing outputs to each other, and collectively replacing entire operational teams. Here are three real deployment architectures.

Architecture 1: The Fully Agentic DeFi Lending Protocol

A DeFi lending protocol handling $200M TVL deploys five coordinating agents that replace what would have been a 12-person operations team:

Gate Agent (fraud-detector + aml-scorer): Every new wallet attempting to borrow is screened in real time. Fraud probability above 20% → declined with documented reason. AML risk above medium → additional verification required. Processes 10,000 applications per day in under 100ms each.

Credit Agent (wallet-ranker + trust-scorer): For approved wallets, calculates maximum loan size and interest rate tier based on Wallet Rank and Trust Score. Rank 80+, Trust 90+ → best rates and highest limits. Rank 40-60, Trust 60-80 → standard terms. Below thresholds → conservative terms or collateral requirement. Replaces the credit committee function.

Monitoring Agent (transaction-monitoring-agent + whale-detector): Continuously monitors all active loan positions. Flags unusual repayment patterns, collateral movements, and large position changes. Alerts risk team to whale exit preparation 24-48 hours before execution.

Growth Agent (wallet-marketer + onboarding-router): Routes new borrowers to the right onboarding experience, generates personalized follow-up based on borrowing behavior, identifies upsell opportunities when wallet profiles suggest readiness for additional products.

Research Agent (token-analyzer + rug-pull-detector): Continuously screens all collateral assets accepted by the protocol for quality degradation – falling holder quality, rising wash trading, rug pull behavioral patterns – and alerts the team to reduce collateral ratios before a crisis.

Architecture 2: The Agentic Exchange Compliance Stack

A regulated crypto exchange operating under MiCA compliance deploys a three-tier compliance architecture that handles 95% of cases without human intervention. The complete framework for this tiered approach is documented in the Autonomous Compliance Screening use case:

Tier 1 – Fast Path (trust-scorer): Runs in under 100ms at transaction initiation. Trust score 85+ → auto-approve, no further review. Handles 70% of all transactions instantly.

Tier 2 – Standard Review (aml-scorer + fraud-detector): For Trust 50-85, runs full AML and fraud screen. Auto-approves if both pass with documented results. Escalates if either flags risk. Handles 25% of transactions in under 5 seconds.

Tier 3 – Enhanced Review (analyst + reputation-scorer): For Trust below 50, generates a complete compliance report and reputation assessment. Human compliance officer reviews this pre-built report rather than conducting their own analysis. Handles 5% of transactions – the ones that genuinely need human judgment. Human review time per case: 5 minutes (vs 45 minutes without the analyst agent’s pre-built report).

Architecture 3: The Full-Stack Growth Protocol

A Web3 gaming protocol deploys end-to-end agentic growth infrastructure:

At acquisition: wallet-ranker scores every inbound user in real time by channel, reporting daily quality metrics. Growth team reallocates budget weekly based on agent data, not gut feel.

At activation: onboarding-router detects experience level and routes new players to beginner, intermediate, or expert game tracks. Tutorial completion: 35% → 71%.

At retention: wallet-marketer monitors play patterns and sends personalized re-engagement when activity drops – tailored to each player’s preferred game modes and asset preferences. D30 retention: 24% → 47%.

At monetization: whale-detector identifies high-value players early and flags them for VIP treatment – special access, early features, personal outreach from the team. Top 10% of players contribute 80% of revenue; identifying them in week 1 instead of month 3 compounds LTV dramatically. See our AI Marketing in the Privacy Era guide for the cookie-free methodology underlying this approach.

The Risks: What Agents Get Wrong

The Web3 Agentic Economy is not without serious risks. Protocols that deploy agents without understanding their failure modes will create new categories of harm – potentially at a scale and speed that human-operated systems never could. Responsible agentic deployment requires honest accounting of where agents fail.

Hallucination in financial decisions. LLMs can generate confident-sounding but factually wrong outputs. In a marketing context, a hallucinated recommendation wastes budget. In a compliance context, a hallucinated approval of a sanctioned wallet creates legal liability. The mitigation is architectural: agents making compliance or fraud decisions should call verified data sources (like ChainAware’s prediction API) rather than relying on LLM reasoning alone. The agent’s role is to orchestrate tool calls and synthesize verified outputs – not to generate financial assessments from training data.

Adversarial wallets that game agent scoring. If fraud detection is known to be based on behavioral patterns, sophisticated bad actors will study those patterns and create wallets designed to pass screening. This is the same arms race that exists in traditional fraud detection – and the same mitigation applies: continuous model retraining on new fraud patterns, ensemble models that make gaming any single signal insufficient, and human review of edge cases. ChainAware’s models are retrained continuously on new fraud data specifically to stay ahead of adversarial adaptation.

Over-automation without human oversight. Agents making high-stakes decisions without any human checkpoint are brittle. A model drift, a data quality issue, or an adversarial attack can cause systematic errors at machine speed and scale before anyone notices. The architecture should be: agents handle high-volume, low-stakes decisions autonomously; agents surface high-stakes decisions for human review with pre-built analysis. Never remove the human from irreversible, high-value decisions entirely.

False positives harming legitimate users. Any screening system generates false positives – legitimate users incorrectly flagged as risky. In human-operated systems, false positives are caught and corrected through human review. In fully automated systems, they can result in users being locked out of their funds with no recourse. The mitigation: always provide an appeal pathway for flagged users, monitor false positive rates continuously, and design tiered responses (additional verification) rather than binary block decisions for medium-risk cases.

Regulatory uncertainty around agentic compliance. Regulators in most jurisdictions have not yet clarified whether AI-generated compliance documentation satisfies human review requirements. A compliance agent that auto-generates SAR filings may or may not meet the regulatory standard for “reasonable investigation.” Legal review of your jurisdiction’s specific requirements is essential before deploying agentic compliance at scale.

How to Build Your First Agentic Web3 Stack in 2026

The right approach to agentic deployment is incremental. Start with one agent, measure its impact, then expand. Here is the recommended sequence for most protocols:

Step 1: Deploy fraud-detector at your highest-risk touchpoint. If you process withdrawals, put fraud-detector there. If you have a lending product, put it at loan origination. If you’re an exchange, put it at account creation. The ROI on fraud prevention is immediate and measurable – and it builds confidence in the technology before expanding to more complex agent functions. Start free: try the Fraud Detector with any wallet address, no account required.

Step 2: Clone the GitHub repository and configure your MCP server. Visit github.com/ChainAware/behavioral-prediction-mcp, clone the repository, and follow the setup instructions. The .claude/agents/ directory contains all 12 agent definition files – copy the ones relevant to your use case into your project.

Step 3: Get your MCP API key. Subscribe at chainaware.ai/mcp. All plans provide access to all 12 agents. Configure your API key in your environment and test with natural language queries against your AI agent of choice.

Step 4: Add onboarding-router as your second agent. The ROI on personalized onboarding is fast and highly visible – completion rates improve within the first week. This is also the agent with the clearest A/B test structure: run it for half of new users, compare onboarding completion and D7 retention against the control group.

Step 5: Add wallet-ranker to your acquisition channel reporting. Instrument your inbound channels with wallet ranking and let your growth team see quality scores alongside volume metrics for the first time. Most teams are shocked by how dramatically quality varies by channel. Budget reallocation follows naturally.

Step 6: Build toward full-stack multi-agent coordination. Once you’ve validated individual agents, design the coordination layer – how do agents share outputs, how does the output of wallet-ranker feed into onboarding-router’s routing decision, how does fraud-detector’s output trigger different flows in the transaction monitoring agent. This is where the compounding value of agentic infrastructure emerges.

For detailed technical implementation, including code samples, configuration files, and multi-agent orchestration patterns, see the complete MCP Integration Guide. According to a16z’s State of Crypto 2025 report, the protocols that successfully deploy agentic infrastructure in this window will have structural advantages that compound over multiple years – both in cost efficiency and in the behavioral data feedback loops that improve their models over time.

Frequently Asked Questions

Conclusion: The Infrastructure Window Is Open Now

The Web3 Agentic Economy is not a trend to watch – it’s a structural shift to build for. The protocols that deploy agentic infrastructure in 2026 will operate with fundamentally different economics, response speeds, and user experience quality than those that continue relying on human-operated functions. That gap compounds over time: better data, better models, better agent performance, lower cost per decision.

The enabling technology – capable LLMs, the MCP standard, behavioral prediction infrastructure – exists today. The 12 pre-built agent definitions in ChainAware’s GitHub repository cover the seven core functions that agentic protocols need: compliance, fraud detection, growth, onboarding, research, customer success, and treasury monitoring. The same behavioral intelligence that makes vitalik.eth’s spider chart look different from sassal.eth’s is the intelligence that tells your protocol how to treat each of those wallets differently – automatically, in real time, at any scale.

Every wallet has a unique behavioral identity. The Web3 Agentic Economy is the infrastructure that finally lets your protocol act accordingly.

About ChainAware.ai

ChainAware.ai is the Web3 Agentic Growth Infrastructure – the behavioral intelligence layer powering AI agents, DeFi protocols, exchanges, compliance teams, and enterprises. 14M+ wallets analyzed across 8 blockchains. 98% fraud prediction accuracy. 12 open-source MCP agents. Backed by Google Cloud, AWS, and ChainGPT Labs.

→ chainaware.ai | MCP: chainaware.ai/mcp | GitHub: behavioral-prediction-mcp | Free audit: chainaware.ai/audit

The post The Web3 Agentic Economy: How AI Agents Are Replacing Web3 Growth Teams first appeared on ChainAware.ai.

Every AI agent needs tools. A financial advisor agent needs market data. A compliance agent needs regulatory screening. A marketing bot needs audience intelligence. Until now, blockchain intelligence – one of the richest behavioral data sources in the world – has been locked behind complex APIs that require deep crypto expertise to use.

That changes with Model Context Protocol (MCP).

ChainAware has published 12 open-source, pre-built agent definitions on GitHub that give any AI agent – Claude, GPT, or custom LLM – instant access to 14 million+ wallet behavioral profiles, 98% accurate fraud prediction, real-time AML screening, token holder analysis, and more. No crypto knowledge required. No custom integration work. Just clone, configure your API key, and your agent gains blockchain superpowers.

This guide covers all 12 agents, explains the MCP architecture in plain language, shows real-world multi-agent scenarios, and walks you through integration step by step. Whether you’re building financial compliance tools, investment research systems, or growth automation, these blockchain capabilities are now one configuration file away. For a full product overview, see the ChainAware For AI Agents overview.

In This Guide

1. What Is MCP? (Plain Language Explanation)
2. Why MCP vs Direct API Integration
3. Architecture Overview
4. All 12 ChainAware MCP Agents Explained
5. 3 Multi-Agent Scenarios
6. Step-by-Step Integration Guide
7. Use Cases by Domain
8. Frequently Asked Questions

What Is MCP? (Plain Language Explanation)

MCP stands for Model Context Protocol – an open standard introduced by Anthropic in late 2024 that defines how AI agents communicate with external tools and data sources. Think of it as USB-C for AI agents: a single, universal connector that lets any compatible AI system plug into any compatible tool – without custom integration work for each pairing. Full technical documentation and tool reference at the Prediction MCP learn guide.

Before MCP, connecting an AI agent to a database or API required: writing custom function-calling code for each tool, maintaining separate API clients per service, rebuilding integrations whenever tool interfaces changed, and training agents specifically on each tool’s schema.

With MCP, tool providers (like ChainAware) publish a standardized server definition. Any MCP-compatible AI agent – Claude, GPT, open-source LLMs – can automatically discover, understand, and call that tool using natural language. The agent figures out when and how to call the tool based on the task at hand.

According to the official MCP documentation, the protocol is designed to give AI models “a standardized way to access context from tools, files, databases, and APIs.” In practice, this means your compliance agent can call a blockchain AML screening tool the same way it calls a sanctions database – without any extra integration work.

MCP vs Function Calling vs RAG

MCP shines in multi-agent systems where different agents need to share tools, or where a single agent needs to orchestrate calls across many data sources dynamically.

Why MCP vs Direct API Integration

If ChainAware already has a REST API, why use MCP at all? The answer is about agent-native design versus developer-first design.

A traditional REST API is designed for developers: endpoints, authentication headers, JSON schemas, documentation pages. Your AI agent can call it – but you need to write wrapper code, handle errors, parse responses, and teach the agent when and why to make each call.

An MCP server is designed for agents: the capability description, input schema, and expected output are all defined in a format that LLMs natively understand. The agent reads the tool definition and autonomously decides when to invoke it based on the task context.

• Zero integration boilerplate – no API client code to write or maintain
• Autonomous tool selection – agent decides which tool to call, not your code
• Natural language invocation – “check if this wallet is safe” instead of constructing request objects
• Composable with other MCP tools – chain ChainAware calls with database queries, web searches, Slack notifications
• Works across LLM providers – same agent definition works with Claude, GPT, and open-source models
• Maintained by tool provider – when ChainAware updates its capabilities, the MCP definition updates, not your code

According to research from the Anthropic AI safety and alignment team on building effective agents, the most reliable agentic systems use well-defined tool interfaces that agents can understand and invoke without ambiguity. MCP is that interface.

Clone GitHub Repo

Get MCP API Key

Architecture Overview

Understanding how ChainAware MCP fits into an AI agent architecture helps clarify what you’re building. The flow is simple: your agent receives a task, identifies it needs blockchain intelligence, calls the appropriate ChainAware MCP tool in natural language, receives structured results, and incorporates them into its response or next action. The agent never needs to know about REST endpoints, authentication headers, or JSON schemas – MCP handles that layer.

┌─────────────────────────────────────────────────────────┐
│                    Your AI Agent                        │
│   (Claude / GPT / Custom LLM)                          │
│                                                         │
│  "Analyze this wallet before approving the transfer"    │
└──────────────────────┬──────────────────────────────┘
                       │ MCP Protocol
                       ▼
┌─────────────────────────────────────────────────────────┐
│              ChainAware MCP Server                      │
│                                                         │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐  │
│  │fraud-detector│  │  aml-scorer  │  │wallet-ranker │  │
│  └──────────────┘  └──────────────┘  └──────────────┘  │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐  │
│  │token-ranker  │  │trust-scorer  │  │whale-detector│  │
│  └──────────────┘  └──────────────┘  └──────────────┘  │
│               + 6 more agents...                        │
└──────────────────────┬──────────────────────────────┘
                       │ API calls
                       ▼
┌─────────────────────────────────────────────────────────┐
│           ChainAware Prediction Engine                  │
│                                                         │
│  14M+ wallets · 8 blockchains · 98% accuracy           │
│  ML models · Graph neural networks · Real-time data    │
└─────────────────────────────────────────────────────────┘

Each of the 12 agent definition files in the GitHub repository contains the tool description, capability scope, and usage examples that allow any compatible LLM to understand and invoke the capability correctly.

All 12 ChainAware MCP Agents Explained

Each agent below corresponds to a file in the /.claude/agents/ directory. The full catalogue with use case guidance is available at the Ready-Made Agents learn guide. Every agent works with MCP-compatible AI systems (Claude, GPT, custom LLMs) and requires an active ChainAware MCP subscription at chainaware.ai/mcp.

1. fraud-detector

GitHub: chainaware-fraud-detector.md

What it does: Evaluates any wallet address for fraud probability using ChainAware’s ML models trained on 14M+ wallets. Returns a trust score (0-100%), behavioral red flags, mixer interactions, network connections to known fraud addresses, and an overall fraud risk classification. This is ChainAware’s flagship capability – the engine that achieves 98% prediction accuracy by analyzing behavioral patterns rather than just blocklist matching. Full documentation at the Security & Fraud Agents learn guide.

Who needs it: Payment processors that need to screen crypto payees before releasing funds. DeFi protocol operators deciding whether to allow large withdrawals. Exchange compliance teams reviewing high-value accounts. Insurance underwriters assessing crypto custody risk. Lending platforms evaluating borrower creditworthiness in Web3.

Real-world integration example: An agent prompt like “A user wants to withdraw $85,000 from our DeFi protocol to wallet 0x4a2b…c8f1. Before approving, run a full fraud assessment and tell me if this transaction is safe to process” – the agent calls fraud-detector, receives the trust score and risk factors, and either auto-approves or flags for human review – all without the developer writing a single API call. See the complete guide: ChainAware Fraud Detector Guide.

2. rug-pull-detector

GitHub: chainaware-rug-pull-detector.md

What it does: Analyzes a token or project wallet for rug pull indicators – behaviors that signal the founders or team intend to abandon the project and exit with investor funds. Detection signals include: treasury wallet concentration, team allocation patterns, liquidity lock status, developer wallet interaction history, sudden large transfer preparation, and similarity to historical rug pull behavioral signatures.

Who needs it: Investment research agents evaluating new DeFi projects. DAO governance bots assessing partnership proposals. Token launch platforms conducting pre-listing due diligence. Institutional crypto fund managers screening emerging positions.

Real-world integration example: “A new DeFi yield protocol launched 3 weeks ago and is offering 800% APY. The contract address is 0x9c3d…f2a7. Assess the rug pull risk before we recommend it to our users.”

3. aml-scorer

GitHub: chainaware-aml-scorer.md

What it does: Runs comprehensive Anti-Money Laundering screening on a wallet address. Returns sanctions list status (OFAC SDN and equivalents), mixer/tumbler interaction history, connections to known illicit addresses, geographic risk indicators, transaction structuring patterns, and an overall AML risk score. Designed to meet regulatory requirements for VASP compliance under FATF Recommendation 16 and regional equivalents.

Who needs it: Any compliance agent operating in regulated financial environments. Banks integrating crypto payment rails. Exchanges required to file SARs. Fintech platforms offering crypto on/off ramps. See our complete Blockchain Compliance Guide for regulatory context.

Real-world integration example: “New corporate client wants to pay our invoice in USDC from wallet 0x7b1e…d4c9. Run a full AML check and tell me if we can legally accept this payment without filing a SAR.”

4. wallet-ranker

GitHub: chainaware-wallet-ranker.md

What it does: Generates a comprehensive Wallet Rank score (0-100) for any address, consolidating 10 behavioral parameters: risk willingness, experience level, risk capability, predicted trust, intentions, transaction categories, protocol diversity, AML status, wallet age, and balance. Full methodology: ChainAware Wallet Rank Guide.

Who needs it: Growth agents prioritizing user acquisition spend. Token distribution systems that reward high-quality users. DAO governance systems weighting voting power by wallet quality. Lending protocols adjusting credit limits by wallet sophistication.

5. token-ranker

GitHub: chainaware-token-ranker.md

What it does: Assesses the quality of a token’s holder base using ChainAware’s behavioral intelligence. Instead of measuring price or market cap, Token Rank measures who holds the token – the average Wallet Rank of holders, distribution concentration, holder experience levels, and ratio of genuine long-term holders vs farmers and bots. Full explanation: What Is Token Rank?

Who needs it: Investment research agents evaluating token fundamentals beyond price. Listing committees assessing project quality for exchange or launchpad inclusion. Institutional fund managers conducting due diligence.

6. reputation-scorer

GitHub: chainaware-reputation-scorer.md

What it does: Builds a holistic on-chain reputation profile for a wallet – synthesizing transaction history quality, protocol interaction integrity, community participation, governance behavior, and behavioral consistency over time. Unlike trust score (which focuses on fraud risk) or wallet rank (which measures overall quality), reputation score captures community standing.

Who needs it: DAO governance agents evaluating voting eligibility and weight. Marketplace platforms assessing seller trustworthiness. Peer-to-peer lending agents evaluating borrower reliability without credit bureaus.

7. trust-scorer

GitHub: chainaware-trust-scorer.md

What it does: Returns a focused trust probability score (0-100%) representing the likelihood that a wallet will behave legitimately in future transactions. Trust score is forward-looking (predicts future behavior) whereas fraud detection is risk-weighted (assesses current risk level). Useful for tiered access decisions: high trust → full access, medium trust → enhanced monitoring, low trust → additional verification required.

Who needs it: Access control agents managing feature gating in DeFi platforms. KYC-lite systems that use behavioral trust as a supplement to identity verification. Risk management systems setting leverage limits based on behavioral trust.

8. analyst

GitHub: chainaware-analyst.md

What it does: A general-purpose blockchain intelligence agent that synthesizes multiple ChainAware data points into comprehensive analytical reports. Instead of returning raw scores, the analyst interprets and contextualizes behavioral data – writing narrative summaries, identifying patterns, comparing against benchmarks, and highlighting actionable insights.

Who needs it: Research report generation pipelines delivering insights to investors or executives. Compliance reporting agents generating regulatory documentation. Due diligence automation tools that need readable summaries, not just numbers.

9. token-analyzer

GitHub: chainaware-token-analyzer.md

What it does: Deep-dives into a specific token – analyzing its smart contract interactions, holder distribution, whale concentration, trading pattern quality (genuine vs wash trading), liquidity depth and health, and on-chain growth metrics. Goes beyond surface-level market cap and volume to assess whether a token has genuine ecosystem traction or manufactured metrics.

10. whale-detector

GitHub: chainaware-whale-detector.md

What it does: Identifies, profiles, and monitors high-value wallet addresses (“whales”) – wallets with significant portfolio value and market influence. Returns whale classification, portfolio composition, recent large movement signals, historical behavior during market events, and behavioral predictions for likely near-term actions.

11. wallet-marketer

GitHub: chainaware-wallet-marketer.md

What it does: Generates personalized marketing and engagement strategies for a specific wallet based on its behavioral profile. Analyzes experience level, risk tolerance, protocol preferences, and predicted intentions to recommend the right messaging tone, which product features to highlight, optimal communication timing, and appropriate incentive structures.

12. onboarding-router

GitHub: chainaware-onboarding-router.md

What it does: Instantly classifies a newly connecting wallet and routes it to the appropriate onboarding experience based on behavioral profile. Determines experience level (1-5), risk tolerance, primary activity focus (DeFi, NFT, gaming, trading), and predicted product fit – then recommends the specific onboarding path, feature exposure sequence, support level, and educational content appropriate for that wallet.

Try Fraud Detector Free

Wallet Auditor – Free

3 Multi-Agent Scenarios

The real power of MCP emerges when multiple agents collaborate – each calling different ChainAware capabilities to accomplish complex tasks that no single agent could handle alone. Here are three production-ready architectures.

Scenario 1: Investment Research Pipeline

A crypto fund’s AI research system needs to evaluate 50 new DeFi protocols per week and deliver investment recommendations to the investment committee. The pipeline involves three coordinating agents:

Agent A – Initial Screening (calls rug-pull-detector + token-ranker): Scans every new protocol automatically. Filters out rug pull risks and low-quality token communities in the first pass. Reduces 50 protocols to 15 worth deeper analysis.

Agent B – Deep Analysis (calls token-analyzer + whale-detector + wallet-ranker): For each surviving protocol, runs full token analysis, identifies whale concentration risk, and assesses the quality of the top 100 holders.

Agent C – Report Generation (calls analyst): Synthesizes all data into investment committee-ready memos with narrative summaries, risk assessments, and buy/watch/pass recommendations.

Scenario 2: Real-Time Compliance Agent

A regulated crypto exchange needs to screen every withdrawal request in real-time without slowing down the user experience. Three compliance agents run in parallel:

Fast Path Agent (calls trust-scorer): Instant trust check runs in <100ms. For high-trust wallets (score 85+), auto-approves withdrawal. Handles 70% of requests without further review.

Standard Review Agent (calls aml-scorer + fraud-detector): For medium-trust wallets (score 50-85), runs full AML and fraud screen. Auto-approves if both pass, escalates if either flags risk.

Enhanced Review Agent (calls analyst + reputation-scorer): For low-trust wallets, generates a full compliance report and reputation assessment that human compliance officers review before decision.

Scenario 3: Growth and Marketing Automation

A DeFi protocol’s growth team uses AI agents to run the entire user acquisition and retention lifecycle without manual segmentation work:

Acquisition Agent (calls wallet-ranker): Scores inbound users from each marketing channel in real-time. Reports Wallet Rank distribution per channel, enabling budget reallocation toward channels that deliver high-quality users (Rank 70+) instead of airdrop farmers (Rank <30).

Onboarding Agent (calls onboarding-router): Instantly routes each connecting wallet to the right first experience – expert users get the pro dashboard immediately, newcomers get guided tutorials, and high-fraud-risk wallets get additional verification before access. Completion rates increase from 35% to 62%.

Retention Agent (calls wallet-marketer + whale-detector): Monitors all active users for churn signals and whale exit preparation. Automatically triggers personalized retention campaigns for at-risk power users.

Step-by-Step Integration Guide

Getting started with ChainAware MCP takes under 30 minutes for a working integration. For additional setup guidance, see the Prediction MCP learn guide. Here’s the complete path from zero to production.

Step 1: Get Your MCP API Key

Visit chainaware.ai/mcp and select a subscription plan. All plans provide access to the full MCP server with all 12 agent capabilities. The API key grants authenticated access to ChainAware’s prediction engine for your MCP requests.

Step 2: Clone the GitHub Repository

git clone https://github.com/ChainAware/behavioral-prediction-mcp.git
cd behavioral-prediction-mcp

Step 3: Configure Your API Key

# Set your ChainAware API key as an environment variable
export CHAINAWARE_API_KEY="your_api_key_here"

# Or add to your .env file
echo "CHAINAWARE_API_KEY=your_api_key_here" >> .env

Step 4: Configure Your MCP Client

{
  "mcpServers": {
    "chainaware": {
      "command": "node",
      "args": ["path/to/behavioral-prediction-mcp/server.js"],
      "env": {
        "CHAINAWARE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Step 5: Select the Agents You Need

Copy the relevant agent definition files from .claude/agents/ to your project. Each file is independent – you don’t need all 12. A compliance-focused deployment might only need aml-scorer, fraud-detector, and trust-scorer. A growth platform might only need wallet-ranker, onboarding-router, and wallet-marketer.

Step 6: Test with Natural Language

Once configured, test your integration by asking your agent natural language questions: “Check if wallet 0x1234…5678 is safe to transact with”, “What’s the fraud risk on this address?”, “Give me the Wallet Rank for 0xabcd…ef01”, “Is this token’s volume genuine or wash-traded?”, “Should we onboard this new user to beginner or expert flow?”

Use Cases by Domain

ChainAware MCP agents aren’t just for crypto companies. Any AI system that handles financial relationships, identity verification, or community management can benefit from blockchain behavioral intelligence.

Financial Services & FinTech

• Payment processors: fraud-detector + aml-scorer for every crypto payment acceptance
• Neo-banks with crypto rails: trust-scorer for tiered feature access without full KYC
• Crypto lending platforms: wallet-ranker + reputation-scorer for creditworthiness assessment
• Insurance underwriters: analyst for crypto custody risk reports

Institutional Investment

• Crypto funds: Full pipeline using rug-pull-detector → token-ranker → token-analyzer → analyst
• Trading desks: whale-detector for large holder movement signals
• Research platforms: token-analyzer for data-driven token assessments

DeFi & Web3 Products

• DEXs and lending protocols: fraud-detector + trust-scorer for real-time transaction screening
• NFT marketplaces: reputation-scorer for seller trust, whale-detector for high-value buyer identification
• DAOs: reputation-scorer + wallet-ranker for governance weight calibration
• Launchpads: rug-pull-detector + token-analyzer for project screening

Marketing & Growth

• Web3 marketing platforms: wallet-marketer for personalized campaign generation
• CRM systems: wallet-ranker for behavioral segmentation without PII
• Growth automation tools: onboarding-router for intelligent user flow selection
• Token distribution platforms: wallet-ranker for anti-sybil, quality-weighted distributions

Frequently Asked Questions

Do I need to know blockchain or crypto to use these agents?

No. The entire point of MCP is abstraction – your AI agent understands and calls the tools in natural language. You describe what you want (“check if this wallet is trustworthy”) and ChainAware’s MCP server handles all the blockchain-specific complexity. You need a ChainAware API key and the agent definition files. No crypto expertise required.

Which AI systems are compatible with ChainAware MCP?

Any MCP-compatible system, including Claude (all versions), GPT-4 and later (via MCP bridges), open-source models running in MCP-compatible frameworks, LangChain agents, AutoGen multi-agent systems, and custom LLM pipelines. See the MCP documentation for framework-specific setup.

What data does ChainAware analyze and how accurate is it?

ChainAware analyzes 14M+ wallet addresses across 8 blockchains (Ethereum, BNB Smart Chain, Polygon, Base, Solana, Avalanche, Arbitrum, Haqq Network). All data is derived from public on-chain transaction history – no personal information is collected or required. Fraud prediction accuracy is 98%, measured as F1 score on held-out test data. Inference latency is <100ms for real-time applications.

Is the GitHub repository open source? Can I modify the agents?

Yes. The agent definition files in the behavioral-prediction-mcp GitHub repository are open source. You can fork the repo, modify agent descriptions, adjust behavior, and create custom agent definitions that call ChainAware’s underlying capabilities in new ways. The MCP subscription covers API access; the agent definitions themselves are free to use and modify.

Conclusion

The emergence of MCP as an open standard for AI agent tool integration marks a fundamental shift in how blockchain intelligence gets deployed. With ChainAware’s 12 pre-built MCP agents, any AI agent – compliance bot, investment research system, growth automation platform, due diligence pipeline – can now call upon 14 million wallet behavioral profiles, 98% accurate fraud prediction, real-time AML screening, and comprehensive token analysis in natural language.

Clone the repo. Get your API key. Give your agent blockchain superpowers.

Clone GitHub Repo

Get MCP API Key

Try Fraud Detector Free

The post 12 Blockchain Capabilities Any AI Agent Can Use (MCP Integration Guide) first appeared on ChainAware.ai.

If you’ve built or used AI agents in Web3, you already know the problem: they behave like autopilot ships. Reliable in calm water, but rigid when conditions shift. A user changes their behavior, a market moves, a wallet suddenly turns active – and the agent keeps serving yesterday’s playbook.

The gap between what AI agents could do and what they actually do comes down to one missing ingredient: personalization powered by real-time on-chain data.

This guide explains why on-chain behavioral personalization is becoming the defining competitive advantage for Web3 AI agents, what the technical architecture looks like, and how projects are already using it to drive measurable gains in conversion and retention.

The Problem: Why Generic AI Agents Fail in Web3

Most AI agents deployed in Web3 today operate on one of two flawed models:

1. Static rules – hard-coded logic that responds the same way to every wallet regardless of history
2. Batch analytics – overnight data processing that’s already stale by the time it reaches the agent

Neither model reflects how real users behave. A DeFi trader who moved $200K into a liquidity pool this morning has completely different needs than the same wallet address did six months ago when it held only ETH. A rule written last quarter cannot capture that shift. A batch job running at midnight won’t catch it in time to matter.

The consequences are tangible. Generic messaging feels irrelevant. Irrelevant messaging gets ignored. Ignored prompts kill conversion. In Web3, where users are anonymous, cynical about marketing, and have dozens of competing platforms one click away, the cost of a generic experience is measured directly in churn.

According to McKinsey’s personalization research, companies that get personalization right generate 40% more revenue from those activities than average players. The same dynamic is now arriving in Web3 – and AI agents are the delivery mechanism.

For a broader picture of where AI in Web3 is heading, see our analysis of real AI use cases for Web3 projects and the distinction between attention AI vs. real utility AI in Web3.

What On-Chain Personalization Actually Means

Personalization in Web3 is fundamentally different from Web2 personalization. There are no cookies, no login histories, no CRM records. There is only the blockchain – and for those who know how to read it, the blockchain is the richest behavioral dataset in existence. The methodology behind turning on-chain data into actionable behavioral profiles is documented at the Web3 User Analytics learn guide.

Every wallet tells a story:

• Which protocols it uses (Aave, Uniswap, GMX, OpenSea…)
• How frequently it trades, lends, or stakes
• Its risk appetite – conservative holder vs. aggressive leverage trader
• Its experience level – how long it has been active, how many chains it operates on
• Its predicted next action – based on behavioral patterns across 14M+ similar wallets

This is what ChainAware.ai calls a Web3 Persona – a continuously updated behavioral fingerprint for every wallet, calculated across 8 blockchains and refreshed in real time. A Web3 Persona is not a static label. It evolves as the wallet evolves, and it drives every personalization decision an AI agent makes.

When an AI agent has access to a Web3 Persona, it stops guessing and starts knowing. It doesn’t show a generic DeFi prompt to every user – it shows a yield farming suggestion to the active lender, a risk warning to the high-leverage trader, and an onboarding guide to the wallet that just bridged its first ETH.

The Technology Making It Possible

Three converging technologies have made real-time, on-chain personalization viable for AI agents at scale.

1. Predictive Behavioral Analytics

Raw transaction data is not personalization fuel on its own. It needs to be transformed into behavioral signals: trading frequency, protocol affinity, risk profile, and predicted future actions. This transformation requires AI models trained on billions of data points across millions of wallets.

ChainAware.ai’s Web3 Predictive Data Layer does exactly this – processing 1.3 billion+ predictive data points across 14M+ wallets to produce actionable behavioral signals rather than raw logs. The result is predictions, not descriptions: not “this wallet traded ETH” but “this wallet has a high probability of staking in the next 14 days.”

2. Real-Time On-Chain Data Streaming

Batch processing is the enemy of personalization. By the time overnight analytics are ready, the user moment has passed. Real-time data streaming – ingesting swaps, liquidity moves, staking events, and contract interactions as they happen – gives AI agents the freshness they need to act at the right moment.

According to Harvard Business Review’s research on AI-driven customer experience, real-time context delivery is the single biggest differentiator between AI deployments that improve outcomes and those that don’t.

3. The Model Context Protocol (MCP) Standard

Even with great behavioral data, there’s a delivery problem: how do you get on-chain signals into an AI agent without building a custom pipeline for every chain, every data source, and every agent framework?

The Model Context Protocol (MCP) solves this. MCP is an emerging standard – pioneered in part by Anthropic – that defines a unified interface for delivering context to AI models. Think of it as the USB-C port of AI personalization: one connector, endless compatible applications. Any LLM or AI agent that speaks MCP can instantly receive structured behavioral context from a compliant data source.

How the ChainAware.ai Behavioral Prediction MCP Works

The ChainAware.ai Behavioral Prediction MCP is the implementation of this standard applied to Web3 behavioral intelligence. It connects any LLM or AI agent to ChainAware.ai’s full predictive data layer – 14M+ Web3 Personas across 8 blockchains – through a single MCP endpoint. Full technical reference at the Prediction MCP learn guide.

Here’s what happens when a user connects their wallet to a Dapp that has integrated the Behavioral Prediction MCP:

1. The wallet address is passed to the MCP endpoint
2. ChainAware.ai returns the wallet’s full Web3 Persona: behavioral categories, Wallet Rank, risk profile, protocol usage, predicted next actions, and more
3. The AI agent receives this context and immediately adapts its response, content, and calls-to-action to match that specific user
4. All of this happens in real time – before the user sees their first screen

For AI developers, the integration takes minutes. There is no need to build blockchain indexers, train behavioral models, or maintain data pipelines. The MCP endpoint delivers everything the agent needs in a structured, ready-to-use format.

The MCP unlocks use cases that were previously impractical to build:

• 1:1 user conversion – every interaction personalized to the wallet’s actual behavioral history
• Wallet comparison – compare any two wallets across behavioral dimensions on demand
• Reputation scoring – instant trustworthiness scores for borrowers, counterparties, or governance voters
• ABC wallet ranking – segment and rank any wallet list by quality or predicted engagement
• Personalized outreach generation – create messages that reference what a wallet has actually done on-chain

We covered the full technical architecture in our dedicated deep-dive: Prediction MCP for AI Agents: Personalize Decisions from Wallet Behavior.

Real-World Use Cases Across DeFi, GameFi & NFTs

Abstract personalization benefits become concrete when you map them to specific product contexts. Here is how AI agents with behavioral intelligence perform across the major Web3 verticals.

DeFi Lending Protocols

A lending protocol integrated with the Behavioral Prediction MCP can immediately identify whether a connecting wallet is an experienced DeFi borrower or a first-time user. The AI agent then shows the experienced borrower the highest-yield vault options and optimal leverage parameters based on their historical risk appetite, shows the first-timer a guided onboarding flow with conservative collateral suggestions, and automatically offers better loan terms to wallets with high Credit Scores. The full onboarding routing architecture is documented at the Agentic Onboarding Personalisation use case.

This is not hypothetical. SmartCredit.io deploys ChainAware.ai’s behavioral data layer in production to differentiate borrowing terms by wallet quality. Read the full outcome in our SmartCredit.io conversion case study.

DEX and Trading Platforms

Trading platforms have historically offered every user the same interface. With behavioral personalization:

• High-frequency traders see advanced order types and leverage tools front-and-center
• Passive holders see staking and yield options
• Wallets flagged by the Predictive Fraud Detector are screened before they can execute large trades

GameFi and NFT Platforms

GameFi platforms can use wallet behavioral data to adjust difficulty, reward structures, and in-game offers based on each player’s on-chain risk profile and spending history. An NFT marketplace can surface collections most likely to match a wallet’s past buying patterns, significantly improving discovery and reducing bounce rate.

AI Chatbots and Support Agents

A Web3 project’s AI support agent typically knows nothing about the user asking the question. With the Behavioral Prediction MCP, it instantly knows whether the user is a veteran DeFi participant or a newcomer, which protocols they actively use, whether their wallet has any risk flags, and what they’re most likely trying to accomplish. The result is support interactions that feel like talking to a knowledgeable advisor – not a generic FAQ bot.

Business Impact: Conversion, Retention & Revenue

Personalization is not a UX nicety – it’s a growth strategy with direct, measurable ROI. Here is what the data shows across Web2 and early Web3 implementations.

Conversion Rate Improvements

When an AI agent surfaces the right product to the right wallet at the right moment, conversion rates increase substantially. In Web2, Salesforce research shows that 73% of consumers expect companies to understand their needs and expectations. The wallets connecting to your Dapp are no different. For the complete suite of Growth Agents powering this conversion layer, see the Growth Agents learn guide.

Retention and Lifetime Value

Retention in DeFi is notoriously difficult. Users are mercenary, chasing the best yields across dozens of protocols. Personalization creates a moat: when a platform consistently surfaces relevant opportunities, users stop hunting elsewhere. The platform becomes their default. This is the same mechanism that makes Netflix sticky: not just the content, but the feeling that the platform knows you.

Fraud Reduction as a Revenue Driver

Personalization also works defensively. When AI agents know their users’ behavioral profiles, they can instantly flag anomalies. A wallet that has never traded more than $5,000 in a single transaction suddenly attempting a $500,000 withdrawal is a red flag – one that a personalized agent catches immediately, while a generic agent waves through. Our deep dive on predictive fraud detection covers this in full.

How to Implement Personalization in Your AI Agent: Step by Step

Step 1: Establish Your Behavioral Data Source

You need a source of on-chain behavioral intelligence that is accurate, real-time, and multi-chain. The faster path: connect to ChainAware.ai’s existing data layer via the Behavioral Prediction MCP. It provides instant access to 14M+ Web3 Personas across 8 chains, without any infrastructure investment. The Enterprise API is also available for teams that want programmatic access at scale.

Step 2: Define Your Personalization Variables

Identify which behavioral signals matter most for your specific use case. For a lending protocol, the key variables might be Credit Score, risk profile, and borrowing history. For a DEX, it might be trading frequency, preferred token pairs, and Wallet Rank. Start with 2-3 variables and expand from there.

Step 3: Map Signals to Agent Actions

Create explicit mappings: if Wallet Rank > 70th percentile, show premium features; if predicted behavior = “likely to stake,” surface staking products; if fraud score > 0.7, require additional verification.

Step 4: Build the MCP Integration

Connect your AI agent or LLM to the Behavioral Prediction MCP endpoint. Pass the wallet address on connection, receive the behavioral context payload, and inject it into your agent’s system prompt or decision logic. The integration is documented at swagger.chainaware.ai.

Step 5: Test, Measure, and Iterate

Run A/B tests comparing personalized flows against your existing generic experience. Measure conversion rate, session depth, and retention at 7, 14, and 30 days.

Measuring What Works: KPIs for Personalized AI Agents

You cannot improve what you don’t measure. These are the key performance indicators that matter specifically for personalized AI agent deployments in Web3.

Primary Conversion Metrics

• Wallet-to-action conversion rate – what percentage of connecting wallets complete a target action after receiving a personalized prompt vs. a generic one
• Time-to-first-action – personalized experiences consistently reduce the time between wallet connection and first meaningful action
• CTA click-through rate by behavioral segment – which Web3 Persona segments respond best to which offer types

Retention Metrics

• 7/14/30-day retention by personalization cohort – do wallets that received personalized experiences return more often?
• Session depth – number of interactions per session for personalized vs. generic users

According to Gartner’s research on AI personalization in digital commerce, organizations that measure and iterate on personalization KPIs achieve 2-3x better outcomes than those that deploy personalization without structured measurement.

The Future: Agents That Truly Know Their Users

The trajectory is clear. AI agents in Web3 are moving from reactive to proactive, from generic to personalized, from static to continuously learning. Several forces are accelerating this shift:

• User expectations are rising. Web2 has conditioned every internet user to expect personalization as the default.
• Multi-chain complexity is increasing. As users operate across more chains simultaneously, only a multi-chain behavioral layer – like ChainAware.ai’s, which covers 8 chains – can build the full picture.
• AI agents are proliferating. The MCP standard is creating a new category of AI-native Web3 infrastructure. Those agents will need behavioral intelligence to be useful. See the ChainAware For AI Agents overview for the complete infrastructure layer.
• Regulatory pressure is intensifying. Knowing who your users are – their behavioral history, risk profile, and Wallet Rank – is becoming essential not just for conversion but for AML compliance and fraud prevention.

For a broader view of where AI agents are heading in Web3, see our piece on how AI agents are revolutionizing Web3.

Conclusion: Personalization Is the Moat

Generic AI agents are a commodity. Any team can deploy one. The competitive advantage in Web3 AI is not having an agent – it’s having an agent that knows its users, adapts to their behavior in real time, and gets smarter with every interaction.

On-chain behavioral data, delivered through the Model Context Protocol, is the foundation of that advantage. ChainAware.ai’s Behavioral Prediction MCP gives any AI agent or LLM instant access to 14M+ Web3 Personas across 8 blockchains – no infrastructure investment, no model training, no blockchain indexing required.

The wallets are talking. The behavioral signals are there. The only question is whether your AI agent is listening.

The post Why Personalization Is the Next Big Thing for AI Agents in Web3 first appeared on ChainAware.ai.

AI agents are only as smart as the context they receive. Give an agent generic data and it produces generic decisions. Give it a real-time behavioral profile of the specific wallet it’s talking to – and everything changes.

That’s the core promise of the ChainAware.ai Behavioral Prediction MCP: a single protocol endpoint that delivers deep, continuously updated on-chain intelligence to any AI agent or LLM, the moment it needs it. No blockchain indexers to build. No models to train. No data pipelines to maintain.

This guide covers everything developers and Web3 product teams need to understand: what the Prediction MCP is, how it works architecturally, what it unlocks in practice, and how to integrate it step by step.

Why On-Chain Context Is the Missing Layer for AI Agents

Most Web3 AI agents today suffer from the same blind spot: they know nothing about the specific wallet they’re interacting with. They serve every user the same prompt, the same interface, the same call-to-action – regardless of whether that wallet has $50 or $5 million in assets, whether it’s a seasoned DeFi lender or a first-time bridge user.

The consequences are predictable. Conversion rates are low. Users disengage. The agent’s “intelligence” is largely performative – it can generate fluent text, but it’s guessing at what the user actually wants.

The fix is not a better language model. It’s better context. And in Web3, the richest possible context comes from the blockchain itself.

Every wallet tells a detailed story: which protocols it uses, how frequently it trades, its risk appetite, its experience level across chains, and – critically – what it is likely to do next. According to McKinsey’s personalization research, companies that use behavioral data to personalize interactions generate up to 40% more revenue than those that don’t. The same principle applies in Web3 – and the blockchain provides richer behavioral data than any cookie or CRM record.

The challenge has always been delivery: how do you get that on-chain behavioral intelligence into an AI agent, in real time, without building a massive data infrastructure from scratch? That’s exactly what the Model Context Protocol solves.

For a broader look at how AI and Web3 are converging, see our piece on real AI use cases for every Web3 project and our analysis of attention AI vs. real utility AI.

What the Behavioral Prediction MCP Is

The Model Context Protocol (MCP) is an open standard – pioneered by Anthropic – that defines a unified interface for delivering structured context to AI models. It’s the equivalent of a universal connector: instead of each AI agent needing custom integrations with every data source, MCP provides a single, standardized channel through which any compliant data provider can deliver context to any compliant agent.

The ChainAware.ai Behavioral Prediction MCP is the implementation of this standard for Web3 behavioral intelligence. It connects any LLM or AI agent framework to ChainAware.ai’s Web3 Predictive Data Layer – a continuously updated database of 14M+ Web3 wallet profiles across 8 blockchains, built from 1.3 billion+ predictive data points.

When an AI agent connects via the MCP endpoint and passes a wallet address, it receives back a complete, structured behavioral profile – the wallet’s Web3 Persona – including risk scores, behavioral categories, predicted next actions, Wallet Rank, and protocol usage history. The agent can immediately use this context to personalize its response, without any additional processing.

This is a fundamentally different architecture from traditional analytics. Traditional tools tell you what happened. The Behavioral Prediction MCP tells your agent what is about to happen – and lets it act accordingly.

Architecture: How the Behavioral Prediction MCP Works

Understanding the architecture helps you integrate faster and design better personalization logic. Here’s how data flows from the blockchain to your AI agent.

Layer 1: The Web3 Predictive Data Layer

ChainAware.ai’s engine runs 24/7 across 8 blockchains – Ethereum, BNB Smart Chain, Base, Polygon, Haqq, Solana, TON, and Tron – ingesting on-chain events in real time. Every swap, stake, borrow, bridge, NFT purchase, and contract interaction is captured and fed into predictive AI models.

These models produce a Web3 Persona for every wallet: a continuously updated behavioral fingerprint that goes far beyond raw transaction history. The Persona captures risk profile, protocol affinity, experience level, behavioral category (DeFi lender, NFT trader, bridge user, etc.), and predicted next actions – all expressed as structured, queryable data.

Layer 2: The MCP Endpoint

The MCP endpoint exposes the Web3 Predictive Data Layer through the standardized Model Context Protocol interface. When your AI agent sends a wallet address to the endpoint, it receives back a complete, schema-validated behavioral context payload – ready for immediate injection into the agent’s decision logic or system prompt.

The endpoint is designed for low latency and high availability. Responses are typically returned in under 200ms, making real-time personalization practical even in interactive Dapp environments where user experience depends on instant feedback.

Layer 3: Your AI Agent

Your agent – whether it’s built on GPT-4, Claude, Llama, or any other LLM framework – receives the behavioral context payload and uses it to make better decisions. The integration is framework-agnostic: if your agent supports MCP (and most modern frameworks do), you connect once and gain access to the full data layer.

According to Anthropic’s MCP documentation, the protocol is designed specifically to eliminate the M×N integration problem – where M agents each need custom integrations with N data sources. MCP reduces this to M+N, making it dramatically more scalable.

The Data Payload: What Your Agent Receives

When your agent queries the Behavioral Prediction MCP with a wallet address, the response payload includes the following structured data:

Behavioral Categories

High-level descriptors that classify the wallet’s primary on-chain behavior patterns: DeFi Lender, Active Trader, NFT Collector, Governance Participant, Bridge User, New Wallet, and more. These categories map directly to personalization segments.

Prediction Scores

Numeric probability scores for the wallet’s most likely next actions: probability of staking (0-1), probability of borrowing, probability of trading, probability of bridging to another chain, and more. Your agent can use these scores to surface the most relevant product or content at the right moment.

Wallet Rank

A unified reputation score derived from the wallet’s full behavioral history across all supported chains. Wallet Rank is extremely difficult to game – it’s based on genuine on-chain activity, not social metrics. It can be used as a quality gate, a personalization tier, or a basis for differential product offerings.

Risk & Fraud Score

A fraud probability score calculated by ChainAware.ai’s Predictive Fraud Detector, which achieves 98% accuracy on Ethereum and 96% on BNB Smart Chain. Your agent can use this score to flag suspicious sessions, require additional verification, or adjust feature access in real time – without any separate fraud detection integration.

Credit Score

A borrowing-specific reputation score for wallets, ideal for DeFi lending protocols. Wallets with high Credit Scores can be automatically offered better loan terms – lower collateral, higher limits, better rates. Already deployed in production at SmartCredit.io. Read the full outcome in our SmartCredit.io conversion case study.

Protocol Usage History

Which protocols the wallet has interacted with, how recently, and how frequently. This allows your agent to reference the user’s actual experience – “I see you’ve been using Aave” – creating interactions that feel genuinely personalized rather than generic.

Use Cases Across DeFi, GameFi, NFT & Support

The Behavioral Prediction MCP is not a single-use tool – it’s a behavioral intelligence layer that unlocks dozens of use cases across every major Web3 vertical. Here are the highest-impact applications.

DeFi Lending: Risk-Adjusted Personalization

A lending protocol integrated with the MCP instantly knows whether a connecting wallet is a creditworthy borrower, a first-timer, or a high-risk address. The AI agent can then:

• Offer the high-credit wallet a pre-approved loan at preferential rates – automatically
• Guide the first-timer through a conservative onboarding flow with educational content
• Flag the high-risk wallet for additional verification before allowing large positions

This is not hypothetical – it’s live in production at SmartCredit.io. The result is measurably higher conversion among creditworthy borrowers and lower default rates across the loan book.

DEX & Trading: Interface Personalization

Trading platforms that integrate the MCP can dynamically adapt their interface based on each wallet’s trading history:

• High-frequency traders see advanced order types, leverage tools, and analytics dashboards
• Passive holders see yield opportunities, staking pools, and conservative allocation suggestions
• New wallets see simplified onboarding flows with educational tooltips

This mirrors how Amazon and Netflix personalize their interfaces – but applied to pseudonymous wallet identities, with no cookies or logins required.

GameFi: Dynamic Difficulty & Reward Tuning

GameFi platforms can use wallet behavioral data to personalize the game experience itself. A player whose on-chain history shows high risk tolerance gets more challenging content and higher-variance rewards. A conservative wallet gets a more structured progression. In-game economy events can be targeted to wallets predicted to make purchases in the next 48 hours – dramatically improving in-game conversion.

According to Harvard Business Review’s research on AI-driven customer experience, real-time behavioral context is the single most impactful variable in AI-powered personalization outcomes. GameFi is no exception.

NFT Marketplaces: Discovery Personalization

An NFT marketplace integrated with the MCP can surface collections most likely to match each wallet’s past buying patterns, price range, and category preferences. Instead of a generic trending feed, every user sees a personalized discovery page – collections they’re statistically likely to engage with. This reduces bounce rate and significantly increases listing-to-purchase conversion.

AI Support Agents: Context-Aware Assistance

A Web3 project’s AI support agent normally knows nothing about the user asking for help. With the Behavioral Prediction MCP, it instantly knows whether the user is a veteran DeFi participant or a newcomer, which protocols they use, what their risk profile looks like, and what they’re most likely trying to accomplish. The result is support that feels like a knowledgeable advisor, not a FAQ bot.

We explored this vertical in depth in our piece on 5 ways Prediction MCP will turbocharge your DeFi platform.

Personalized Marketing Campaigns

Instead of blanket email or in-app campaigns, the MCP enables surgical targeting: send a borrowing offer only to wallets predicted to borrow in the next 24 hours. Send a staking promotion only to wallets with idle assets and high staking probability scores. This level of precision reduces acquisition costs dramatically while improving campaign ROI.

For a full breakdown of how this changes crypto marketing strategy, see our guide on Web3 marketing strategy and our analysis of why influencer marketing is failing in Web3.

Step-by-Step Integration Guide

Getting started with the Behavioral Prediction MCP is designed to take minutes, not weeks. Here’s the practical path.

Step 1: Review the API Documentation

Start at swagger.chainaware.ai for the full API reference. The MCP endpoint is documented with request/response schemas, authentication details, supported chains, and example payloads. Familiarize yourself with the Web3 Persona response structure before writing any integration code.

Step 2: Test with the Free Wallet Auditor

Before writing a single line of code, use the free Wallet Auditor to inspect behavioral profiles for several wallet addresses relevant to your use case. This lets you validate the data quality and understand which fields matter most for your personalization logic.

Step 3: Connect to the MCP Endpoint

Configure your AI agent or LLM framework to connect to the ChainAware.ai MCP endpoint. Pass your API key in the request headers and the target wallet address in the request body. The endpoint returns the full Web3 Persona payload in a structured JSON format ready for immediate use.

Step 4: Define Your Personalization Mappings

Map behavioral signals to agent actions. Keep it explicit and testable:

• If predicted_stake_probability > 0.7 → surface staking products prominently
• If wallet_rank > 75th_percentile → unlock premium features or better terms
• If fraud_score > 0.6 → require additional verification before high-value actions
• If behavioral_category == "new_wallet" → trigger onboarding flow
• If credit_score > 80 → offer preferential borrowing conditions automatically

Step 5: Inject Context into Agent Prompts

Include the behavioral payload in your agent’s system prompt or context window. A simple injection pattern looks like: “The user connecting has Wallet Rank 82/100, is categorized as an Active DeFi Lender, and has a 78% probability of staking in the next 14 days. Tailor your response accordingly.” The LLM uses this context to generate genuinely personalized responses without any rule-based templates.

Step 6: A/B Test and Iterate

Run A/B tests comparing personalized agent flows against your existing generic experience. Measure conversion rate, session depth, and 7/14/30-day retention for each cohort. Use the results to refine your signal mappings and progressively expand the set of behavioral variables you act on.

Business Impact: Conversion, Retention & Fraud Reduction

Personalization via the Behavioral Prediction MCP doesn’t just improve UX – it drives measurable business outcomes across three dimensions.

Conversion Rate Uplift

When an AI agent surfaces the right product to the right wallet at the right moment, conversion rates increase substantially. Salesforce research shows that 73% of consumers expect companies to understand their unique needs – and disengage immediately when they don’t feel understood. In Web3, where anonymous wallets have no second-chance remarketing, first-impression conversion is everything.

DeFi platforms that segment users by behavioral category and serve each segment a tailored call-to-action consistently see higher conversion on primary actions – deposits, borrows, stakes – compared to generic funnels.

Retention and Lifetime Value

Retention in DeFi is notoriously low. Users are yield-mercenaries, constantly hunting the best rates across dozens of protocols. Personalization creates a moat: when your platform consistently surfaces opportunities that match each wallet’s specific behavior pattern, users stop hunting elsewhere. The platform becomes their default.

For a deep dive into how personalization drives retention in Web3 AI contexts, see our full guide on why personalization is the next big thing for AI agents.

Fraud Reduction as a Revenue Driver

The fraud score embedded in every MCP payload means your AI agent functions as a real-time fraud screener without any separate integration. A wallet flagged with a high fraud score can be automatically routed to additional verification, blocked from high-value transactions, or shown a restricted interface – all before any transaction occurs.

At 98% accuracy on Ethereum, this is not a marginal improvement over manual review – it’s a fundamentally different risk posture. Fraud reduction protects platform reputation, reduces regulatory exposure, and maintains the trust of legitimate high-value users. For the full technical breakdown, see our article on the ChainAware.ai fraud detection approach.

Measuring Performance: KPIs That Matter

According to Gartner’s research on AI personalization, organizations that establish clear measurement frameworks for personalization achieve 2-3x better outcomes than those that deploy personalization without structured measurement. Here are the KPIs to track for your MCP integration.

Conversion Metrics

• Wallet-to-action conversion rate – personalized vs. generic cohorts, measured on primary actions (deposit, borrow, stake, trade)
• Time-to-first-action – how quickly after wallet connection does the user complete a meaningful action?
• CTA click-through rate by behavioral segment – which Web3 Persona segments respond best to which offers?

Retention Metrics

• 7/14/30-day wallet return rate – do personalized users come back more often?
• Session depth – number of protocol interactions per session, personalized vs. generic
• Protocol stickiness score – is personalization keeping users on your platform rather than spreading to competitors?

Prediction Quality Metrics

• Behavioral forecast accuracy – how often does the MCP’s predicted next action match the wallet’s actual next action?
• Segment stability rate – how stable are behavioral categories over time, and does your agent adapt when they shift?
• Fraud score precision – what percentage of flagged wallets are confirmed as fraudulent vs. legitimate?

The Future of Agent-Native Web3

The Behavioral Prediction MCP represents something larger than a useful developer tool – it’s a preview of the architecture that Web3 is converging toward: one where AI agents are the primary interface layer between users and protocols, and where those agents have real-time access to the behavioral intelligence they need to act well.

Several trends are accelerating this future:

• MCP standardization is accelerating. As MCP becomes the dominant protocol for AI context delivery, the ecosystem of compliant agents and data providers is growing rapidly. Building on MCP today means your integration remains forward-compatible as the standard matures.
• Multi-chain user behavior is the norm. Users increasingly operate across 3, 5, or 8 chains simultaneously. Single-chain behavioral views are increasingly incomplete. ChainAware.ai’s 8-chain coverage provides a holistic view that single-chain analytics tools fundamentally cannot match.
• Regulatory requirements are converging with personalization. Knowing who your users are – their behavioral history, risk profile, and fraud score – is becoming mandatory for AML compliance, not just optional for personalization. The same MCP integration serves both purposes.
• Agent-to-agent workflows are emerging. The Behavioral Prediction MCP is uniquely positioned for the next wave: multi-agent systems where one agent queries another for behavioral context, enabling complex automated workflows with genuine user-level personalization at every step.

We explored the broader trajectory in our pieces on how AI agents are revolutionizing Web3 and real utility AI meets DeFi.

Conclusion: Context Is the Competitive Advantage

Generic AI agents are a commodity. Any team can deploy one in an afternoon. The competitive advantage in Web3 AI is not the agent – it’s the context that agent operates with. Real-time on-chain behavioral data, delivered via the Behavioral Prediction MCP, is the context layer that separates agents that guess from agents that know.

ChainAware.ai has spent years building the Web3 Predictive Data Layer that makes this possible: 14M+ wallet profiles, 1.3B+ data points, 8 chains, continuously updated. The Behavioral Prediction MCP makes all of that intelligence accessible to any AI agent or LLM through a single endpoint connection.

The wallets are talking. The behavioral signals are there. The only question is whether your AI agent is listening.

The post Prediction MCP for AI Agents: Personalize Decisions from Wallet Behavior (Complete Guide) first appeared on ChainAware.ai.