# Agent402 Block Receipts

> Agent402 Block Receipts is a paid API for AI agents from agent402.tools, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Fetches transaction receipts and a summary for a specific Ethereum-compatible block, including gas usage, fee totals, transaction types, and per-transaction details.

## Facts

- Endpoint: POST https://agent402.tools/api/block-receipts
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent402-block-receipts-93a1818a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6poMEpiUXHsp9X1pPOGsp

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 agent402-block-receipts-93a1818a -d '<json body>'
```

Example prompt: Can you pull all the transaction receipts for block 25563191 on Ethereum and give me a summary of gas used, fees, and how many transactions succeeded or failed?

## When to prefer this

Choose this endpoint when you need comprehensive receipt-level data for an entire block across major EVM-compatible networks (Ethereum, Base, Polygon, Arbitrum, Optimism), including aggregated summaries and per-transaction status, fees, and gas. It is especially useful for on-chain analytics, block auditing, or fee monitoring where you want both a block-level summary and individual receipt details in a single call without setting up your own RPC infrastructure.

## Known failure modes

- Invalid or non-existent block number returns an error or empty result
- Unsupported network name causes a validation error
- Limit value outside 0–300 range may be rejected or clamped
- Block not yet finalized (future block) returns not-found error
- Network congestion or upstream Alchemy timeout causes slow or failed response

## How this service works

Every transaction receipt in one block, fetched as a single upstream read and summarised: tx count, succeeded vs failed, total gas used, total fees, log count, contract creations, tx-type mix - plus compact per-transaction rows (hash, from, to, status, gas used, effective gas price, fee, log count) capped at 300. Block analytics, failed-tx hunting, or 'who paid what in block N' without N separate receipt calls.

## Output

Returns a JSON object containing: the block number, source (Alchemy), chainId, network name, a summary object (transaction type counts, failed/succeeded counts, total fee in Wei and native units, gas used, tx count, log count, contract creations), an array of per-transaction receipts (to, from, hash, type, index, feeWei, status, gasUsed, logCount, contractAddress, effectiveGasPriceGwei), total returned count, blockHash, and fetch timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "block": {
   "type": "string",
   "description": "Block number (decimal or 0x hex) or latest."
  },
  "limit": {
   "type": "number",
   "description": "Per-transaction rows to return, 0-300 (default 100). The summary always covers the whole block."
  },
  "network": {
   "type": "string",
   "description": "ethereum / base / polygon / arbitrum / optimism (default ethereum)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "block": 25563191,
  "source": "alchemy",
  "chainId": 1,
  "network": "ethereum",
  "summary": {
   "types": {
    "0x0": 16,
    "0x2": 126,
    "0x3": 1,
    "0x4": 6
   },
   "failed": 6,
   "feeWei": "4453605500724532",
   "gasUsed": "16506190",
   "txCount": 149,
   "logCount": 420,
   "feeNative": "0.004453605500724532",
   "succeeded": 143,
   "contractCreations": 0
  },
  "receipts": [
   {
    "to": "0x7c46…0f54",
    "from": "0xb01c…9c2e",
    "hash": "0xdcae…9cd6",
    "type": "0x2",
    "index": 0,
    "feeWei": "21852814746000",
    "status": "success",
    "gasUsed": "21000",
    "logCount": 0,
    "contractAddress": null,
    "effectiveGasPriceGwei": 1.040610226
   }
  ],
  "returned": 5,
  "blockHash": "0x8e12…1243",
  "fetchedAt": "2026-08-22T12:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent402-block-receipts-93a1818a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)