BlockCypher is a hosted, multi-chain API service that provides REST endpoints for Bitcoin, Ethereum, Litecoin, and Dogecoin. It handles infrastructure, offers address balance lookups, transaction history, and webhook notifications. Developers send queries to BlockCypher's servers, which maintain their own indexed copies of each blockchain.

Satoshi API is an open-source, self-hosted REST API that sits on top of a developer's own Bitcoin Core node. It exposes analyzed endpoints for fees, mempool, mining, and network data. All queries stay local. Satoshi API is Bitcoin-only and does not index addresses or wallet balances.

These are fundamentally different architectures solving overlapping problems. BlockCypher abstracts away node management entirely. Satoshi API assumes the developer wants to run their own node and need a clean API layer on top of it.

Feature Comparison

Feature BlockCypher Satoshi API
Hosting model SaaS (managed) Self-hosted + hosted Pro
Multi-chain BTC / ETH / LTC / DOGE Bitcoin only
Query privacy BlockCypher sees all queries Fully local, no third party
Vendor lock-in Proprietary, dependent on service Apache-2.0 licensed, no lock-in
Address balance / TX history Full address indexing UTXO + validation only
Webhooks Transaction & address webhooks SSE real-time streams
AI agent support (MCP) No Built-in MCP server
Fee analysis Basic estimates Multi-target, congestion scoring
Mempool analysis Limited Deep: distribution, age, weight
Free tier rate limit 3 req/sec, 200 req/hr Unlimited (self-hosted)
Paid plans $75 - $475/mo $19/mo hosted Pro
Source code Closed source Open source (Apache-2.0)

When to Use Each

When to use BlockCypher

  • Multi-chain support is required (ETH, LTC, DOGE alongside BTC)
  • Address balance and transaction history lookups are core to the application
  • Webhook-driven architecture is already in place
  • Running and maintaining a Bitcoin Core node is not feasible
  • Rapid prototyping across multiple blockchains

When to use Satoshi API

  • Bitcoin-focused application with no multi-chain requirements
  • Privacy-critical queries that cannot leave the local network
  • AI agent integration via MCP is needed
  • Cost-sensitive at scale (no per-request fees when self-hosted)
  • Full control over infrastructure, caching, and rate limits
  • Analyzed fee and mempool data beyond raw blockchain reads

Migration Path from BlockCypher

For developers currently using BlockCypher who want to move to a self-hosted setup, the migration depends on which endpoints are in use.

1

Set up Bitcoin Core

Install and sync a Bitcoin Core node. Satoshi API requires a fully synced node with RPC enabled. Initial sync takes 1-3 days depending on hardware.

2

Install Satoshi API

Run pip install satoshi-api and configure RPC credentials. The API starts immediately and exposes all endpoints on port 9332 by default.

3

Map BlockCypher endpoints

Block and transaction endpoints map directly. Fee estimation, mempool, and network info endpoints have Satoshi API equivalents with richer analysis. Replace webhook listeners with SSE stream consumers.

4

Address endpoints: add an indexer

If the application uses BlockCypher's address balance or transaction history endpoints, those require an additional indexing layer. Electrs or Fulcrum can provide address lookups alongside Satoshi API. This is the only non-trivial step.

5

Cut over

Point application traffic to the self-hosted instance. There are no API keys to rotate on the Satoshi API side (unless using the hosted Pro tier). Monitor via the built-in /health endpoint.

Related Pages

Compare with Mempool.space

Block explorer vs self-hosted API layer — a different kind of comparison.

Fee API Details

Multi-target fee estimation, congestion scoring, and fee landscape endpoints.

AI Agent Integration

Connect Claude, Cursor, or any MCP-compatible agent to Bitcoin data.

Self-Hosting Guide

Run Satoshi API on your own Bitcoin Core node with full privacy.