# Agent Exchange — Batch Blockchain Read (Multi-Op)

> Agent Exchange — Batch Blockchain Read (Multi-Op) is a paid API for AI agents from store.agentexchange.work, paid per call via x402, $0.09/call, status unknown (last checked 2026-09-14).

Executes up to 10 batched on-chain read operations in a single call across major EVM chains, returning balances, nonces, gas prices, block numbers, token balances, and contract code checks.

## Facts

- Endpoint: GET https://store.agentexchange.work/chain/batch
- Price: $0.09/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-exchange-batch-blockchain-read-multi-op-9db19901
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RSSYAhqdmykl02d5ALY01

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 agent-exchange-batch-blockchain-read-multi-op-9db19901
```

Example prompt: On Ethereum, in one shot, give me the current block number, gas price, ETH balance for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045, and its nonce.

## When to prefer this

Choose this endpoint when you need multiple different on-chain data points for one or more addresses in a single round-trip, avoiding the overhead of separate RPC calls. It is ideal for agents that need a full wallet snapshot (balance + nonce + token holdings) before executing a transaction, or for dashboards that need block number and gas price alongside address data simultaneously. Prefer it over single-purpose endpoints when latency and call cost efficiency matter.

## Known failure modes

- Invalid or unsupported chain name returns an error or defaults to Base
- Malformed address in a read op causes that individual result to have ok:false
- Exceeding 10 ops in the reads parameter may result in truncation or rejection
- Network congestion or RPC timeout may cause partial:true with some results missing
- Payment failure (insufficient USDC or missing x402 header) returns HTTP 402

## How this service works

Machine-payable data APIs for AI agents across web search, on-chain reads, trading data, market judgment, and AI visibility. The canonical x402 catalog currently exposes 85 paid routes. Pay per call in USDC via x402 on Base. No API keys, no signup.

## Output

A JSON object with the chain name, total requested operations count, succeeded count, failed count, a partial flag, and a results array where each entry includes the read type, a boolean ok flag, and the returned value (with unit where applicable, e.g. gwei for gas, native for ETH balance).

## 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": [
      "reads"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "base|ethereum|optimism|arbitrum|polygon|gnosis (default base)"
      },
      "reads": {
       "type": "string",
       "description": "Comma-separated ops, max 10: balance:0xADDR | nonce:0xADDR | code:0xADDR | erc20:0xTOKEN:0xWALLET | blocknumber | gas"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "partial": {
       "type": "boolean"
      },
      "results": {
       "type": "array"
      },
      "requested": {
       "type": "number"
      },
      "succeeded": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "ethereum",
  "failed": 0,
  "partial": false,
  "results": [
   {
    "ok": true,
    "read": "blocknumber",
    "value": 21500000
   },
   {
    "ok": true,
    "read": "gas",
    "unit": "gwei",
    "value": 0.55
   },
   {
    "ok": true,
    "read": "balance:0xd8da...",
    "unit": "native",
    "value": 1042.3
   },
   {
    "ok": true,
    "read": "nonce:0xd8da...",
    "value": 1842
   }
  ],
  "requested": 4,
  "succeeded": 4
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-exchange-batch-blockchain-read-multi-op-9db19901/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from store.agentexchange.work](https://www.zero.xyz/host/store.agentexchange.work/llms.txt)