Sanctions and Risk Labels API
Screen a list of addresses for sanctions designations and risk signals before you accept a deposit, pay out a withdrawal or trace a flow. Bitquery holds tens of thousands of sanctioned and risk-flagged addresses across Tron, Bitcoin, Ethereum, BNB Chain, Solana and more.
ProductUsing this in production? See the Address Labels API page for plans, free trial and enterprise delivery options.
What it is
Label.Type | Meaning | Example Label.Value |
|---|---|---|
sanctioned-entity | Address tied to a sanctioned person or organization. The value names the sanctioning body when known | sanctioned-by-ofac-hydra-market, sanctioned-by-ofac-lazarus-group, sanctioned-by-eu-garantex |
risk-flag | Address flagged as risky or suspicious | risk-flag, suspicious, risk-flag-tornado-cash |
tainted | Address that received funds linked to a theft or scam | tainted-stolen-funds |
no-kyc | Service that does not verify customers, and its users | no-kyc, no-kyc-fixedfloat-recipient |
Related categories live on their own pages: crime and illicit activity, mixers and frozen stablecoin addresses.
How to get it
Query the Metadata.Labels cube of the Address Labels API with the risk types:
{
Metadata {
Labels(
where: {
Address: {in: [
"0x08723392ed15743cc38513c4925f5e6be5c17243",
"123WBUDmSJv4GctdVEz6Qq6z8nXSKrJ4KX",
"0x1e985636d657b4597a95f077e4bbccce41b35519",
"0x28c6c06298d514db089934071355e5743bf21d60"
]}
Label: {Type: {in: ["sanctioned-entity", "tainted", "no-kyc"]}}
}
limitBy: {by: [Address, Chain, Label_Value], count: 1}
orderBy: {descending: RecordedAt}
) {
Address
Chain
Label {
Type
Value
}
RecordedAt
}
}
}
The first address returns Lazarus Group sanctions labels, the second returns Hydra Market sanctions labels on Bitcoin, and the third is marked tainted-stolen-funds. The exchange hot wallet at the end returns nothing for these types.
How it is derived
Bitquery's labelling pipeline compiles each label from many inputs and returns one finished result: a type, a value and the date it was recorded. Responses carry the label itself, not a per-label source reference. Where a sanctions label names the designating body, that body is part of the label value.
Fields
| Field | Meaning |
|---|---|
Address | The address you queried |
Chain | Chain the label applies to |
Label.Type | sanctioned-entity, risk-flag, tainted or no-kyc |
Label.Value | The entity or reason |
RecordedAt | When the label was added to Bitquery's label table |
Examples
Screen one address for every risk type
{
Metadata {
Labels(
where: {
Address: {is: "0x08723392ed15743cc38513c4925f5e6be5c17243"}
Label: {Type: {in: ["sanctioned-entity", "risk-flag", "tainted", "no-kyc", "hacker", "scam", "phishing", "mixer", "money-laundering"]}}
}
limitBy: {by: [Label_Type, Label_Value], count: 1}
orderBy: {descending: RecordedAt}
) {
Chain
Label {
Type
Value
}
}
}
}
Screen the counterparties of a wallet
Get a wallet's senders and receivers from the Transfers cube, send them here in batches of 100, and keep the rows that come back. Each row is a counterparty with a sanctions or risk label.
Pitfalls
- A label is a signal, not a legal finding. Use it to prioritize review. Confirm against the official list before you act on a sanctions match.
- No row is not a clearance. An address with no label has not been found risky so far. It has not been cleared.
- Screen across chains. Leave out the
Chainfilter on EVM addresses. The same address can carry a label on a different chain. risk-flagis broad. It can also sit on well-known services. ReadLabel.Valuebefore you treat it as a hit.
Get the full dataset
To screen millions of addresses offline, or to load a sanctions and risk list into your own system, buy the bulk Address Labels dataset on the Bitquery Data Store.
Frequently Asked Questions
How do I check if a crypto address is sanctioned?
Query Metadata.Labels with the address and filter Label Type to sanctioned-entity. A returned row means Bitquery holds a sanctions label for it, and Label.Value names the entity and, when known, the sanctioning body.
How many addresses can I screen in one request?
Up to 100 addresses per query. Split longer lists into batches of 100.
Does the API return a risk score?
No. It returns labels. You decide how each label type counts in your own policy. For an agent-built risk report, see the Bitquery MCP tracing tools.
Related
Ready to run this in production?
Get an API key and run these queries in minutes, or talk to us about plans and enterprise delivery.