Skip to main content
Grouped by who is asking. Interpretation questions link into the walkthrough rather than answering twice.

​
About the product

A tool for assessing the risk of crypto wallets and transactions. It analyzes the origin of funds, identifies links to high-risk entities, and produces evidence you can archive. See the Overview.
KYC identifies the user; KYT analyzes the behavior of funds on the blockchain. KYC tells you who your customer is, KYT tells you where their crypto has been. KYT works standalone, but the pair is what makes a complete AML framework.
Bitcoin, Ethereum (ERC-20), and TRON (TRC-20), covering native assets plus USDT and USDC on Ethereum and TRON. More are on the roadmap — see Supported networks.
Crypto exchanges, neobanks and fintechs, payment gateways and PSPs, OTC desks and brokers, and any AML team screening crypto wallets. Workflows per business are in Decision playbooks.
Not yet. Address monitoring, alerts, and custom risk profiles are planned; today KYT provides on-demand checks. See Feature availability.

​
Reading results

It is a weighted composite of the funds’ exposure across entity categories, based on direct and indirect interactions with tagged entities, transaction history, and the share of assets tied to high-risk categories. High-risk exposure weighs more heavily. Details in Risk scoring.
Yes. Every result includes a per-category breakdown showing which entity types are in the fund trail and what share each accounts for, plus a Direct transfers table naming the immediate counterparties. The walkthrough shows how to use both: How to read a KYT report.
Because the score is weighted, not additive — a small high-risk share inside a large clean flow still produces a Low score. Treat any High-tier exposure as an escalation trigger anyway: see the decision matrix.
New transactions arrive and entity classifications are added continuously, so every result is a point-in-time record. This is why re-screening is a control rather than a formality.
Two different things depending on where you see it. As Owner / Type it means the address is not attributed to a known service — normal for personal wallets. As the grade it means there was not enough attributable data to classify the source of funds — treat it as no signal, not as a pass.
Yes to both. It analyzes direct (1-hop) and indirect (n-hop) relationships along the fund trail, and related addresses are grouped into clusters and analyzed as a single entity, which improves attribution accuracy.

​
Integration

Usually seconds, most under 5 via the API. While analysis runs, the API returns 404 with "No data, please try again later" — retry with a short backoff.
The API returns a 0–1 coefficient; the dashboard and PDF show a percentage. "0.34" means 34%. Multiply by 100 for display, and branch on risk_score_grade to avoid the conversion entirely. See Result fields.
Yes. The API allows 24 requests per second per key; for bulk jobs batch the requests with backoff, and contact service@dataspike.io about higher sustained limits.
Custom profiles and thresholds are planned. Today, use the built-in grades as decision gates and the raw coefficient for any finer logic on your side.

​
Data and compliance

No. KYT works exclusively with public blockchain data. Stored data covers analysis results, risk scores, aggregated on-chain analytics, reports, and audit logs. See Data handling.
Yes. Reports are timestamped, attributable, and self-contained, suitable for AML teams, internal audit, banking partners, and as supporting evidence for SAR/STR filings. Retention guidance is in Exporting reports.
No — and no screening tool does on its own. KYT supports Travel Rule workflows by identifying counterparty services one hop away; it is not a Travel Rule messaging protocol. See Compliance context.