BTCintel
nodeok
mempool68,600 tx
node next1.08 sat/vB
retarget40 blocks
chainmainnet

Docs

Chain and blocks

Status, the tip, blocks by height or hash and their transactions. Facts from btcintel's own index; the node tip rides along for confirmations.

Generated from openapi.yaml (Btcintel native API 0.1.0). Every hash is canonical display order; every answer carries the index and node heights; errors use one envelope — see Semantics.

GET /v1/status

Chain, node and mempool status

MCP tool
get_status — see For agents

Response 200

Index tip, live node info, mempool summary, fee estimates.

Headers: X-Btcintel-Index-Height, X-Btcintel-Node-Height

schema
  • community object — Spec S4.1 §8: the embedded relay and the ingester. Absent when neither runs on this deployment.
    • relay object
      • url string
      • connections integer
      • write_enabled boolean
      • min_pow integer — The effective proof-of-work floor (24 while attack_mode is on).
      • attack_mode boolean
    • ingest object — One entry per public relay the ingester follows.
      • relays array of object
        • url string
        • connected boolean
        • since string | null (date-time) — The newest created_at seen.
        • events_total integer
        • last_error string | null
    • publish object — Spec S5.1 FR-8: the API write path — whether it is open (WRITES_ENABLED) and the outbound relays.
      • enabled boolean
      • queued integer — The deepest backlog among the outbound relays; each relay has its own queue and worker (codex#111).
      • dropped_total integer
      • relays array of object
        • url string
        • connected boolean
        • sent_total integer
        • failed_total integer
        • queued integer
    • signer object — The custodied signer (spec S5.6 §5): counts only. Absent when the deployment runs without one or it does not answer.
      • keys integer required — Live custodied keys.
      • clients integer required — NIP-46 apps connected to them.
      • signing boolean required — The signer signs and exports (SIGNING_ENABLED on its side).
      • bunker boolean required — The signer listens on the relay for NIP-46 requests.
  • features object — Routes a client may switch on when present (spec S3.4); a key absent here means the deployment predates the route.
    • feedback boolean — POST /v1/feedback is served; the web renders its feedback sheet.
    • sessions boolean — The NIP-98 login and the session cookie are served (spec S5.1 FR-1).
    • login_nonce boolean — GET /v1/auth/nonce is served and the login reads the nonce tag (spec S5.8); absent on a deployment that predates it.
    • writes boolean — The API write path is open: publish, delete, propose (spec S5.1 §10; on since CP3, P60).
    • accounts boolean — Sign-up and sign-in with an e-mail account, the t4 band, are served (spec S5.5 §10; ACCOUNTS_ENABLED).
    • sign_in array of string — The sign-in providers configured (spec S5.5 FR-13, phase D) while accounts are on; empty otherwise. The web renders one button per entry.
    • signing boolean — The custodied signer signs and exports (spec S5.6 §10; SIGNING_ENABLED, off until CP4).
  • intel object — Intel pipeline: active sources and the latest fetch per source (fetched_at, sha256, status, last_error).
    • sources_active integer
    • sources_total integer
    • push boolean — The push endpoint is configured.
    • scheduler boolean — The in-process fetch scheduler is running.
    • last_fetch object
  • chain string
  • tip_height integer — Index tip.
  • tip_hash string — Canonical display byte order.
  • bitcoind_height integer — Live node tip.
  • bitcoind_ok boolean
  • bitcoind object — Subset of getblockchaininfo.
  • network_hashps number
  • mempool_size integer — getmempoolinfo.size, not the mirrored sample.
  • mempool object
    • size integer
    • bytes integer
    • usage integer
    • total_fee integer — sats
    • mempoolminfee number — sat/vB
    • minrelaytxfee number — sat/vB
  • fee_estimates object — estimatesmartfee sat/vB by confirmation target ("1", "3", "6").
  • updated_at string (date-time)

Errors

  • 401 — Missing or invalid bearer (unauthorized).

Example

curl -s https://api.btcintel.io/v1/status | jq '{chain, tip_height, tip_hash}'

GET /v1/blocks

Recent blocks

Parameters

NameInTypeDescription
limitqueryinteger · ≤ 50 · default 10—
start_heightqueryintegerDefaults to the index tip.

Response 200

Blocks, newest first.

schema
array of any

Example

curl -s https://api.btcintel.io/v1/blocks | jq

GET /v1/blocks/tip/height

Index tip height

Response 200

Height the index has reached (not the node tip).

schema
  • height integer

Example

curl -s https://api.btcintel.io/v1/blocks/tip/height | jq

GET /v1/blocks/tip/hash

Index tip hash

Response 200

Canonical hash of the index tip.

schema
  • hash string — Canonical display byte order.

Example

curl -s https://api.btcintel.io/v1/blocks/tip/hash | jq

GET /v1/blocks/{id}

Block by height or canonical hash

MCP tool
get_block — see For agents

Parameters

NameInTypeDescription
id requiredpathstringHeight (decimal) or canonical block hash (64 hex).
includequerystring · one of "expired"expired to include expired and retracted claims in annotations (attributions and hop-0 stay current-only).

Response 200

Block header facts with the intel siblings.

schema

BlockDetail

Errors

  • 301 — Legacy internal-order hash; Location holds the canonical URL.
  • 400 — Malformed input (bad hex, wrong-network address, bad vout).
  • 404 — Unknown to the index and, for transactions, to the node mempool.

Example

curl -s https://api.btcintel.io/v1/blocks/968212 | jq

GET /v1/blocks/{id}/txs

Txids of a block

Parameters

NameInTypeDescription
id requiredpathstringHeight (decimal) or canonical block hash (64 hex).

Response 200

Canonical txids in block order.

schema
  • height integer
  • txids array of string

Errors

  • 301 — Legacy internal-order hash; Location holds the canonical URL.
  • 404 — Unknown to the index and, for transactions, to the node mempool.

Example

curl -s https://api.btcintel.io/v1/blocks/968212/txs | jq

GET /v1/blocks/{id}/status

Block chain-status

Parameters

NameInTypeDescription
id requiredpathstringHeight (decimal) or canonical block hash (64 hex).

Response 200

Whether the block is in the best indexed chain and its successor.

schema
  • in_best_chain boolean
  • height integer
  • hash string — Canonical display byte order.
  • next_best string — Canonical display byte order.

Errors

  • 404 — Unknown to the index and, for transactions, to the node mempool.

Example

curl -s https://api.btcintel.io/v1/blocks/968212/status | jq '{in_best_chain, height, hash}'