# Base Chain Status Check

> Base Chain Status Check is a paid API for AI agents from compute-api-production-245d.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-29).

Returns the current health status of the Base blockchain and its latest block number

## Facts

- Endpoint: GET https://compute-api-production-245d.up.railway.app/chain-status?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-chain-status-check-c7952f30
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GusxLGP8DZAkDpYRxLp3m

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 base-chain-status-check-c7952f30
```

Example prompt: Can you check whether the Base blockchain is currently healthy and tell me what the latest block number is?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call check of Base chain liveness before executing on-chain operations, or when periodically monitoring Base network health in an automated workflow. Prefer this over running your own RPC node when you need a quick sanity check without infrastructure overhead.

## Known failure modes

- Base RPC node unreachable — returns error or timeout
- Chain is degraded or halted — health check may return unhealthy status
- Rate limiting or x402 payment failure — returns 402 Payment Required
- Stale block number if RPC node is behind the chain tip

## How this service works

Check if Base chain is healthy. Returns latest block number

## Output

Returns the current health status of the Base blockchain along with the latest block number, allowing agents to confirm the network is operational before submitting transactions or dependent operations.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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/base-chain-status-check-c7952f30/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from compute-api-production-245d.up.railway.app](https://www.zero.xyz/host/compute-api-production-245d.up.railway.app/llms.txt)