# Obol Base Network Status

> Obol Base Network Status is a paid API for AI agents from obol.danieldutoit.net, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns verified, multi-provider-consensus Base blockchain network status including latest block, block hash, and provider agreement.

## Facts

- Endpoint: GET https://obol.danieldutoit.net/v1/base/network-status
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-base-network-status-6ff12a9a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tI181devHUSgJm_X_CdRt

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 obol-base-network-status-6ff12a9a
```

Example prompt: What's the current block number and network status on Base right now — verified across multiple providers?

## When to prefer this

Prefer this endpoint when you need cryptographically-grounded, multi-provider-verified Base network status rather than a single-RPC query. It is ideal for audit logging, pre-transaction health checks, or any application where provider consensus matters. At $0.001 USDC per call via x402, it is cost-effective for real-time or frequent polling.

## Known failure modes

- Payment not provided or insufficient USDC — returns HTTP 402 Payment Required
- Provider inconsistency — providers disagree on current block, agreement field returns false
- Network outage — upstream RPC providers unreachable, returns error
- Invalid or expired payment — 402 with payment validation failure

## How this service works

Obol sells verified blockchain data over x402, settled in USDC on Base.

## Output

A JSON object containing the Base chain ID (8453), network identifier (eip155:8453), the most recently observed block number and hash, the timestamp of observation, and a provider consistency object showing whether multiple providers agree on the current state, how many providers were polled, and which providers were used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": {
   "id": 8453,
   "name": "Base"
  },
  "network": "eip155:8453",
  "observed_at": "2026-09-10T15:41:03.000Z",
  "observed_block": 51132758,
  "observed_block_hash": "0x3c3ef53d548d15b1da11be5c5eb3e1435fd8e37e9f08a058d134cd1ee5cb7a91",
  "provider_consistency": {
   "agreement": true,
   "providers": [
    "base-public.nodies.app",
    "mainnet.base.org"
   ],
   "provider_count": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-base-network-status-6ff12a9a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from obol.danieldutoit.net](https://www.zero.xyz/host/obol.danieldutoit.net/llms.txt)