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

Query the chain · Bitcoin data API

Bitcoin data API and data provider for the indexed chain

Most teams stitch several vendors together for Bitcoin data: one for addresses, one for metrics, one for price. This Bitcoin data API serves raw chain rows, on-chain metrics, entity labels and market history from one indexed source, over REST, SQL and dashboards.

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 ...

Choosing a Bitcoin data provider comes down to one question: can you get the on-chain data you need, in the shape your team works in, without building and maintaining the indexing yourself. BitcoinDatabase serves address and transaction history back to the 2009 genesis block as a REST API for engineers, with SQL for analysts and dashboards for everyone else over the indexed chain, which grows with every new block. Addresses, balances to the satoshi, transactions with full inputs and outputs, UTXOs, confirmations, mempool state, entity labels and historical market data all come from one indexed source.

Most blockchain data providers spread thin across dozens of chains. This one is Bitcoin-native and goes deep instead of wide, so the schema, the labels and the raw lookups are built for how Bitcoin actually works. Pricing is usage-based with no free plan, which keeps the service built for production rather than casual scraping. Everything here is informational on-chain data and analytics, not investment 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 Bitcoin data API

One source, not five

Chain data, balances, on-chain metrics, labels and market history come from one indexed platform, so you stop reconciling mismatched feeds from separate vendors.

Bitcoin-native, not multi-chain thin

Where broad providers stretch across many chains, BitcoinDatabase indexes Bitcoin deeply: UTXOs, script types, entity labels and full history are first-class, not an afterthought bolted onto a generic schema.

Raw and derived together

Read the raw ledger and the metrics built on it side by side, so you can drill from a chart straight down to the underlying addresses and transactions.

Side by side

Bitcoin data providers, as we measured them

Every row below was checked first-hand against live endpoints and public pricing pages on the date shown, not copied from a roundup. Prices and limits change without notice, so treat the date as part of the fact and re-check before you sign. Where a provider is genuinely better at something than we are, the row says so.

Provider Answers without a key Entry price Bitcoin chain rows Measured
BitcoinDatabase No Usage-based, on our pricing page Blocks, transactions, inputs, outputs and the UTXO set over REST and SQL Current
mempool.space and Blockstream Esplora Yes Free public endpoints Blocks and transactions, but no balance at a past height 10 Sep 2026
BlockCypher Yes, 3 req/sec and 100 req/hr Paid plans from $119 a month Blocks, transactions and addresses 9 Aug 2026
Google BigQuery public dataset No, needs a GCP project 1 TiB a month free, then $6.25 per TiB scanned Full chain, roughly 3 blocks behind the tip 9 Aug 2026
Bitquery No, returns 401 $39 a month personal use, $79 commercial, billed annually GraphQL across many chains 9 Aug 2026
CryptoQuant Yes, browse only $109 a month is the first tier with an API key Metrics at day resolution, not rows 16 Aug 2026
Glassnode No, returns 401 $49 a month billed annually, API not included at that tier Metrics, not rows 21 Aug 2026
CoinGlass No, returns an API key missing error $29 a month Exchange aggregates, hourly cache, two decimal places 10 Sep 2026

Two measurement notes worth carrying into your own evaluation. First, an authentication failure does not always arrive as an HTTP error: when we called the CoinGlass exchange balance endpoint with no key on 10 September 2026 the transport status was 200 and the refusal was a code field inside the body, so a client that only checks the HTTP status will parse an error object as data. Second, a missing capability does not always arrive as an error either. Passing a height parameter to an Esplora address call returns a byte-identical response to the call without it, and asking BlockCypher for an address state before block 300,000 returned every numeric field as zero rather than an error. Both failures are silent, and both will flow into a report unnoticed.

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.

  • Pull address balances, history and UTXOs
  • Fetch transactions with full inputs and outputs
  • Query blocks, confirmations and mempool state
  • Run custom SQL over the indexed chain
  • Read entity labels and historical market data
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 Bitcoin data API

