# Blockscout Arbitrum Batch Count

> Blockscout Arbitrum Batch Count is a paid API for AI agents from api.blockscout.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Returns the total count of Arbitrum L2 batches submitted to the L1 chain, as tracked by Blockscout's explorer for the specified chain.

## Facts

- Endpoint: GET https://api.blockscout.com/%7Bchain_id%7D/api/v2/arbitrum/batches/count
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-arbitrum-batch-count-0c3bbf11
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nXD4tSUKTCQZbylY3SIUj

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 blockscout-arbitrum-batch-count-0c3bbf11
```

Example prompt: How many Arbitrum batches have been submitted to L1 so far? Pull the current total batch count from Blockscout for Arbitrum.

## When to prefer this

Use this endpoint when you need a quick scalar count of total Arbitrum L2 batches without needing full batch details. Ideal for dashboards, monitoring pipelines, or sanity checks on rollup progress. Prefer this over fetching full batch lists when only the count is needed, saving bandwidth and cost.

## Known failure modes

- Invalid or unsupported chain_id returns a 404 or error response
- Chain not yet indexed by Blockscout returns zero or empty result
- Rate limiting or payment failure (402) if x402 payment is not properly attached
- Network timeout if Blockscout's indexer is temporarily unavailable

## How this service works

Explore crypto activities with Blockscout's multichain search. Find transactions, addresses, tokens, and dapps across top blockchain networks — your go-to explorer for cross-chain blockchain data

## Output

A single integer representing the total number of Arbitrum batches that have been submitted and indexed by Blockscout for the given chain. Example response: 0 (or any non-negative integer reflecting the current batch count).

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "properties": {
      "chain_id": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": 0
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-arbitrum-batch-count-0c3bbf11/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockscout.com](https://www.zero.xyz/host/api.blockscout.com/llms.txt)