How KYW detection works
Understand custody signals, heuristic-only checks, and independent agentic attribution.
Use these details when you need to explain a classification or configure a specialized check. For the request and routing sequence, start with KYW integration.
Heuristic-only requests
Add ?heuristicOnly=true to a new KYW request to skip verified-wallet, platform-wallet, partner-network, analytics entity lookup, and ERC-8004 registry lookup stages and run only behavioral heuristics. This changes the evidence used for the check; it does not turn the result into verified ownership proof.
How Classification Works
KYW evaluates the wallet through several signal layers:
- Completed self-hosted wallet verifications. A previous verified self-hosted wallet match is the strongest signal and classifies the wallet as
NON_CUSTODIAL. - Wallets registered by CryptoSwift platform tenants. A tenant wallet match can identify a custodial counterparty or another known platform entity.
- Partner-network attribution. When available, network data can connect a wallet to a known entity.
- Blockchain analytics. When enabled, analytics can identify entity names, entity types, risk scores, and wallet type signals.
- Known self-hosted wallet apps. Some resolved entities are wallet applications rather than custodians, so KYW classifies them as
NON_CUSTODIAL. - Behavioral heuristics. If no owner or entity is resolved, KYW analyzes wallet behavior and returns the best available classification with a confidence score.
Every response is persisted as an AML Check history record. The id and auditLogId refer to that stored record.
How Agentic Detection Works
Agentic detection is returned independently from wallet classification. walletType describes custody, while agenticBehaviour describes deterministic agent attribution or observed automation. Some transaction patterns can contribute evidence to both analyses, but the scores and attribution fields remain separate. For example, a wallet can be NON_CUSTODIAL and agentic, or CUSTODIAL with no agentic behavior detected.
ERC-8004 registry lookup
For supported networks, KYW checks ERC-8004 registries for an exact match between the requested wallet address and network. A related owner or controller address does not verify the requested wallet as an agent; the wallet itself must be registered.
An exact match returns:
detected: trueconfidenceScore: 100confidence: "HIGH"isVerified: trueattributionReasonCode: "DETECTED_VIA_ERC8004"
ERC-8004 attribution takes precedence if both registry attribution and behavioral analysis detect the wallet. When there is no verified registry attribution, agenticBehaviour reflects the available behavioral analysis.
Supported networks: Ethereum, Base, Arbitrum, Polygon, Optimism, BNB Smart Chain, Avalanche, Linea, Scroll, Celo, Gnosis, Mantle, Soneium, XLayer, Abstract, MegaETH, Monad, GOAT Network, Metis, SKALE, and Taiko.
Behavioral automation analysis
When transaction-history coverage is available, KYW evaluates a combination of automation signals:
- high transaction frequency
- activity distributed across most hours of the day
- repetitive destination or contract-interaction patterns
- rapid outgoing transactions after incoming transfers
- repeated sweeping to a dominant destination
- highly regular transaction timing
Behavioral signals are additive. A meaningful combined score is required before detected becomes true. Behavioral attribution is capped below 100 and always returns isVerified: false, because automation can represent VASP infrastructure, trading bots, treasury or payment automation, AI agents, or other software-controlled wallets.
Behavioral transaction analysis currently has coverage for Bitcoin, Ethereum, Polygon, BNB Smart Chain, Avalanche, Arbitrum, Base, Optimism, and Solana. If transaction data is unavailable or the evidence is below the detection threshold, KYW returns the explicit no-detection object shown below rather than treating the wallet as a verified non-agent.
{
"detected": false,
"confidenceScore": 0,
"confidence": "LOW",
"isVerified": false,
"attributionReason": null,
"attributionReasonCode": null
}