# Agent402 Token Info — ERC-20/721/1155 Metadata via Blockscout

> Agent402 Token Info — ERC-20/721/1155 Metadata via Blockscout is a paid API for AI agents from agent402.tools, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Fetches on-chain metadata (name, symbol, decimals, type, total supply, holder count, 24h transfer count) for any ERC-20, ERC-721, or ERC-1155 token on any Blockscout-hosted chain

## Facts

- Endpoint: POST https://agent402.tools/api/token-info
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent402-token-info-erc-20-721-1155-metadata-via-blockscout-0dde71a2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S4sDBGoelpUCCjWsK5GHc

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-token-info-erc-20-721-1155-metadata-via-blockscout-0dde71a2 -d '<json body>'
```

Example prompt: What's the name, symbol, total supply, and holder count for the token at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum?

## When to prefer this

Use this endpoint when you need authoritative on-chain token metadata (name, symbol, decimals, supply, holders, recent activity) for any ERC token on a Blockscout-indexed chain without managing your own API key — especially when working with Base, Polygon, Arbitrum, Optimism, or Ethereum tokens in an agent workflow that handles micropayments via x402.

## Known failure modes

- Invalid or non-contract address returns an error or empty result
- Unsupported chain identifier returns a chain resolution error
- Token contract exists but is not indexed by Blockscout returns no data
- Payment failure over x402 protocol results in 402 response and no data
- Network timeout from Blockscout Pro API causes upstream error

## How this service works

Explorer-grade metadata for any ERC-20/721/1155 token on any Blockscout-hosted chain: name, symbol, decimals, type, total supply, holder count, and 24h transfer count - bought per call from Blockscout's Pro API over x402, no API key. Marked untrustedContent: token names are attacker-chosen, analyze don't trust.

## Output

Returns structured token metadata including name, symbol, decimals, token standard (ERC-20/721/1155), total supply, current holder count, and number of transfers in the past 24 hours for the specified contract on the requested chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "description": "chain name or numeric id (default base)"
  },
  "address": {
   "type": "string",
   "description": "token contract address (0x…)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "USD Coin",
  "type": "ERC-20",
  "chain": "8453",
  "symbol": "USDC",
  "address": "0x8335…2913",
  "holders": "…",
  "decimals": "6",
  "untrustedContent": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent402-token-info-erc-20-721-1155-metadata-via-blockscout-0dde71a2/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)