Supported networks
AmlBridge screens addresses and transactions across 24 blockchain networks and token standards — from Bitcoin and Ethereum to TON, Cardano and Polkadot. The code from the "API code" column goes into the chain field when creating a check; the same list is returned by GET /v1/chains. The support level determines how deep the analysis goes.
| Network | API code | Support |
|---|---|---|
BTC | Full | |
ERC20 | Full | |
TRC20 | Full | |
BEP20 | Full | |
SOL | Full | |
POL | Full | |
ARBITRUM | Full | |
OPTIMISM | Full | |
| BAS Base | BASE | Full |
LTC | Full | |
BCHA | Full | |
ETC | Full | |
XRP | Full | |
XLM | Full | |
ADA | Full | |
AVAX | Limited | |
DOT | Limited | |
TON | Limited | |
NEAR | Limited | |
DOGE | Limited | |
ZEC | Limited | |
BCHSV | Limited | |
XTZ | Limited | |
ALGO | Limited |
What the support level means
Full support — address clustering and risk propagation across links are available. This gives the most accurate score, and the result is usually ready immediately.
Limited support — clustering and risk propagation are unavailable. A risk score is only returned if the counterparty belongs to a known entity, and the result requires an extra request, so it takes longer.
Which network code should I pass to the API?
The value from the "API code" column — for example ERC20 for Ethereum, POL for Polygon, BCHA for Bitcoin Cash. GET /v1/chains always returns the current list.
Are tokens screened, not just native coins?
Yes. Token standards have their own codes: ERC20 for Ethereum tokens, TRC20 for Tron, BEP20 for BNB Smart Chain.
Will new networks be added?
The list grows along with the provider. New networks appear without any change on your side — just pass the new code in the chain field.