# code402 ERC-20 Token Chain Data

> code402 ERC-20 Token Chain Data is a paid API for AI agents from verify.code402.dev, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-01).

Fetches on-chain ERC-20 token data for a specific token contract and address on Ethereum, returning chain data with a signed receipt, paid per call via x402 on Base (USDC).

## Facts

- Endpoint: GET https://verify.code402.dev/v1/chain/erc20/%7Btoken%7D/%7Baddress%7D?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/code402-erc-20-token-chain-data-e1e59b8f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_biN5QPyziO4i2ZJie4jVk

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 code402-erc-20-token-chain-data-e1e59b8f
```

Example prompt: Can you look up the on-chain ERC-20 token data for the USDC contract (0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) and my wallet address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum?

## When to prefer this

Choose this endpoint when you need deterministic, auditable on-chain ERC-20 token data for a specific token and wallet address on Ethereum, especially when a signed XDR-1 receipt is required for compliance or audit purposes. It is best suited for per-call, pay-as-you-go queries via x402 on Base (USDC) where you need a tamper-evident record of the query result.

## Known failure modes

- Invalid token contract address returns an error or empty result
- Invalid or malformed Ethereum wallet address returns a 400-level error
- Token contract does not exist on the specified network, returning no data
- Payment failure via x402 protocol results in 402 Payment Required before data is returned
- RPC node downtime or Ethereum network congestion may cause delayed or failed responses

## How this service works

Deterministic compliance verification (IBAN, sanctions, onchain address) with XDR-1 signed receipts, plus Ethereum chain-data endpoints. Paid per call via x402 on Base (USDC).

## Output

Returns a JSON object with a 'result' field containing the ERC-20 token chain data (such as balance or token metadata) for the given token contract and address, along with a 'network' field identifying the chain (e.g. 'ethereum'). Responses include an XDR-1 signed receipt for auditability.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "result": "string",
     "network": "ethereum-mainnet"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "chain data",
  "network": "ethereum"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/code402-erc-20-token-chain-data-e1e59b8f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verify.code402.dev](https://www.zero.xyz/host/verify.code402.dev/llms.txt)