Skip to content

Wallet Intelligence (KYW)

Classify a wallet, interpret confidence, and choose the next transaction workflow.

Start with KYW to identify whether a wallet is custodial, non-custodial, or unknown, then use the result to choose the next transaction workflow. Apply your policy's confidence thresholds and use your own tools or customer information when further evidence is needed.

Endpoint

Call the endpoint from your backend with the wallet's blockchain and address:

curl --location 'https://api-dev.cryptoswift.eu/kyw/Ethereum/0x742d35cc6634c0532925a3b844bc454e4438f44e' \
  --header "X-Api-Key: $API_KEY"
Always double-check you are using the correct environment when integrating. Using the wrong base URL or API key will result in authentication errors.

Use the name returned by the List blockchains endpoint (Sandbox). Coverage depth varies by blockchain. An invalid address/blockchain combination returns a validation error; an unclassified wallet returns HTTP 200 with walletType: "UNKNOWN".

Choose the next step

ResultHow to use it
CUSTODIALContinue with counterparty identification and Travel Rule messaging.
NON_CUSTODIALApply your self-hosted wallet policy, including wallet verification when proof of customer control is required.
UNKNOWNAsk for more information or route to review according to your policy.

Apply the confidence threshold required by your policy. A wallet type with insufficient confidence should prompt more evidence or review, rather than automatically selecting a transfer path. For incoming deposits, combine KYW with the available Travel Rule data and your deposit-review rules.

KYW classification, classification confidence, and wallet risk are separate signals. isVerified describes the classification evidence; it does not establish that the customer in your current session controls that wallet.

Optional agentic signals

agenticBehaviour independently describes registered-agent attribution or behavioral automation. It does not change walletType and is not a substitute for custody classification or ownership proof. See detection mechanics and response fields for details.

Use heuristicOnly=true only when you specifically want behavioral-only analysis. It skips the other classification and registry lookup stages.

Save the result

Keep the response's id or auditLogId with your internal transaction decision, along with the classification, confidence, attribution, and any agentic signals you used. Retrieve KYW history to inspect the saved evidence later.

Each new KYW check consumes one credit and does not require you to activate an external KYT provider. See Credit usage.

Next steps