# Explorer Gateway API — Bitcoin Block List

> Explorer Gateway API — Bitcoin Block List is a paid API for AI agents from api.blockchain.info, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Returns a paginated list of recent Bitcoin blocks from the blockchain.info explorer gateway, starting from the chain tip or a specified block height.

## Facts

- Endpoint: POST https://api.blockchain.info/explorer-gateway-kt/x402/btc/blocks?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/explorer-gateway-api-bitcoin-block-list-4617feb2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_--UfsILtjMMwHarIFnJIC

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability explorer-gateway-api-bitcoin-block-list-4617feb2 -d '<json body>'
```

Example prompt: Can you pull the last 20 Bitcoin blocks from blockchain.info's explorer gateway, starting from block height 840000 and paginating downward?

## When to prefer this

Choose this endpoint when you need to enumerate or paginate through Bitcoin blocks by height using a trusted, established block explorer (blockchain.info). Prefer this over generic Bitcoin RPC nodes when you want a REST/JSON interface without running your own node, and when per-call micropayment billing via x402 is acceptable. Best for read-only exploration, auditing, and data aggregation use cases on the Bitcoin chain.

## Known failure modes

- Invalid 'after' cursor (block height out of range) — returns error or empty list
- 'limit' exceeds maximum of 50 — clamped or rejected with validation error
- Payment failure via x402 protocol — 402 Payment Required response
- Network timeout or gateway unavailability — 5xx error
- Requesting a block height beyond the current chain tip — returns empty or error

## How this service works

Paid AI-agent access to Blockchain.com Explorer API

## Output

A JSON array of Bitcoin block objects, each containing metadata such as block height, block hash, timestamp, transaction count, and miner details. Results are ordered descending by block height (newest first), capped at up to 50 blocks per call. Includes cursor information for further pagination.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": [
    "integer",
    "null"
   ],
   "format": "int64",
   "description": "Cursor for pagination — block height to start from (inclusive, descending). Omit to start from the current chain tip."
  },
  "limit": {
   "type": "integer",
   "default": 10,
   "maximum": 50,
   "minimum": 1,
   "description": "Number of blocks to return (capped at 50)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "format": "application/json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/explorer-gateway-api-bitcoin-block-list-4617feb2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockchain.info](https://www.zero.xyz/host/api.blockchain.info/llms.txt)