BitcoinDatabase.com

Compare · Amberdata

Amberdata alternative for Bitcoin on-chain data

Amberdata is an institutional multi-chain data platform, and since June 2026 it belongs to Kaiko. If you are re-evaluating that stack for Bitcoin work, here is what we measured on 3 September 2026.

Every figure below came from calling Amberdata ourselves, without a key.

REST API · SQL · dashboards · address history since the 2009 genesis block

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

Amberdata sells breadth to institutions: derivatives analytics, market data, DeFi and wallet intelligence across many chains, priced by quote. BitcoinDatabase sells depth on one chain: Bitcoin address, balance and history lookups back to the genesis block, plus SQL over the indexed chain, on a published plan you can start today without a sales call.

Side by side

Amberdata vs BitcoinDatabase, honestly

A fair look at what each does well. Both are capable tools. Here is where they differ.

What matters BitcoinDatabase Amberdata
Ownership as of September 2026 Independent, single product Acquired by Kaiko, announced 2 June 2026
Chain coverage Bitcoin only, indexed deeply Many chains plus centralized market and derivatives data
Derivatives and options analytics None, we do not cover derivatives at all A genuine strength, and the reason many desks buy it
Published price you can read Yes, plans and limits are on the pricing page No. The pricing page names Startup and Enterprise with no figures
Buy without talking to sales Yes, self serve signup Partly. A Buy Now link exists but the plan page renders no price in HTML
Auth failure shape One consistent 401 with a JSON error body Three different shapes: 401 text/plain, 403 Forbidden, 403 Missing Authentication Token
Can you smoke test a URL before you have a key Yes, a wrong path returns 404 and a valid path returns 401 No. A typo and a real route return the identical refusal
Query by Bitcoin address Yes, address is a first class key across balances and history Yes, addresses balances and transactions endpoints exist
Custom SQL over the chain Yes, on Growth plans and above Not exposed as user written SQL, the surface is REST, RPC and WebSocket
Cost basis attached to each output Yes, every output row carries price_at_creation_usd Price and chain data are separate products you join yourself
Institutional compliance posture Not a regulated benchmark administrator Stronger, and Kaiko adds regulated indices and reference rates
Best for Bitcoin research, analytics, cohort and address level questions Multi-asset desks that need derivatives, market data and DeFi in one contract

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

Amberdata is now part of Kaiko, and that changes the evaluation

On 2 June 2026 Kaiko announced it had acquired Amberdata, and Amberdata publishes the announcement on its own blog, so this is not a rumor. Kaiko had already bought the on-chain infrastructure provider Cometh, and it describes the combined company as covering more than 200 exchanges, more than 20 blockchains and more than 20,000 digital assets. Amberdata itself was founded in 2017 and built its institutional business around derivatives analytics, on-chain data and market intelligence for hedge funds, asset managers, banks and exchanges. None of that is bad news for a buyer, but it is material. Roadmaps, endpoint lifecycles, contract terms and support ownership all tend to move in the two years after a data vendor is absorbed, and product overlap between two acquired stacks usually gets resolved rather than maintained forever. If you are signing a multi-year data agreement in 2026, ask which entity you are contracting with, which of the overlapping products is the long term one, and what the deprecation notice period is. Those are ordinary questions and a good vendor will answer them.

The pricing page loads, and still tells you nothing

This is worth measuring rather than assuming, because the screening and analytics vendors we have checked mostly do not even have a pricing page. Chainalysis, Elliptic, TRM Labs and Merkle Science all returned HTTP 404 on their pricing paths when we tested them on 29 August 2026. Amberdata is better: www.amberdata.io/pricing answered HTTP 200 on 3 September 2026. What it contains is another matter. It names exactly two plans, Startup, described as discounted pricing for pre-revenue startups and development projects, and Enterprise, aimed at financial institutions and established crypto natives. Neither carries a figure, a unit, a rate limit or a credit allowance. The call to action is Tell Us Your Needs and Request a Price Quote. There is one interesting exception. A banner reads that Amberdata market data is now available to purchase online, with a Buy Now link to intelligence.amberdata.com/plans. We followed it. It returns HTTP 200, but the document is a 515 byte JavaScript shell whose entire text content is the words Amberdata Market Intelligence, with no price anywhere in the HTML. So there may well be a real self serve price behind that app, but as of 3 September 2026 it is not readable without running the client side bundle, which means it is invisible to a procurement spreadsheet, to a search engine, and to an answer engine being asked what Amberdata costs.

