# Horizon Pulse Batch Chain Checks API

> Horizon Pulse Batch Chain Checks API is a paid API for AI agents from horizonpulse.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Executes up to 10 blockchain/crypto sub-queries in a single paid request, batching balance, gas, tx-status, token metadata, chain head, and name resolution calls into one response.

## Facts

- Endpoint: GET https://horizonpulse.dev/api/batch?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/horizon-pulse-batch-chain-checks-api-655eb021
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Yo8qERXwAn9xmH1vAidAi

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 horizon-pulse-batch-chain-checks-api-655eb021
```

Example prompt: Can you batch-check my wallet balance on Base, the current gas price, and the status of transaction 0xabc123 all in one go — using the Horizon Pulse batch endpoint so I only pay once?

## When to prefer this

Choose this endpoint when you need results from 2 or more of Horizon Pulse's individual routes (balance, gas, tx-status, token/meta, chain/head, name/resolve) and want to minimize latency and cost — you pay a single $0.01 charge rather than multiple per-route fees, and you get all results in one round trip. Prefer the individual route endpoints if you only need a single data type or need to handle failures for each route independently with separate retry logic.

## Known failure modes

- Invalid JSON in items parameter returns a bad-input error and is not charged
- All sub-items failing returns an error response and is not charged
- More than 10 items in the batch array may be rejected
- An unrecognized route name within a batch item causes that item to fail with a non-ok status
- Malformed params for a sub-route cause that item to fail while others may succeed
- Network or upstream chain RPC failures can cause individual items to return non-ok status

## How this service works

Batch chain checks API: up to 10 checks for one payment. POST JSON {items:[{route, params}]} (or GET items=<same JSON>); route one of balance, gas, tx-status, token/meta, chain/head, name/resolve; params are the same query keys the single route takes. Returns JSON: results [{index, route, status, ok, body}] in request order, count, okCount. Each item runs the single route's handler. Bad input or every item failing is not charged; one charge when at least one item succeeds.

## Output

Returns a JSON object with a `results` array (one entry per requested item, preserving input order), each containing `index`, `route`, `status` (HTTP status code), `ok` (boolean), and `body` (the single-route JSON response for that sub-query). Also includes `count` (total items) and `okCount` (number of successful items). Charged only when at least one item succeeds.

## 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",
     "required": [
      "items"
     ],
     "properties": {
      "items": {
       "type": "string",
       "description": "JSON array of 1-10 {route, params} objects (same shape as the POST body's items)."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "description": "Horizon Pulse batch: results[] in request order (index, route, status, ok, body = the single route's JSON without priced/charged), count, okCount. The example is an illustrative format sample (illustrative: true), not a recorded real response."
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/horizon-pulse-batch-chain-checks-api-655eb021/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from horizonpulse.dev](https://www.zero.xyz/host/horizonpulse.dev/llms.txt)