# Chainsize - Historical EVM Chain Size

> Chainsize - Historical EVM Chain Size is a paid API for AI agents from stablecrypto.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Returns historical blockchain chain size data for a given EVM chain over a specified date range, proxying Etherscan's chainsize stats API.

## Facts

- Endpoint: POST https://stablecrypto.dev/api/etherscan/stats/chainsize
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainsize-historical-evm-chain-size-c486fd09
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AsSTOjxG2-wVEab86CbXh

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 chainsize-historical-evm-chain-size-c486fd09 -d '<json body>'
```

Example prompt: Can you pull the historical Ethereum mainnet chain size from January 1, 2023 to December 31, 2023, sorted ascending, for a geth client in default sync mode?

## When to prefer this

Use this endpoint when you need historical on-chain storage growth data for EVM-compatible chains, particularly Ethereum. Prefer it over generic RPC endpoints when you need time-series chain size statistics rather than live block data. It is especially useful for infrastructure planning, node operator analysis, and blockchain growth research where archive vs. default sync mode distinction matters.

## Known failure modes

- Invalid chain ID returns an error or empty result
- Date range too broad may hit API limits or timeouts
- Unsupported chain ID for Etherscan coverage returns no data
- Malformed date format (not YYYY-MM-DD) causes validation error
- Invalid enum values for sort, syncmode, or clienttype return errors
- Payment not processed causes 402 response before data is returned

## How this service works

Pay-per-request access to CoinGecko, DefiLlama, Alchemy, and Etherscan APIs. No auth, no subscriptions.

## Output

A time-series dataset of historical chain size measurements for the specified EVM chain and date range, including data points such as date and chain size in bytes or GB, sourced from Etherscan's stats API.

## Example request

```json
{
 "sort": "asc",
 "chainid": 1,
 "enddate": "2023-01-31",
 "syncmode": "default",
 "startdate": "2023-01-01",
 "clienttype": "geth"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sort": {
   "enum": [
    "asc",
    "desc"
   ],
   "type": "string"
  },
  "chainid": {
   "type": "number",
   "description": "EVM chain ID (1=Ethereum, 137=Polygon, 8453=Base, etc.)"
  },
  "enddate": {
   "type": "string",
   "description": "End date (YYYY-MM-DD)"
  },
  "syncmode": {
   "enum": [
    "default",
    "archive"
   ],
   "type": "string"
  },
  "startdate": {
   "type": "string",
   "description": "Start date (YYYY-MM-DD)"
  },
  "clienttype": {
   "enum": [
    "geth",
    "parity"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainsize-historical-evm-chain-size-c486fd09/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stablecrypto.dev](https://www.zero.xyz/host/stablecrypto.dev/llms.txt)