Docs
Wallet surface
https://api.btcintel.io/api speaks the de-facto explorer REST dialect that wallet libraries and tooling already understand — point a client that expects that dialect at this base URL and it works. It is served by vigia, btcintel’s chain index.
Rollout status: vigia is completing its initial sync of the chain. Until it reaches the node tip, /api/* answers 502 — an honest “not serving yet”, never partial data. /v1 is unaffected. This notice disappears when the cut-over completes.
Core endpoints
| GET | Returns |
|---|---|
/api/blocks/tip/height | Tip height (plain text) |
/api/blocks/tip/hash | Tip hash (plain text) |
/api/block/{hash} | Block header facts |
/api/block/{hash}/txids | All txids in the block |
/api/block-height/{height} | Block hash at height (plain text) |
/api/tx/{txid} | Transaction with prevouts |
/api/tx/{txid}/status | Confirmation status |
/api/tx/{txid}/outspends | Spend status of every output |
/api/address/{address} | Funded/spent totals for chain and mempool |
/api/address/{address}/txs/chain | Confirmed history, 25 per page |
/api/address/{address}/utxo | Unspent outputs |
/api/scripthash/{hash} | Same summary by script hash |
/api/mempool | Mempool backlog stats + fee histogram |
/api/fee-estimates | Feerate targets map (blocks → sat/vB) |
Using it from BDK
// Rust: any esplora-compatible client works unchanged
let client = esplora_client::Builder::new("https://api.btcintel.io/api").build_blocking()?;
let height = client.get_height()?;# Sanity checks from a shell
curl -s https://api.btcintel.io/api/blocks/tip/height
curl -s https://api.btcintel.io/api/fee-estimates | jqElectrum protocol
Desktop wallets like Sparrow prefer the Electrum server protocol over REST. vigia speaks it natively; the public listener opens after the cut-over completes and will be announced here with host, port and TLS details.
Which surface should I use?
If a library already speaks the explorer dialect, use /api and change nothing. If you want chain facts joined with annotations — labels, entities, sources with reliability — that only exists on /v1. Both surfaces share the honesty rules; hashes are canonical display order on each.