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
Docs Pricing Blog Contact

Query the chain · Address labels

Bitcoin address labels and entity attribution API

A raw Bitcoin address is just a string of characters, and on its own it tells you nothing about who controls it. Bitcoin address labels close that gap: BitcoinDatabase clusters addresses that provably share ownership and attaches an informational label where the cluster maps to a known entity, such as a major exchange wallet, a mining pool, a payment processor or a well-known service. Query an address and, alongside its balance and history, you get the label we hold for it.

or try it below ↓

REST API · SQL · dashboards · indexed from genesis

Query Console
btc
try:

Hit Run to query the fully-indexed Bitcoin blockchain.

BTC

30-day trend

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Querying the indexed Bitcoin blockchain ...

The same labeled data is queryable three ways: the REST API for apps, SQL for analysts who want to join labels against flows, and dashboards for review. It is built for compliance, research and analytics teams who need to read the chain as entities rather than hashes. Labels are informational context from on-chain clustering and public attribution, not identity claims about individuals and not legal or financial advice.

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

Indexed from genesis queryable in seconds

On-chain data not financial advice

Why it works

What you get with Address labels

Entities, not just hashes

Where an address clusters to a known exchange, miner, pool or service, we attach a label so your query returns an entity name and category, not only a raw string, and your team reads the chain in plain terms.

Clustering you can join

Labels sit next to balances, transactions and fund flows on the same indexed chain, so in SQL you can group flows by entity, filter transactions touching a labeled exchange, or roll up exposure across a cluster in one query.

Informational, not accusatory

Attribution is framed as on-chain context to support your own review, never an identity claim about a person or a guarantee. It surfaces signals; your compliance or research process makes the decisions.

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.

  • Return exchange, miner, pool and service labels
  • Group fund flows by labeled entity in SQL
  • Filter transactions touching known clusters
  • Enrich address lookups with attribution context
  • Label a whole address list in one query, not one call per address
  • Join labels to balances and flows without a second dataset
  • Feed labeled data into AML and research workflows
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 Address labels

Bitcoin address labels are informational tags that map an address, or a cluster of addresses under shared control, to a known entity such as an exchange, mining pool or payment service. BitcoinDatabase derives them from on-chain clustering and public attribution and returns them alongside balances and history.
No. Labels attribute an address to an entity or service based on on-chain behavior and public information, such as a wallet belonging to a known exchange. They are informational context to support your own review, not identity claims about individuals, and this is data only, not legal or financial advice.
Pass the whole list in one query rather than calling per address. In SQL you filter the labels against an array of addresses and get back one row per match with its tag and entity; over the REST API you post the list and receive the same shape. Labeling ten thousand addresses is one request, not ten thousand.
Yes. BitcoinDatabase exposes labels as a queryable table on the same indexed chain as balances, transactions and flows, so you can select tag, entity and address for a list of addresses and join the result straight to on-chain activity in one statement, with no separate dataset to import and keep in sync.
No. The public crypto_bitcoin dataset holds blocks, transactions, inputs and outputs, which is raw chain data with no exchange, mining pool or service attribution. Analysts usually join a third-party labels table alongside it, inheriting that provider's refresh schedule and labeling decisions. See the BigQuery comparison for how the two approaches differ.
Read every Bitcoin API question

Explore more

More ways to query Bitcoin with BitcoinDatabase

Query the Bitcoin blockchain with SQL

Write plain SQL against the whole indexed chain, no node, no ETL.

Learn more

Bitcoin mining pool data

Coinbase transactions, payout addresses and block share, so you can compute pool distribution yourself.

Learn more

Bulk Bitcoin address balance checker

Check thousands of addresses in one pass, not twenty at a time.

Learn more

Bitcoin block explorer API

Power an explorer with blocks, transactions and addresses, no node to maintain.

Learn more

Bitcoin Network Stats API

Query hashrate, difficulty, block times and network health from the indexed chain.

Learn more

On-chain metrics

Active addresses, realized cap, SOPR, HODL waves and exchange flows.

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, indexed from the genesis block. Informational on-chain data only, not financial advice.

See pricing

Indexed from genesis · REST · SQL · dashboards · addresses, transactions, UTXOs, metrics