# Bitcoin Mining Pool Statistics (Last N Blocks)

> Bitcoin Mining Pool Statistics (Last N Blocks) is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-16).

Returns Bitcoin mining pool distribution, hashrate estimates, block rewards, fee ratios, and block intervals over the last N blocks (up to 144 ≈ 1 day).

## Facts

- Endpoint: POST https://api.vextorium.com/bitcoin-mineria-pago?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitcoin-mining-pool-statistics-last-n-blocks-d1330d99
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A6RYkUJgmJ-VWIwV4IkTZ

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 bitcoin-mining-pool-statistics-last-n-blocks-d1330d99 -d '<json body>'
```

Example prompt: Show me the Bitcoin mining pool distribution for the last 144 blocks — I want to know each pool's share, estimated hashrate, and how much of the block reward is coming from transaction fees versus the subsidy.

## When to prefer this

Use this endpoint when you need current Bitcoin mining pool statistics derived from on-chain block data rather than self-reported miner data — ideal for real-time hashrate estimation, fee market monitoring, and pool dominance tracking over windows up to ~24 hours (144 blocks). Prefer over static or delayed data sources when you need up-to-the-minute pool distribution.

## Known failure modes

- bloques value outside 1–144 range returns error or empty result
- Bitcoin node data temporarily unavailable causes timeout or null fields
- Very small block counts (e.g. 1-2) may yield unreliable pool share estimates
- Network connectivity issues to Bitcoin data source return null across most fields

## How this service works

Bitcoin mining over the last N blocks (max 144, ~1 day): blocks per pool (Foundry, AntPool, ViaBTC, F2Pool...) with share and estimated hashrate, average block reward (subsidy + fees), fees as % of reward and average block interval.

## Output

Returns a JSON object with: block height range analyzed, number of blocks analyzed, per-pool breakdown (pool name, blocks mined, share %, last block height, estimated hashrate in EH/s), average block subsidy in BTC, average fees in BTC, average total reward in BTC, fees as % of reward, average block interval in minutes, and estimated total network hashrate in EH/s.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bloques": {
   "type": "integer",
   "description": "10-144"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bitcoin-mining-pool-statistics-last-n-blocks-d1330d99/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)