Current Bitcoin network fee rates in sat/vB for next-block, half-hour, one-hour and eco…
Current Bitcoin network fee rates in sat/vB for next-block, half-hour, one-hour and economy confirmation, the estimated cost in sats of a typical payment, mempool size and total pending fees, and the latest block height. Use before sending a Bitcoin transacti…
by agent-data-tools.revmesh2074.workers.dev · discovered, not yet claimed by its owner · updated 2026-10-10
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Current Bitcoin network fee rates in sat/vB for next-block, half-hour, one-hour and economy confirmation, the estimated cost in sats of a typical payment, mempool size and total pending fees, and the latest block height. Use before sending a Bitcoin transaction or to decide whether to wait for lower fees.
Tags: bitcoin · fees · mempool · btc · onchain · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-10
{}{
"blockHeight": 970000,
"fees": {
"economy": 1,
"halfHour": 3,
"hour": 1,
"minimum": 1,
"nextBlock": 4
},
"mempool": {
"totalFeesBtc": 0.1093664,
"transactions": 83832,
"vsize": 42066150
},
"network": "bitcoin",
"typicalPaymentSats": {
"hour": 141,
"nextBlock": 564
},
"unit": "sat/vB"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/36449.jsonfor the price and payment options. - Pay. Call
GET https://agent-data-tools.revmesh2074.workers.dev/btc-fees. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.002 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.002 | 0x2074c40346ae2a90e0e4a391bcee6f16bf5277f5 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x2074c40346ae2a90e0e4a391bcee6f16bf5277f5",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "2000",
"amountUsd": 0.002,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://agent-data-tools.revmesh2074.workers.dev/btc-fees"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://agent-data-tools.revmesh2074.workers.dev/btc-fees");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://agent-data-tools.revmesh2074.workers.dev/btc-fees")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- agent-data-tools.revmesh2074.workers.dev
- Endpoint
- https://agent-data-tools.revmesh2074.workers.dev/btc-fees
- Machine-readable
/resources/36449.json