One missing API key, three different refusals

We called Amberdata unauthenticated from a single US machine on 3 September 2026 and the auth surface is inconsistent in a way that will cost somebody an afternoon. Requests under web3api.io/api/v2/addresses/ returned HTTP 401 with content type text/plain and a body of exactly the word unauthorized. Requests to web3api.io/api/v2/market/tickers, the spot price pair endpoint, the blockchains blocks endpoint and api.amberdata.com paths returned HTTP 403 with a JSON body of message Forbidden. Requests to web3api.io/api/v2/tokens and web3api.io/api/v2/blockchains returned HTTP 403 with a JSON body of message Missing Authentication Token, which is the stock Amazon API Gateway response. All three mean the same thing, add credentials, but a client that switches on status code and content type will handle them as three unrelated failures. Whatever wrapper you write, collapse 401 and both flavors of 403 into one add credentials branch and do not let a retry loop treat any of them as transient.

You cannot map the surface without a key, and we tested that

We had a hypothesis worth checking, because it would have been genuinely useful: perhaps the 401 marks a route that exists and the 403 marks one that does not, which would let you validate URLs before you buy. It is wrong, and we would rather publish the failed test than a tidy claim. We requested the real balances latest endpoint and a deliberate typo of it, balances latestXX, for the same address. Both returned an identical HTTP 401 text/plain unauthorized. Then we requested a nonsense path, api/v2/nonsense-path-xyz, and a plausible real one, api/v2/tokens. Both returned an identical HTTP 403 Missing Authentication Token. The refusal is keyed on the URL prefix, not on whether the route is deployed. The practical consequence is simple and worth budgeting for: with Amberdata you cannot smoke test an endpoint path before you have credentials, and your integration cannot infer from a status code that it has the URL right. Add to that the fact that docs.amberdata.io returns HTTP 200 for every path we tried, including one we invented, because it is a single page application, so a 200 from the docs host is not evidence that a documented endpoint exists either. Plan on validating the whole path list during a trial rather than in advance.

Where Amberdata is the better buy, plainly

We would rather you pick correctly than pick us. If your questions span crypto derivatives, options surfaces, order book liquidity, DeFi lending protocols or dozens of chains, Amberdata is built for that and we are not. We cover exactly one chain and we have no derivatives data at all. If you need regulated reference rates, indices or benchmarks for a fund NAV or a structured product, Kaiko is a regulated benchmark administrator and that matters legally in a way that a research API does not. If you are a bank or an asset manager whose procurement process expects a named account team, an SLA and an annual contract, that is a normal way to buy and Amberdata serves it well. Where we are the better fit is narrower and deeper. If your question starts with a Bitcoin address, a cohort of addresses, a balance at a past height, a UTXO age distribution or a metric you want to rebuild and audit line by line, you want one chain indexed properly, SQL access, and a price already attached to each output rather than a separate market data product to join against. That is what we built, and you can start on it today without a call.

Good questions

Amberdata vs BitcoinDatabase, answered

