# Blockscout Token Counters by Chain

> Blockscout Token Counters by Chain 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-12).

Returns transfer count and holder count statistics for a specific token contract on a given blockchain network

## Facts

- Endpoint: GET https://api.blockscout.com/%7Bchain_id%7D/api/v2/tokens/%7Baddress_hash_param%7D/counters
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-token-counters-by-chain-d3695ca9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CSQ9eczP-gqkcisv10v1X

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-token-counters-by-chain-d3695ca9
```

Example prompt: How many holders and total transfers does the USDC token contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 have on Ethereum mainnet? Use Blockscout to look it up.

## When to prefer this

Choose this endpoint when you need lightweight, fast token adoption statistics (holder count and transfer count) for a specific contract on a specific chain without requiring full transfer history or holder list. It is more efficient than fetching paginated holder lists or transfer lists when only aggregate counts are needed. Best for dashboards, quick comparisons, or eligibility checks where raw totals suffice.

## Known failure modes

- Invalid or non-existent token contract address returns empty or error response
- Unsupported chain_id returns 404 or no data
- Token contract exists but has no recorded transfers yet — counters may return zero strings
- Network latency or Blockscout node downtime causes timeout
- Malformed address hash (wrong length or checksum) returns validation error

## 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 with two string fields: transfers_count (total number of token transfer events recorded on-chain for that contract) and token_holders_count (total number of unique addresses currently holding a non-zero balance of the token), both as stringified integers.

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "transfers_count": "string",
  "token_holders_count": "string"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-token-counters-by-chain-d3695ca9/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)