# Hermes x402 Toolkit – Base Token Info Lookup

> Hermes x402 Toolkit – Base Token Info Lookup is a paid API for AI agents from api.zlovev.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-19).

Fetches on-chain metadata for a token contract on Base mainnet given a 0x address, returning symbol, decimals, EIP-3009 support, total supply, and contract status.

## Facts

- Endpoint: GET https://api.zlovev.com/api/chain/token
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hermes-x402-toolkit-base-token-info-lookup-3d2e7dc4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JaNp_hYVn4AOB002HzMDc

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 hermes-x402-toolkit-base-token-info-lookup-3d2e7dc4
```

Example prompt: Can you look up the token metadata for the contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base mainnet — I need its symbol, decimals, total supply, and whether it supports EIP-3009?

## When to prefer this

Choose this endpoint when you need on-chain Base mainnet token metadata (symbol, decimals, EIP-3009 support, total supply) without registering for an account or holding an API key — ideal for AI agents that pay per call via USDC on Base using the x402 protocol. Prefer alternatives like Alchemy or Infura if you need batch lookups, historical data, or multi-chain support.

## Known failure modes

- Address not 0x-prefixed or not 20 bytes — validation error
- Address is an EOA (non-contract) — returns is_contract=false with no token fields
- Network issues with Base RPC — timeout or 5xx
- Missing required 'address' query parameter — 400 error
- Payment not settled — 402 Payment Required if x402 flow fails

## How this service works

Pay-per-call data API for AI agents. No API key, no account, no signup — pay USDC on Base (eip155:8453) per request; free /api/meta lists all 22 endpoints. One call each: web page to LLM-ready text and link previews; China A-share quotes and limit-up pool; Chinese text and pinyin; Base/Ethereum on-chain reads (address, token, ERC-20 balances, tx, blocks, transfer history, gas price in USD); NFT records (collection, owner, and ipfs:// tokenURI resolved through public gateways); full-page screenshots; email verification without sending mail; ENS forward/reverse resolution; smart-contract due diligence (ABI, verified source, proxy); token security facts (owner, renounced ownership, paused, bytecode capability selectors); domain dossier (RDAP, DNS, TLS certificate, HTTP facts, hosting network).

## Output

A JSON object with ok=true, the token's symbol (e.g. 'USDC'), its contract address, whether EIP-3009 is supported, the number of decimals, a flag confirming it is a contract, and the total supply as a string. Returns ok=false with an error on invalid or non-contract addresses.

## 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"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string",
       "description": "0x-prefixed 20-byte address on Base mainnet"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "symbol": "USDC",
  "address": "0x8335…2913",
  "eip3009": {
   "supported": true
  },
  "decimals": 6,
  "is_contract": true,
  "total_supply": "4231….0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hermes-x402-toolkit-base-token-info-lookup-3d2e7dc4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zlovev.com](https://www.zero.xyz/host/api.zlovev.com/llms.txt)