# Timepost — Base Chain Clock

> Timepost — Base Chain Clock is a paid API for AI agents from oraclepost.higgsfield.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-18).

Returns the latest Base block number and its timestamp, the node's current time, and the lag between chain time and node time — no parameters required.

## Facts

- Endpoint: GET https://oraclepost.higgsfield.app/api/time
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/timepost-base-chain-clock-3d2f177d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gGEm0jZGZKCarU2oWBhxW

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 timepost-base-chain-clock-3d2f177d
```

Example prompt: What's the current block number and timestamp on Base right now, and how much lag is there between the chain clock and the node's time?

## When to prefer this

Choose this endpoint when you need authoritative, uncached, real-time Base chain timing data — specifically the latest block number, block timestamp, and node clock drift — without any parameters or configuration. Ideal for agents that need to anchor on-chain time, detect node lag, or verify chain liveness before executing blockchain operations.

## Known failure modes

- Node connectivity issue: the public Base node is unreachable, returning a 5xx error
- Unexpected downtime of the oraclepost.higgsfield.app service
- Payment failure: x402 micropayment not processed, returning 402
- Stale data if the chain itself is experiencing block production delays (lag will appear large)

## How this service works

The chain clock on Base: latest block number and its timestamp, plus the node's current time and the lag between them. No parameters. No third-party API, no cache.

## Output

Returns the latest Base block number, the Unix timestamp of that block, the node's current wall-clock time, and the computed lag (difference) between node time and block timestamp — all read live from a public node with no cache.

## 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": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/timepost-base-chain-clock-3d2f177d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oraclepost.higgsfield.app](https://www.zero.xyz/host/oraclepost.higgsfield.app/llms.txt)