Live fee rates and send-or-wait verdicts. Updated every 30 seconds.
Fetching latest fee data from Bitcoin Core node...
Current fee rates for different confirmation speeds.
| Priority | Fee Rate | Est. Cost (2-in/2-out) | Est. USD |
|---|---|---|---|
| High Priority (next block) | -- sat/vB | -- sats | -- |
| Medium (~6 blocks) | -- sat/vB | -- sats | -- |
| Economy (~24 blocks) | -- sat/vB | -- sats | -- |
Current state of the Bitcoin transaction queue.
Standard transaction (2 inputs, 2 outputs): 141 vBytes
All the data on this page is available via the free Satoshi API.
# Get the send-or-wait verdict curl https://bitcoinsapi.com/api/v1/fees/landscape
# Python — 3 lines to fee intelligence
import requests
data = requests.get("https://bitcoinsapi.com/api/v1/fees/landscape").json()
print(data["data"]["recommendation"], data["data"]["reasoning"])
# For AI agents pip install bitcoin-mcp
Every 30 seconds from a Bitcoin Core node. The underlying data is cached with a 10-second TTL, so you always get near-real-time estimates without overloading the node.
Satoshi API analyzes the current fee environment, mempool congestion, and fee trends to recommend whether you should send your transaction now or wait for a cheaper window. A "send" verdict means fees are reasonable; "wait" means you could save significantly by delaying.
It compares the current next-block (high priority) fee rate to the economy (low priority) fee rate. For example, if the next-block fee is 20 sat/vB and the economy fee is 5 sat/vB, waiting saves 75%.
Yes. All fee data shown on this page is available via the free Satoshi API. Use GET /api/v1/fees/landscape for the send-or-wait verdict, GET /api/v1/fees/recommended for fee tiers, and GET /api/v1/mempool/info for mempool status. Full documentation at bitcoinsapi.com/docs.