One pip install. Analyzed data, not raw RPC dumps. Open source, self-hosted, zero vendor lock-in.
$ pip install satoshi-api
$ bitcoin-api
INFO Satoshi API running at http://localhost:9332
INFO Interactive docs at http://localhost:9332/docs
$ curl https://bitcoinsapi.com/api/v1/fees/recommended | jq .dataLoading live fee data...A thin REST layer between your Bitcoin Core node and your applications.
Bitcoin Core's JSON-RPC is powerful but awkward. Raw responses, no caching, no rate limiting, no input validation.
Satoshi API wraps it in a clean REST interface with typed responses, smart caching, and analyzed data.
Instead of calling estimatesmartfee five times and doing math, you get a single endpoint with human-readable recommendations in sat/vB.
It's part of a three-layer stack for Bitcoin developers:
Everything Bitcoin Core is missing as an API server.
Fee recommendations in sat/vB. Mempool congestion scores. Block weight utilization percentages. Not raw hex and BTC/kVB.
Reorg-aware TTL caching. Deep blocks cached 1 hour. Tip blocks cached 30 seconds. Fees refresh every 10 seconds. Zero stale data risk.
Four tiers with sliding-window per-minute and daily limits. Expose your API safely without worrying about abuse.
Optional API keys via X-API-Key header. SHA256 hashed storage. Tiered access control. Anonymous read access for public use.
Txids validated as 64-hex before hitting RPC. Block heights checked for bounds. RPC errors mapped to proper HTTP status codes (404, 400, 502).
Every response: { data, meta }. Every error: { error: { status, title, detail } }. Request IDs on everything. No guessing.
Pair with bitcoin-mcp to give Claude or GPT direct access to your node via MCP tool calls.
Your node, your data, your API. No third party sees your queries. No vendor lock-in. No surprise pricing changes. MIT licensed.
59 tests. Docker support. Cloudflare Tunnel deployment. Structured access logging. Graceful shutdown. Tested under load.
Anyone who runs a Bitcoin node and wants to build on top of it.
You run a node already. You want to check fees, monitor the mempool, or build a dashboard. pip install, point at your node, done.
curl localhost:9332/api/v1/mempool
# Congestion level, fee buckets,
# next-block minimum feeBuilding a wallet, payment processor, or Bitcoin app? Get fee estimates, broadcast transactions, look up UTXOs. All validated and typed.
curl -X POST /api/v1/broadcast \
-H "X-API-Key: sk_..." \
-d '{"hex": "0200000001..."}'
# Returns txid on successGive your AI assistant real-time Bitcoin data. "What are current fees?" "Analyze the latest block." Your node answers directly via MCP.
# claude desktop config
"bitcoin": {
"command": "bitcoin-mcp",
"args": ["--api-url",
"http://localhost:9332"]
}Pull block stats, mining data, and fee trends into your analytics pipeline. JSON responses, consistent format, easy to ingest.
curl localhost:9332/api/v1/mining
# Difficulty, hashrate, next
# retarget height, blocks untilThird-party APIs correlate your address lookups with your IP. Self-hosted = zero data leakage. Query your own node, keep your privacy.
Teaching Bitcoin internals? The interactive docs at /docs let students explore blocks, transactions, and the mempool with live data.
Blocks, transactions, fees, mempool, mining, network, status.
| Method | Endpoint | Description |
|---|---|---|
| GET | /health | Node reachability check |
| GET | /status | Full node status (sync, peers, disk) |
| GET | /blocks/latest | Latest block analysis |
| GET | /blocks/{height_or_hash} | Block by height or hash |
| GET | /blocks/{height}/stats | Detailed block statistics |
| GET | /tx/{txid} | Transaction analysis (fees, SegWit, Taproot) |
| GET | /tx/{txid}/raw | Raw decoded transaction |
| GET | /utxo/{txid}/{vout} | UTXO lookup (spent/unspent) |
| POST | /decode | Decode raw transaction hex |
| POST | /broadcast | Broadcast signed transaction |
| GET | /fees | Fee estimates (all targets) |
| GET | /fees/recommended | Human-readable fee recommendation |
| GET | /fees/{target} | Fee for specific confirmation target |
| GET | /mempool | Mempool analysis (congestion, fee buckets) |
| GET | /mempool/info | Raw mempool info |
| GET | /mempool/tx/{txid} | Single mempool entry |
| GET | /mining | Mining stats (difficulty, hashrate, retarget) |
| GET | /mining/nextblock | Next block template analysis |
| GET | /network | Network info (connections, relay fee) |
| GET | /network/forks | Chain tips and fork detection |
All endpoints prefixed with /api/v1. Interactive docs at /docs (Swagger UI) and /redoc.
Three lines from node to API.
# Install
pip install satoshi-api
# Configure (point at your node)
export BITCOIN_RPC_USER=your_user
export BITCOIN_RPC_PASSWORD=your_password
# Run
satoshi-api
# API at http://localhost:9332
# Docs at http://localhost:9332/docs# Create env file
echo "BITCOIN_RPC_USER=your_user" > .env
echo "BITCOIN_RPC_PASSWORD=your_password" >> .env
# Run
docker compose up -d# Generate a key for your app
python scripts/create_api_key.py --tier pro --label "my-wallet"
# Key: sk_abc123... (save this, it won't be shown again)
# Use it
curl -H "X-API-Key: sk_abc123..." localhost:9332/api/v1/mempoolserver=1 in bitcoin.conftxindex=1 recommended (required for transaction lookups by txid)Self-host for free, or use our hosted API at bitcoinsapi.com.
Enterprise needs? Get in touch for custom limits, SLAs, and dedicated instances.
You have options. Here's why Satoshi API exists.
| Feature | Satoshi API | Raw RPC | Hosted APIs |
|---|---|---|---|
| Setup time | 3 lines | Already there | Sign up + API key |
| Self-hosted | Yes | Yes | No |
| Privacy | Your node, your data | Your node | They see your queries |
| Analyzed data | Fee recs, congestion, analysis | Raw values only | Varies |
| Caching | Reorg-aware TTL | None | Varies |
| Rate limiting | Built-in, tiered | None | Yes (their limits) |
| Input validation | Before RPC call | None | Yes |
| Cost at scale | $0 (self-host) | $0 | $50-500+/mo |
| AI agent support | MCP ready | No | No |
| Vendor lock-in | None (MIT) | None | Yes |
pip install satoshi-api and start building.