Skip to main content
One check, three surfaces: the dashboard, the AML PDF report, and the API response. The tables below are the lookup between them — useful when an analyst and a developer are looking at the same case and using different words for the same field. This page also documents what KYT covers today: supported networks and feature availability. For the interpretation of these fields in context, see How to read a KYT report.

​
Address check

indirect_payments[].risk_score_grade is the tier of that category (low / moderate / high / undefined), not the score of the check. The tier totals shown in the PDF are the sums of the categories in each tier.

​
Transaction check

Same fields as above, minus balance-related ones, plus: Transaction reports contain no balance field — a transaction has an amount, not a balance.

​
Transfer check (API only)

Isolates one sender → recipient pair inside a transaction. Useful on UTXO chains and in multi-party transactions.

​
Request parameters that change the result

When comparing two results for the same address, confirm that token and directs match. Different parameters produce legitimately different scores.

​
Statuses and response codes you will see

​
Supported networks

KYT currently supports three blockchain networks. All check types — address, transaction, and transfer — work on all supported networks. Selecting the asset
  • Dashboard: choose the Network, then the Token. Leave the token empty to screen the native asset (BTC/ETH/TRX).
  • API: set blockchain to "btc", "eth", or "trx", and token to "" (native), "USDT", or "USDC".
Network-specific behavior
  • Bitcoin (UTXO model). A single transaction can include many senders (inputs) and recipients (outputs). To score one specific flow of funds inside such a transaction, use the transfer check — for Bitcoin, only the recipient_address is required to isolate the flow.
  • Ethereum and TRON (account model). Transfer checks require both sender_address and recipient_address. Token transfers (USDT/USDC) are screened with the same endpoints — just set the token parameter.
An address is screened per network: the same entity may control addresses on several chains, and each is checked in its own network context. If an address has no transaction history on the selected network, the API returns 404 Empty address.
Additional blockchain networks are on the Dataspike roadmap. Only Bitcoin, Ethereum, and TRON are supported today — if you need another chain for your integration, tell us at service@dataspike.io so we can factor it into prioritization.

​
Feature availability

KYT capabilities ship to the API and the dashboard on their own schedules. This table is the single source of truth for what you can rely on today. Coming soon Risk profiles will let you define what your business considers risky — entity types, threshold amounts, and the acceptable share of high-risk exposure — and apply different profiles per product line or jurisdiction. Address monitoring will track subscribed addresses in the background and raise alerts when the risk score changes, new suspicious activity appears, or a risk-profile condition triggers. Further ahead, the roadmap includes additional blockchain networks and deeper integration between KYT and Dataspike’s AML Screening module.
Timelines are indicative and may change. Until a feature appears in the Available now table, don’t build production logic that depends on it — and if one of these capabilities is blocking your integration, tell us at service@dataspike.io.