BitcoinDatabase.com
How it works
Bitcoin API Block explorer API Address lookup Historical data API On-chain data Transaction API Bitcoin data API Wallet tracker On-chain metrics Rich list Address balance API Query with SQL Crypto AML API UTXO data Blockchain API Flow analysis Node API Webhook API Price API Transaction monitoring Mempool API RPC API xpub balance API See all →
Glassnode alternative Dune alternative Blockchair alternative Chainalysis alternative BlockCypher alternative Chainstack alternative Blockchain.com API alternative Mempool.space alternative CoinAPI alternative TRM Labs alternative Whale Alert alternative CoinGecko alternative CoinMarketCap alternative Blockdaemon alternative Xverse alternative BigQuery alternative Bitquery alternative TimechainIndex alternative CryptoQuant alternative Alchemy alternative QuickNode alternative Hiro alternative Amberdata alternative Elliptic alternative Merkle Science alternative Coin Metrics alternative CoinGlass alternative Crypto APIs alternative Tatum alternative NOWNodes alternative GetBlock alternative Arkham Intelligence alternative Santiment alternative Nansen alternative Allium alternative Flipside alternative SonarX alternative GoldRush alternative Scorechain alternative AMLBot alternative
Docs Pricing Blog Contact Sign in

Compliance & flows · Crypto AML API

Crypto AML API with on-chain risk signals and entity labels

The crypto AML API surfaces on-chain risk signals for Bitcoin addresses and transactions: exposure to known entity categories such as exchanges, mixers, miners or services, the fund flows connecting an address to those clusters, and label context drawn from the fully-indexed chain. It is designed as compliance tooling that supports your own analysts.

or try it below ↓

REST API · SQL · dashboards · address history from genesis

Query Console
btc
try:

Hit Run to query the Bitcoin blockchain.

Live from the chain for .

BTC

Balance trail

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Reading the chain ...

Screen an address or transaction over the API, query exposure in SQL, or review cases on a dashboard. The output is informational: data, signals and labels that your regulated compliance function weighs and decides on. It does not accuse anyone, prove identity, guarantee an outcome, or make deanonymization claims, and it is not legal or financial advice.

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

History from genesis queryable in seconds

On-chain data not financial advice

Why it works

What you get with Crypto AML API

Risk signals and exposure

See an address or transaction's exposure to entity categories such as exchanges, mixers and services, surfaced as signals for your analysts to weigh.

Flows and labels for context

Trace the fund flows linking an address to known clusters, with entity labels as informational context, never as accusations or identity claims.

Built to support your review

The API provides compliance tooling: it surfaces data and signals, while your regulated compliance function makes every decision and judgment.

What it handles

The indexed Bitcoin chain, queryable your way

Look up an address, a transaction, a UTXO, the rich list or an on-chain metric, by REST API, SQL or dashboard. The same authoritative data, reconciled block-by-block against the canonical chain, without running a node.

  • Screen addresses and transactions for exposure
  • Surface risk signals by entity category
  • Trace flows to and from known clusters
  • Attach entity labels as case context
  • Feed signals into your own review workflow
GET /v1/address/{addr} query result
200 · JSON 
{
  "address": "bc1qxy2k…l0wdv8",
  "balance_btc": 68432.10,
  "balance_usd": 4612165420,
  "tx_count": 1284,
  "unspent_outputs": 37,
  "first_seen": "2014-02-09"
}
indexed from genesis · to the satoshi ✓ reconciled block-by-block

Why BitcoinDatabase

One platform, queryable three ways

Not a raw node to sync, not an indexer to build, and not five vendors to stitch together. The fully-indexed Bitcoin blockchain, available as a REST API, as SQL, and as dashboards, on one authoritative dataset.

REST API

Typed JSON for addresses, transactions, balances, UTXOs and metrics. Drop it into apps, wallets, explorers and agents with curl, Python or any HTTP client.

SQL access

Run SQL directly against the indexed Bitcoin dataset for ad-hoc analysis, cohorts and exports, the same data the API and dashboards read from.

Compliance-first

Informational on-chain data and analytics only. Entity labels and flow tracing are framed as tooling to support a regulated team's own review, not accusations.

Good questions

Questions about Crypto AML API

