Skip to main content
You can use KYT in two ways: interactively in the dashboard (great for compliance teams and manual reviews) or through the REST API (for automated screening inside your product). Both run the same checks and produce the same reports.

​
In the dashboard

1

Open the KYT module

Log in at dash.dataspike.io, click the grid icon next to the module name in the top-left corner, and select KYT from the dropdown. You land on the Wallet Scoring page — the main interface for running checks.
2

Run a check

Select the Network (Ethereum, Bitcoin, or TRON) and the Token — leave it empty for the native asset (ETH/BTC/TRX) or choose USDT/USDC. Paste a wallet address or a transaction TxID into the input field and click Scan. Results are processed in seconds and saved to your history.
3

Read the result

Every scan is saved to the Recently verified wallets table. Each row shows the wallet/TxID, date, check type, network, token, the risk score with a Low/Moderate/High badge, and Flags — the top risk categories detected. Open a row for the full breakdown, or see How to read a KYT report.
4

Download the PDF report

Click the download icon at the end of any row to save a full AML PDF report — including the risk score, category breakdown, and direct transfers list — for your audit trail.

​
Your first API call

1

Get your API key

In dash.dataspike.io, go to API → API Settings and click Generate. Store the key securely.
Never expose the API key in frontend or mobile code. Always proxy KYT requests through your backend.
2

Submit an address check

Every request needs the ds-api-token header and Content-Type: application/json. Use btc, eth, or trx for blockchain, and leave token empty for the native asset. Store the returned check id — you need it to fetch the result and the report.
3

Poll for the result

Analysis typically completes in under 5 seconds. While it is still in progress, the API returns 404 with "No data, please try again later" — this is normal. Retry after 2–5 seconds with exponential backoff until status is "success".
4

Act on the risk grade

Branch your logic on risk_score_grade:
  • low → auto-approve
  • moderate → queue for manual review / enhanced due diligence
  • high → block and escalate
See Risk scoring for what each grade means — and note that the raw risk_score is a 0–1 coefficient, not a percentage.
5

Download and archive the PDF report

Store the report with your customer or transaction record as evidence of the automated risk assessment.
  1. On user deposit or wallet connect → submit an address check (PUT /api/v4/kyt/checks/address).
  2. Store the returned check id alongside the user or transaction record in your database.
  3. Poll GET /api/v4/kyt/checks/address/{id} until status = "success".
  4. Branch on risk_score_grade: low → auto-approve, moderate → queue for review, high → block and alert.
  5. Download and store the PDF report linked to the check id for your audit trail.
For screening individual deposits or withdrawals, use a transaction check; for isolating one sender → recipient flow (especially on Bitcoin), use a transfer check. See How KYT works.

​
Rate limits

The KYT API enforces a limit of 24 requests per second per API key. Requests above the threshold receive 429 Too Many Requests with a Retry-After header. Use exponential backoff starting at 1 second. For bulk screening, process in batches of 20 with a 1-second pause between batches. For very high volumes, contact service@dataspike.io to discuss increased limits.

​
Common response codes

The full field mapping, response schemas, and status codes live in the Result fields reference.