# Goldsky Feeds – Base Chain Head Block

> Goldsky Feeds – Base Chain Head Block is a paid API for AI agents from edge.goldsky.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-31).

Returns the latest (head) block number, timestamp, and lag for the Base blockchain in real time

## Facts

- Endpoint: GET https://edge.goldsky.com/data/blocks/base/head?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/goldsky-feeds-base-chain-head-block-cf3fa614
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QtTvUfryO_41mC0Y0AEF-

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 goldsky-feeds-base-chain-head-block-cf3fa614
```

Example prompt: What's the latest block number and timestamp on the Base chain right now, and how many seconds behind is the head?

## When to prefer this

Choose this endpoint when you need a lightweight, low-cost ($0.005/call) real-time lookup of the Base blockchain's current head block without running your own node or using a full RPC provider. It is ideal for monitoring scripts, agent health checks, or timestamping workflows that only need block number, timestamp, and lag — not full transaction data.

## Known failure modes

- 402 Payment Required if prepaid balance is exhausted
- 503 or timeout if Goldsky indexer is temporarily unavailable
- Stale data if head_lag_seconds is elevated due to indexer sync issues
- Network errors if edge.goldsky.com is unreachable

## How this service works

Goldsky Feeds: Prediction markets and Chain datasets — prepaid balance, funds ~500 requests at 10 atomic units each

## Output

Returns a JSON object containing the chain name (e.g. 'base'), the latest block number as an integer, the block's Unix timestamp, and the head_lag_seconds indicating how many seconds the indexed head trails the actual chain tip.

## 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",
     "required": [],
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "chain",
      "number",
      "timestamp",
      "head_lag_seconds"
     ],
     "properties": {
      "chain": {
       "type": "string"
      },
      "number": {
       "type": "integer"
      },
      "timestamp": {
       "type": "integer"
      },
      "head_lag_seconds": {
       "type": "integer"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/goldsky-feeds-base-chain-head-block-cf3fa614/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from edge.goldsky.com](https://www.zero.xyz/host/edge.goldsky.com/llms.txt)