On-chain risk signals, exposure to entity categories such as exchanges or mixers, fund-flow context and entity labels for an address or transaction. It is compliance tooling that surfaces data for your analysts; it does not decide outcomes.
No. It provides informational signals and labels to support a regulated team's own review. It makes no accusations, no guarantees and no deanonymization claims about individuals, and it is not legal or financial advice.
No, and any vendor that says otherwise is overselling. An API returns on-chain data and risk signals. Your obligations sit with your regulated compliance function, which sets the risk appetite, reviews the alerts, documents the decision and files where required. Treat the data as evidence for a human review, not as the review itself.
Arithmetic is exact and anyone can recompute it: balances, amounts, timestamps, and the graph of which output funded which input. Entity labels are inference, assembled from clustering heuristics and off-chain research, and different vendors legitimately disagree. Keeping the two apart in your case file is what makes a finding defensible if it is challenged.
It happens. Between 17 and 24 August 2026 roughly 12,000 unsolicited small deposits reached Kraken from a wallet that Arkham Intelligence had labeled as the sanctioned exchange HTX, and automated screening locked customer accounts that had done nothing but receive them. HTX denies sending them and the attribution is disputed.
Trace the funding path backwards from the address and check whether it touches any address on a sanctions list, then measure how many hops away that contact sits and what share of value came through it. Direct exposure and five-hop exposure are very different findings, so record the hop distance rather than a single yes or no.
Not as a product. We serve raw indexed chain data, blocks, transactions, inputs and outputs, plus clustering you can run yourself. Dedicated screening vendors invest heavily in proprietary entity attribution and genuinely beat us there. What none of them publishes is a price: Chainalysis, Elliptic, TRM Labs and Merkle Science all returned HTTP 404 on their pricing pages when checked on 29 August 2026.
The screening vendors do not say. We checked all four major ones on 29 August 2026 and every pricing page returned HTTP 404, with no pricing link anywhere on their homepages and a request-a-demo path instead. Expect an enterprise sales cycle and an annual contract. Data-layer providers, ourselves included, publish usage-based pricing you can read without a call.
Because the common-input-ownership heuristic only merges addresses that actually co-spent in a transaction you have seen. Anything that never co-spent stays separate even when the same party controls it, so a cluster is a floor on what one entity holds, not a ceiling. CoinJoin and PayJoin defeat the heuristic deliberately, which pushes the count down further.
Because one address can sit on more than one sanctions entry. In the OFAC SDN file published 23 September 2026, one Bitcoin address is listed under two separate individuals. A match that returns only the first entry hides the second party from the analyst reviewing the alert, and the case file then names one person where the list names two. Return all entries, with the list publish date, on every hit.
Enterprise, at $1,498 a month or $749 a month billed yearly, with 100 million credits. It adds GET /v1/screen/{address} at 10 credits per screening and the screening book, which takes up to 1,000 addresses per call and is rescreened automatically when OFAC publishes a new SDN list. A refused call on a lower plan costs no credits.
The newest transactions, up to about 100 confirmed ones, plus up to 30 funding transactions for the two-hop inbound check, within a 12 second budget. The answer always says how many transactions it read out of how many exist and flags a partial trace, so an exchange hot wallet with millions of transactions is never reported as fully traced. Earlier hits stay remembered in your book.
Read every Bitcoin API question

Explore more

More ways to query Bitcoin with BitcoinDatabase

Crypto transaction monitoring API

Screen Bitcoin addresses and flows for AML risk from one fully-indexed data source.

Learn more

Bitcoin dust attack detection

Dust limits per script type, dust transaction data, and the spray patterns behind address poisoning.

Learn more

Bitcoin address screening API

Screen a Bitcoin address for sanctions-list matches and exposure to labeled high-risk entities.

Learn more

Bitcoin exchange reserves

Exchange balance and reserve totals per address, with dated snapshots and the transactions behind every move.

Learn more

Bitcoin UTXO data

The full UTXO set: ages, values, script types and age distribution.

Learn more

Bitcoin address types

Script type on every input and output: legacy, P2SH, native SegWit and Taproot, counted and valued.

Learn more
See every use case See pricing Back to the Bitcoin API

Stop running a node. Just query Bitcoin.

Run your first query now and get on-chain data back by REST API, SQL or dashboard, with address history back to the genesis block over REST. Informational on-chain data only, not financial advice.

See pricing

History from genesis over REST · SQL · dashboards · addresses, transactions, UTXOs, metrics