# Base Block Data Fetcher

> Base Block Data Fetcher is a paid API for AI agents from defi-shield-hazel.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Fetches parsed block data from the Base blockchain including gas utilization metrics and block timing information

## Facts

- Endpoint: POST https://defi-shield-hazel.vercel.app/api/data/block-data
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/defi-shield-hazel-vercel-app-ac33d1a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nz56KXL2Def0j0p7iJWm6

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 defi-shield-hazel-vercel-app-ac33d1a9 -d '<json body>'
```

Example prompt: Pull the parsed block data for Base block 20000000, including gas utilization percentage and block timing — I want to see how congested the network was at that point.

## When to prefer this

Use this endpoint when you need structured, parsed block-level data from the Base L2 network, particularly when gas utilization and block timing are important. Prefer this over raw RPC calls when you want pre-parsed data without handling raw hex values. Useful for gas estimation context, network congestion analysis, or DeFi timing decisions on Base.

## Known failure modes

- Invalid or non-existent block number returns an error response
- Block data unavailable due to RPC node issues
- Malformed request body returns 400 error
- Payment failure or insufficient USDC balance returns 402
- Rate limiting if too many requests are made in quick succession

## Output

Returns structured block data from the Base blockchain including gas utilization (used gas vs gas limit), block timing (timestamp, time since previous block), transaction count, block number, miner/validator details, and other parsed block fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "bodyType",
    "body",
    "method"
   ],
   "properties": {
    "body": {
     "properties": {
      "block_number": {
       "type": "number",
       "description": "Block number to fetch data for"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/defi-shield-hazel-vercel-app-ac33d1a9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from defi-shield-hazel.vercel.app](https://www.zero.xyz/host/defi-shield-hazel.vercel.app/llms.txt)