# Blockscout Arbitrum Batch Details

> Blockscout Arbitrum Batch Details 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).

Retrieves details of a specific Arbitrum batch by batch number on a given chain, including block range, transaction count, and commitment transaction info

## Facts

- Endpoint: GET https://api.blockscout.com/%7Bchain_id%7D/api/v2/arbitrum/batches/%7Bbatch_number%7D
- 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-details-7b6b48d8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qhuy_xAbz0ElqLo5kd6wq

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-details-7b6b48d8
```

Example prompt: Can you pull up the details for Arbitrum batch number 42 on chain arbitrum using Blockscout — I want to see the block range it covers, how many transactions were in it, and the status of its L1 commitment transaction.

## When to prefer this

Use this endpoint when you need detailed metadata about a specific Arbitrum batch by number — including its L1 commitment transaction, block range, and data availability. Prefer this over general transaction lookup endpoints when investigating Arbitrum L2 batch-level data, rollup sequencing, or cross-layer verification workflows.

## Known failure modes

- Invalid or non-existent batch_number returns a 404 or empty response
- Unsupported chain_id returns an error or no data
- Network timeouts on heavily loaded chains
- Batch not yet committed may return incomplete commitment transaction fields
- Malformed batch_number (non-integer) causes a 400 bad request

## 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

Returns a JSON object containing the batch number, before and after accumulator hashes, start and end block numbers, transaction count, data availability metadata, and the commitment transaction details (hash, status, timestamp, and block number on L1).

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "number": 0,
  "after_acc_hash": "string",
  "before_acc_hash": "string",
  "end_block_number": 0,
  "data_availability": {},
  "start_block_number": 0,
  "transactions_count": 0,
  "commitment_transaction": {
   "hash": "string",
   "status": "string",
   "timestamp": "string",
   "block_number": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-arbitrum-batch-details-7b6b48d8/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)