# Blockscout Token Info API

> Blockscout Token Info API 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-15).

Retrieve detailed metadata and on-chain information about a specific ERC-20 or other token by its contract address on a given blockchain

## Facts

- Endpoint: GET https://api.blockscout.com/:chain_id/api/v2/tokens/:address_hash_param
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-token-info-api-f3e36b85
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UI6onTQc6geqb5Qeb0Nas

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-info-api-f3e36b85
```

Example prompt: Can you pull up the full token details for the contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum mainnet — I want to see the name, symbol, total supply, and decimals?

## When to prefer this

Use this endpoint when you need authoritative on-chain token metadata for a specific contract address across multiple EVM-compatible chains. Prefer it over generic blockchain explorers when you need structured JSON data about a token (name, symbol, supply, decimals, holders) for programmatic use. Ideal when the contract address is known and you need to identify or verify what token it represents, especially on chains indexed by Blockscout (Ethereum, Polygon, Base, Gnosis, etc.).

## Known failure modes

- Invalid or non-existent contract address returns 404 not found
- Unsupported or invalid chain_id returns an error response
- Contract address exists but is not a token contract — returns empty or error
- Rate limiting may occur under high request volume
- Token may exist but have no indexed metadata yet if recently deployed

## How this service works

Access to api/v2/tokens/:address_hash. Retrieve detailed information about a specific token

## Output

Returns a JSON object containing comprehensive token metadata including token name, symbol, token type (e.g. ERC-20, ERC-721), total supply, number of decimals, holder count, contract address, token logo URL, and exchange rate/price information where available.

## 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"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-token-info-api-f3e36b85/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)