# SableForge Block Info API

> SableForge Block Info API is a paid API for AI agents from sableforge.servehttp.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-12).

Fetches block data (hash, number, transaction count, timestamp) for a specific Base blockchain block, paid per-call in USDC via x402.

## Facts

- Endpoint: GET https://sableforge.servehttp.com/api/block?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sableforge-block-info-api-b85fb98e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VbefzDhy5eLafSd2W6y6g

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 sableforge-block-info-api-b85fb98e
```

Example prompt: Can you look up block number 12345678 on the Base blockchain and tell me its hash, how many transactions it had, and when it was mined?

## When to prefer this

Use this endpoint when you need lightweight, pay-per-call block metadata from the Base L2 chain without setting up an account, API key, or RPC node. Ideal for AI agents that need occasional block lookups and can settle micropayments in USDC on Base via x402.

## Known failure modes

- Block number not found or not yet mined returns an error or empty response
- Invalid block number format causes a 400-level error
- Payment failure via x402 (insufficient USDC balance) results in 402 Payment Required
- Network or upstream RPC downtime causes 500-level errors
- Missing required query parameter returns validation error

## How this service works

12 pay-per-call HTTP APIs settled in USDC on Base via x402 v2. No API keys, no accounts, no signup — $0.0005–$0.0020 per call. Includes a locally hosted 27B LLM endpoint.

## Output

Returns a JSON object containing the block hash (0x-prefixed hex string), block number (integer), transaction count (integer), and Unix timestamp for the requested Base blockchain block.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "number": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hash": "0x..",
  "number": 12345678,
  "tx_count": 120,
  "timestamp": 1790000000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sableforge-block-info-api-b85fb98e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sableforge.servehttp.com](https://www.zero.xyz/host/sableforge.servehttp.com/llms.txt)