AML API for crypto addresses and transactions
AMLKYC API embeds wallet and transaction screening into exchanges, payment processors and compliance systems. Responses include a risk score, source-of-funds categories and exposure to sanctions, fraud, mixers and other high-risk services.
Automated AML workflows
- screen addresses before deposits or withdrawals;
- analyze a transaction hash;
- monitor incoming and outgoing transfers;
- create evidence for compliance review;
- apply custom risk thresholds.
Integration
Use the API for individual requests or batch processing. Test error handling, rate limits and manual-review rules before production rollout. Authentication, methods and response examples are available in the technical documentation.
Call sequence
Screening an address takes three calls rather than one. The address is queued, the check is started, and the result is collected under the same identifier. The split exists because analysis is not instantaneous: the start call returns immediately, while the finished report is fetched separately.
| Step | Call | What happens |
|---|---|---|
| Queue the address | PUT /api/fast-check | The address is accepted; the response carries its id |
| Start the check | GET /api/fast-check/{id}/run | Analysis begins; the call returns at once |
| Collect the result | GET /api/fast-check/{id} | Risk score and the breakdown behind it |
| List previous checks | GET /api/fast-check | Everything screened so far |
Beyond screening there is address lookup — GET /api/crypto/address — and search — GET /api/crypto/search. Tracing a chain of transfers is a separate object: PUT /api/investigations.
What the response contains
The result carries a numeric score and the reasoning behind it. The score is risk.score, on a 0 to 100 scale. The reasoning is risk_detail: a list of exposure categories, each with a label such as phishing and the share it accounts for in the address history.
The score describes an address, not a person. A high value means the address has received funds from risky categories — grounds for a closer look, not a finished decision to decline.
Supported networks
The asset list is served by the API itself, so treat that as the source of truth rather than this page: coverage grows over time. As documented today, 42 asset-and-network combinations across seven networks are available.
| Network | Assets |
|---|---|
| Bitcoin | BTC |
| Ethereum | ETH, USDT, USDC, WETH, WBTC, DAI, BUSD, UNI, ENS, GRT, UST, BNB |
| TRON | USDT, USDC |
| BNB Smart Chain | BNB, WBNB, USDT, USDC, BUSD, ETH, BTCB, DOGE, SHIB, BCH |
| Polygon | MATIC, WMATIC, USDT, USDC, WETH, WBTC, DAI, AAVE, LINK, UNI, SUSHI, UST |
| Avalanche | AVAX, USDT, USDC |
| TON | Toncoin |
Decisions to make before integrating
- An access key. Issued in the dashboard; no separate application is required.
- What the score means for your process: at which value an operation goes to manual review, and at which it is declined. The threshold is a business decision — the API does not set one.
- Where responses are stored. A score describes an address at a point in time and changes as the address is used, so keep the date alongside the verdict.
- Behaviour when the service is unreachable. Screening is an outbound call, and the “no response” path belongs in the design, not in the first incident report.
Frequently asked questions
The AML API works with crypto addresses and transactions and answers where the funds came from. The KYC API works with a person and their documents and answers who the customer is. Compliance needs both; neither substitutes for the other.
Starting a check and collecting its result are separate calls precisely because analysis is not instantaneous. The start call returns immediately; the finished report is fetched afterwards using the check id.
It is a value from 0 to 100 in risk.score, accompanied by a category breakdown with labels such as phishing. It characterizes the history of an address rather than its owner, so treat it as grounds for review rather than an automatic refusal.
Bitcoin, Ethereum, TRON, BNB Smart Chain, Polygon, Avalanche and TON — 42 asset-and-network combinations as currently documented. The live list is served by the API, which is the source worth checking against.
Keys are issued in the dashboard. Terms governing API use are published as a separate document on the site, and it is the right starting point if the API will sit inside a product with external users.
Screen your first 5 addresses for free
Sign up and get 5 free AML checks. A full report with a risk score and sources of funds — in seconds.
The AMLKYC app — checks at your fingertips
Check addresses and transactions from your phone: Telegram bot, RuStore and App Store.
Have a question? Write to us
Fill in the form and we will get back to you.