Raw chain data such as addresses, transactions and UTXOs, derived on-chain metrics, entity labels, and historical market data, all from the fully-indexed chain and aligned to one timeline. No node or extra vendors needed.
Many teams use it to consolidate address data, metrics and price into one API and one consistent dataset queryable by REST, SQL and dashboards. It provides informational data only, not financial advice.
Complete indexing of the chain, data in the shape your team uses (API, SQL and dashboards), Bitcoin-native depth on UTXOs and labels, and no need to run a node yourself. BitcoinDatabase serves full address history back to the 2009 genesis block over REST, and SQL and dashboards over the indexed chain, which grows with every new block.
Multi-chain providers cover many networks but often expose Bitcoin through a generalized schema that flattens UTXOs and script detail. A Bitcoin-native provider indexes the chain on its own terms, so raw lookups, labels and history go deeper. This is data only, not financial advice.
It ranges widely because the products are not comparable. On the dates we checked, CoinGlass started at $29 a month, Bitquery at $39 for personal use and $79 for commercial, Glassnode at $49 a month billed annually with API access excluded at that tier, CryptoQuant at $109 for the first tier that includes an API key, and BlockCypher at $119. Google BigQuery charges $6.25 per TiB scanned with 1 TiB free each month.
The core set is blocks with height, hash, time and tx_count; transactions with txid, block_height, fee_btc, size and weight; outputs with txid, vout, address, value_btc, script_type, spent and price_at_creation_usd; inputs linking spending_txid to the prev_txid and prev_vout they consume; and metrics_daily for aggregated daily series. Inputs join to outputs on prev_txid and prev_vout.
No, and this catches people out. There is no PostgreSQL wire protocol here, so there is no host, port, username or password to put in a client. SQL runs as an HTTP request, POST to /v1/sql with your key as a bearer token, and the results come back as JSON. Anything that can make an HTTP call can query it.
Both, against the same indexed chain. REST endpoints suit application code doing address, transaction and balance lookups. SQL suits research and anything aggregating across the chain, and it is available from the Growth plan up. A SQL query costs more credits than a single REST lookup, so pick per job rather than per team.
That is the whole point of an indexed API. A self-hosted archival node with enough disk and bandwidth to serve queries runs somewhere around 390 to 430 dollars a month on AWS before anyone maintains it, and a bare node still cannot answer address or aggregate questions without an index on top. Querying an already-indexed copy skips both problems.
It depends on the access path. Over REST, address and transaction history reaches back to the January 2009 genesis block. SQL and dashboards run over the indexed chain, which grows with every new block, and every figure there is pinned to a block height, which is what makes a dated series reproducible months after you first ran it.
Not here, and the free options are worth knowing. We called mempool.space, Blockstream Esplora, BlockCypher and blockchain.com on 8 September 2026 and all four answered with HTTP 200 and no key. What they do not give you is a balance at a past block height, a USD value on a transaction, an entity label, or SQL. Free is the right answer for lookups and the wrong answer for reporting.
Not reliably, and the failures are silent. We tested this directly. Passing a height parameter to a Blockstream Esplora address call returns a byte-identical response to the call without it, so you get the current balance while believing you asked for a historical one. BlockCypher returned every numeric field as zero when asked for a state before block 300,000, with no error raised.
Five things. Can I pin a query to a specific block height. What precision do you return, satoshis or decimals. Can I pull a high-volume address history without paging limits that make it impractical. Do you expose the UTXO set with a spent flag, or only balances. And can I reproduce any figure you publish from the rows you give me. The last one separates a data source from a dashboard.
No, and confusing the two is the most expensive mistake in this category. A metrics provider sells you a finished number computed to a definition it chose. A data provider sells you the rows underneath. When we counted active addresses on one block ourselves we got five defensible answers spanning 2.25 times, all correct, differing only in definition. If you cannot see the rows, you cannot tell which definition you bought.
Almost never about the data, frequently about how it is counted. Every explorer we have compared agrees on balances to the satoshi. Where numbers diverge it is a definitional choice: block count versus block height differs by one because genesis is block 0, and an exchange reserve total depends entirely on whose address list is used. Treat a disagreement as a methodology question, not a correctness question.
It varies by two orders of magnitude and it is the specification people check last. The Google BigQuery public dataset runs roughly three blocks behind the tip. CoinGlass documents an hourly cache on its exchange balance endpoints for every plan including Enterprise, and CryptoQuant offers day resolution below its top tier. BitcoinDatabase indexes each block as it confirms, so a query can be pinned to the current tip or any earlier height.
Read every Bitcoin API question

Explore more

More ways to query Bitcoin with BitcoinDatabase

Best Bitcoin API

Compare the main Bitcoin API providers on data depth, price and limits.

Learn more

Bitcoin node API

JSON-RPC style access to blocks, transactions and balances, with no Bitcoin Core to run.

Learn more

Bitcoin API

Query addresses, transactions and balances across the whole indexed chain in one call.

Learn more

Query the Bitcoin blockchain with SQL

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

Learn more

Bitcoin address labels

Attach exchange, miner and service labels to addresses, so raw hashes read as entities.

Learn more

Bitcoin UTXO data

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

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