Yes. Kaiko announced the acquisition of Amberdata on 2 June 2026, and Amberdata carries the announcement on its own blog. Kaiko had separately acquired the on-chain data infrastructure provider Cometh, and describes the combined business as covering more than 200 exchanges, more than 20 blockchains and more than 20,000 digital assets.
There is no published figure. On 3 September 2026 the Amberdata pricing page returned HTTP 200 and named two plans, Startup and Enterprise, with no prices, no rate limits and no credit allowances. The call to action is a price quote request. A Buy Now link points to a plans app that loads as a JavaScript shell with no price in the HTML.
Not one we could find or reach. Every unauthenticated Bitcoin and market request we sent on 3 September 2026 was refused, returning HTTP 401 or HTTP 403 depending on the path prefix. Amberdata does advertise a free signup for its separate derivatives analytics product, which is a different thing from open API access to chain data.
Because the gateway refuses unauthenticated requests, and it does so in three different shapes. Address paths return HTTP 401 as plain text reading unauthorized. Market and blockchain paths return HTTP 403 with a JSON body of Forbidden. A few paths return HTTP 403 with Missing Authentication Token, the stock Amazon API Gateway message. All three mean add credentials.
No, and we tested it specifically. A real balances endpoint and a deliberate typo of the same path both returned an identical 401. A nonsense path and a plausible real path both returned an identical 403. The refusal depends on the URL prefix rather than on whether the route is deployed, so status codes cannot validate a path list before you buy.
Yes. Amberdata added Bitcoin alongside its multi-chain coverage and exposes it over REST, WebSocket and RPC, with UTXO datasets and address level balances and transactions endpoints. Its by-blockchain metrics coverage includes Bitcoin, Bitcoin Cash, Ethereum, Litecoin and Polygon. Bitcoin is one chain among many there rather than the whole product.
It depends on the question you ask most. For derivatives, options and multi-chain market data there is no like for like cheaper swap, and Kaiko now owns the strongest version of that. For Bitcoin address, balance, history, cohort and metric work, a single chain indexer with SQL access is a better shape, which is what BitcoinDatabase is, and CryptoQuant or Glassnode are the closest metric-first alternatives.
It should change your questions rather than your answer. Ask which legal entity you are contracting with, which of the two overlapping product lines is the long term one, what the deprecation notice period is for endpoints you depend on, and whether support ownership is moving. Vendors handle consolidation well or badly, and the contract is where you find out which.
No. BitcoinDatabase provides informational on-chain data and analytics only. It is not investment, financial or legal advice, and nothing here is a signal or guarantee. Pricing and product facts about other vendors were measured on the dates stated and can change without notice, so verify before you sign.

Explore the data

The Bitcoin data you can query here

More comparisons

See how BitcoinDatabase compares

vs Glassnode

Glassnode alternative

Raw queryable Bitcoin data over REST, SQL and dashboards, not just curated charts.

vs Blockchair

Blockchair alternative

Bitcoin-deep with every UTXO, entity labels, metrics, SQL and dashboards.

vs BlockCypher

BlockCypher alternative

Bitcoin-native depth with SQL and dashboards, not just a multi-chain REST API.

vs Mempool.space

Mempool.space alternative

Indexed address, balance and history data over REST and SQL, alongside mempool and fees, on production plans.

vs Xverse

Xverse alternative

Query indexed ordinals, inscriptions, BRC-20 and Runes data over REST and SQL, not just wallet and minting endpoints.

vs BigQuery

BigQuery alternative

Balances, entity labels and fund flows already indexed, without per-terabyte scan billing.

vs Bitquery

Bitquery alternative

Bitcoin-only depth over REST and SQL, billed on calls rather than on points that move with query shape.

vs TimechainIndex

TimechainIndex alternative

Bitcoin-only like TimechainIndex, with published pricing and a commercial REST API.

vs CryptoQuant

CryptoQuant alternative

API access on the entry plan and the raw chain underneath, not day-resolution metrics.

vs Alchemy

Alchemy alternative

An indexed Bitcoin database you query by address, not a Bitcoin Core JSON-RPC passthrough.

vs QuickNode

QuickNode alternative

An indexed Bitcoin database you query by address, not a managed Core node with the address-capable calls switched off.

vs Hiro

Hiro 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 Elliptic

Elliptic 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 Science

Merkle 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 Metrics

Coin 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 CoinGlass

CoinGlass 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 APIs

Crypto 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 Tatum

Tatum 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 NOWNodes

NOWNodes 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 GetBlock

GetBlock alternative

GetBlock sells shared nodes on 130+ chains, priced in compute units, from $49 a month. We read its plan table and CU rules and probed its Bitcoin endpoints on 27 Sep 2026.

vs Arkham

Arkham 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 Santiment

Santiment 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 Nansen

Nansen 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 Allium

Allium 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 Flipside

Flipside 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 SonarX

SonarX 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 GoldRush

GoldRush 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 Scorechain

Scorechain 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 AMLBot

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

See pricing

REST + SQL + dashboards · new blocks within seconds · informational on-chain data only