Compare · GetBlock
GetBlock alternative with pricing and Bitcoin API compared
GetBlock sells node access on 130+ chains, billed in compute units, from $49 a month for 90 million. For raw RPC across many networks it is good value.
If Bitcoin is the business and the job is answering questions, you need SQL. We priced both on 27 September 2026.
REST API · SQL · dashboards · address history since the 2009 genesis block
BTC
Balance trail
informational on-chain data · not financial advice
GetBlock leads on breadth and throughput, shared, flat-rate and dedicated nodes on 130+ chains at up to 800 requests a second, while BitcoinDatabase indexes only Bitcoin so a balance at a block, a flow across addresses or a join over the chain is one SQL query instead of a paging loop.
Side by side
GetBlock vs BitcoinDatabase, honestly
A fair look at what each does well. Both are capable tools. Here is where they differ.
| What matters | BitcoinDatabase | GetBlock |
|---|---|---|
| What you buy | A Bitcoin data index: REST, SQL and exports | Shared, Limitless and Dedicated nodes on 130+ chains, Blockbook as an add-on |
| Entry paid plan | Developer, $49 a month, 500,000 API credits, 10 requests a second | Starter, $49 a month ($39 billed yearly), 90M compute units, 250 requests a second |
| Higher plans | Growth $199 adds SQL, Scale $799 adds bulk CSV, labels and webhooks | Growth $99, Advanced $199, Scale $349, Pro $499, Premium $699, Enterprise from $999 |
| Cost of one Bitcoin call | 1 credit for address, tx and block lookups, 5 for a SQL query | Chain multiplier 10 x method multiplier, doubled on an archive endpoint |
| Free tier | No free plan, a one-time demo query on the site | 50,000 compute units a day, 20 requests a second, 2 endpoints, resets daily |
| Bitcoin address balance and history | Built in: one year on Developer, full history on Growth and Scale | Through the Blockbook add-on over REST or WebSocket, not over JSON-RPC |
| Balance at a past block height | One SQL query over outputs and inputs, from Growth | Page Blockbook history to that height and sum it yourself |
| SQL across addresses | Yes, POST /v1/sql from Growth | Not offered; JSON-RPC, REST, Blockbook and WebSocket |
| Raw RPC, many chains, dedicated nodes | Not offered | Yes, the core product; dedicated full node from $1,000 a month, archive from $1,500 |
| Call with a bad key | HTTP 401 with a JSON error body | go.getblock.io: HTTP 404 with an empty body; go.getblock.us: 401 "Missing token-id" |
| Best suited for | Bitcoin exchanges, custodians, auditors and analysts who need numbers they can prove | Multi-chain apps that need fast node access and high request rates |
Comparison reflects general, publicly understood positioning. Capabilities change, so check each product for the latest.
Why teams pick BitcoinDatabase
The fully indexed Bitcoin blockchain, queryable by REST, SQL and dashboards
What GetBlock costs, read from its plan table
We read GetBlock's plan table in its documentation and on getblock.io/pricing on 27 September 2026. Shared node plans are sold by monthly compute units. Free gives 50,000 compute units a day, 20 requests a second and 2 endpoints, renewed daily with no carry-over. Starter is $49 a month for 90 million units and 250 requests a second. Growth is $99 for 185 million, Advanced $199 for 385 million, Scale $349 for 700 million, Pro $499 for 1 billion at 800 requests a second, and Premium $699 for 1.6 billion. Enterprise starts at $999. Yearly billing takes 20% off, so Starter is $39 and Pro $399. Plan units reset each cycle, while purchased top-ups carry over. Limitless nodes drop the unit meter for a flat fee at a fixed rate cap, and dedicated nodes start at $1,000 a month for a full node and $1,500 for an archive node.
What a Bitcoin job costs in compute units
GetBlock prices a call as chain multiplier times method multiplier times archive modifier. Its documentation lists Bitcoin at a chain multiplier of 10, and the archive modifier is 2 for any request sent to an archive endpoint, even one that does not need old state. A basic Bitcoin call is therefore 10 units, so the free tier is about 5,000 calls a day and Starter about 9 million a month. We priced a real job. On 27 September 2026 the exchange hot wallet we track, bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h, had 2,338,632 transactions and 9,527.50 BTC at block 968,856. At 1,000 transactions a page, its full history is about 2,339 calls, roughly 23,390 units at a method multiplier of 1. That fits inside half a free day, and we say so plainly. What comes back is transactions, though, not totals.
Bitcoin address data is an add-on, and the node cannot answer it
GetBlock's own Blockbook page says it directly: a Bitcoin node tracks unspent outputs but does not organize them by address, so a plain node cannot return an address balance. That matches what we have measured on Bitcoin Core. GetBlock solves it with Blockbook, the indexer Trezor maintains, sold as an add-on over REST and WebSocket, each provisioned as its own endpoint. It is not served over JSON-RPC: sending the upstream bb_getAddress style methods to a standard Bitcoin endpoint returns error -32603. Blockbook is good at one address or one xpub, with paging and block height filters. A balance for 10,000 addresses at the same height, net flow through a cluster over a window, or every output of a script type in a range is still a loop you write and reconcile. That is the step SQL removes.
A bad key looks like a bad URL
We called GetBlock's Bitcoin JSON-RPC hosts without a valid token on 27 September 2026. The main host, go.getblock.io, answered a made-up token with HTTP 404 and an empty body in 0.08 seconds, the same response as a wrong path. The US host, go.getblock.us, answered a request with no token with HTTP 401 and the plain text "Missing token-id". The legacy btc.getblock.io hostname no longer resolved. None of this is a fault, since GetBlock puts the token in the URL path, but it matters for monitoring: an expired or mistyped token in a config file shows up as not found, not as unauthorized, so alert on 404 from your node client as well as 401. BitcoinDatabase returns HTTP 401 with a JSON error body for a missing or bad key, and a spent credit pool returns 402.
Where GetBlock is the better buy
If you run a multi-chain wallet, bridge or trading system and need node access on Bitcoin, Ethereum, Solana and a hundred other networks, GetBlock is hard to beat, and nothing here replaces raw RPC. Its rates go to 800 requests a second on shared plans, its flat-rate Limitless nodes suit spiky traffic, dedicated nodes are priced in public, and the free tier is enough to prototype. BitcoinDatabase is the better fit when Bitcoin is the business and the output is a number someone will check: a balance at a period-end block, net flow through an exchange cluster over a window, fee rates your withdrawals actually paid, or a join across every output in a block range. Growth at $199 a month is where SQL starts, and Scale at $799 adds bulk CSV and Parquet exports, entity labels and webhooks.
Good questions
GetBlock vs BitcoinDatabase, answered
Explore the data
The Bitcoin data you can query here
Bitcoin node API
JSON-RPC style access to blocks, transactions and balances, with no Bitcoin Core to run.
ExploreBitcoin address balance history API
What an address held on any past date, not just what it holds now.
ExploreBitcoin address labels
Attach exchange, miner and service labels to addresses, so raw hashes read as entities.
ExploreBitcoin address lookup
Look up any Bitcoin address: balance, full history and UTXOs in one query.
ExploreMore comparisons
See how BitcoinDatabase compares
Glassnode alternative
Raw queryable Bitcoin data over REST, SQL and dashboards, not just curated charts.
vs DuneDune alternative
Bitcoin-only and fully-indexed, with a REST API too, not just cross-chain SQL.
vs BlockchairBlockchair alternative
Bitcoin-deep with every UTXO, entity labels, metrics, SQL and dashboards.
vs ChainalysisChainalysis alternative
Developer-first, self-serve on-chain data with compliance tooling to support your own review.
vs BlockCypherBlockCypher alternative
Bitcoin-native depth with SQL and dashboards, not just a multi-chain REST API.
vs ChainstackChainstack alternative
Indexed Bitcoin data over REST and SQL, not raw RPC nodes you still have to query.
vs Blockchain.comBlockchain.com API alternative
Production-grade indexed Bitcoin data over REST and SQL, not a rate-capped free explorer API.
vs Mempool.spaceMempool.space alternative
Indexed address, balance and history data over REST and SQL, alongside mempool and fees, on production plans.
vs CoinAPICoinAPI alternative
On-chain Bitcoin data: addresses, balances, UTXOs and labels, not cross-asset market prices.
vs TRM LabsTRM Labs alternative
Bitcoin-native on-chain data and screening signals over REST and SQL, not a full multi-chain investigations suite.
vs Whale AlertWhale Alert alternative
Query large bitcoin transactions on your own thresholds from the fully-indexed chain, not just a fixed real-time feed.
vs CoinGeckoCoinGecko alternative
Raw on-chain Bitcoin data over REST and SQL, not market prices across thousands of coins.
vs CoinMarketCapCoinMarketCap alternative
On-chain Bitcoin data over REST and SQL, where CoinMarketCap serves market prices.
vs BlockdaemonBlockdaemon alternative
A query-first indexed Bitcoin database over REST and SQL, not raw node RPC infrastructure.
vs XverseXverse alternative
Query indexed ordinals, inscriptions, BRC-20 and Runes data over REST and SQL, not just wallet and minting endpoints.
vs BigQueryBigQuery alternative
Balances, entity labels and fund flows already indexed, without per-terabyte scan billing.
vs BitqueryBitquery alternative
Bitcoin-only depth over REST and SQL, billed on calls rather than on points that move with query shape.
vs TimechainIndexTimechainIndex alternative
Bitcoin-only like TimechainIndex, with published pricing and a commercial REST API.
vs CryptoQuantCryptoQuant alternative
API access on the entry plan and the raw chain underneath, not day-resolution metrics.
vs AlchemyAlchemy alternative
An indexed Bitcoin database you query by address, not a Bitcoin Core JSON-RPC passthrough.
vs QuickNodeQuickNode alternative
An indexed Bitcoin database you query by address, not a managed Core node with the address-capable calls switched off.
vs HiroHiro alternative
Hiro retired its Bitcoin Layer 1 APIs. The endpoints now answer HTTP 410 Gone, and the migration link inside that answer is itself dead.
vs AmberdataAmberdata alternative
Amberdata belongs to Kaiko as of June 2026. Its pricing page loads but publishes no number, and its API answers a missing key three different ways.
vs EllipticElliptic alternative
Elliptic publishes no pricing and sells its screening API only on a negotiated contract. We measured its endpoints, and the OFAC list underneath it, on 4 September 2026.
vs Merkle ScienceMerkle Science alternative
Merkle Science publishes no pricing and gates every product behind a demo. We measured its site, its API documentation and its blockchain coverage on 6 September 2026.
vs Coin MetricsCoin Metrics alternative
Coin Metrics is now Talos and its pricing page is gone. We measured the redirects, the free community API and the exact metrics it withholds on 8 September 2026.
vs CoinGlassCoinGlass alternative
CoinGlass publishes exchange balances per wallet address, hourly and rounded, from $29 a month with no free tier. We measured its plans, its documented precision and its Bitcoin gaps on 10 September 2026.
vs Crypto APIsCrypto APIs alternative
Crypto APIs covers 35+ networks from $49 a month. For Bitcoin fee rates, balances and history, we measured where a Bitcoin-only index does the job better and where it does not.
vs TatumTatum alternative
Tatum covers 130+ blockchains from $49 a month. For Bitcoin history, balances at a past block and fee rates, we priced its plans and measured the Bitcoin side on 22 Sep 2026.
vs NOWNodesNOWNodes alternative
NOWNodes sells shared node and Blockbook access across 100+ networks from 20 euros a month. We read its price list and hit its Bitcoin endpoints on 26 Sep 2026.
vs ArkhamArkham Intelligence alternative
Arkham names wallets across seven networks and grants its API by application. We read its access terms and probed its API on 28 Sep 2026.
vs SantimentSantiment alternative
Santiment sells 1,000+ metrics across 2,800 assets over GraphQL. We read its plans and tested its Bitcoin balance query against the chain on 29 Sep 2026.
vs NansenNansen alternative
Nansen labels wallets across 38 chains, and Bitcoin is one of them. We read its API docs, credit table and pay-per-call terms on 30 Sep 2026.
vs AlliumAllium alternative
Allium sells enterprise blockchain data across dozens of chains, Bitcoin included. We read its docs, unit tables and keyless pricing on 1 Oct 2026.
vs FlipsideFlipside alternative
Flipside sold its blockchain data business to SonarX in May 2026 and its old domain now redirects to an enterprise AI product. We checked what is left on 2 Oct 2026.
vs SonarXSonarX alternative
SonarX ships Bitcoin as Snowflake shares, file dumps and Kafka streams, and turns on Bitcoin balances and REST on request. We read its Bitcoin page and checked its pricing URL on 5 Oct 2026.
vs GoldRushGoldRush alternative
GoldRush, the API formerly sold as Covalent, covers 100 plus chains and gives Bitcoin three endpoints. We read its Bitcoin docs and pricing page on 6 Oct 2026.
vs ScorechainScorechain alternative
Scorechain is a Luxembourg blockchain analytics firm covering 25 plus chains. We read its site, its QuickNode add-on docs and pricing on 7 Oct 2026.
vs AMLBotAMLBot alternative
AMLBot sells wallet checks, KYT monitoring and KYC to crypto businesses across many chains. We read its site and plan guide on 8 Oct 2026.
Query the whole Bitcoin blockchain in one place
An address in, structured on-chain data out. BitcoinDatabase serves balances, UTXOs, transactions, entity labels and fund flows, with address history back to the 2009 genesis block over REST, and SQL and dashboards over the indexed chain. No node to run.
REST + SQL + dashboards · new blocks within seconds · informational on-chain data only