# basefeed ERC-20 Token Metadata

> basefeed ERC-20 Token Metadata is a paid API for AI agents from api.basefeed.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns metadata for an ERC-20 token contract on Base or Base Sepolia by contract address

## Facts

- Endpoint: GET https://api.basefeed.io/v1/meta/token
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/basefeed-erc-20-token-metadata-035d4dc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XQp_yeESulSDG-iDz8xB1

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 basefeed-erc-20-token-metadata-035d4dc0
```

Example prompt: What are the name, symbol, and decimals for the ERC-20 token at contract address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base?

## When to prefer this

Use this endpoint when you need to look up ERC-20 token metadata (name, symbol, decimals) for a contract deployed specifically on Base mainnet or Base Sepolia testnet. Prefer this over general blockchain explorers when operating within an x402 micropayment-enabled agent workflow on the Base ecosystem.

## Known failure modes

- Invalid or non-ERC-20 contract address returns error or empty metadata
- Contract address exists but is not an ERC-20 token results in missing fields
- Unsupported chain value (outside 'base' or 'base-sepolia') returns validation error
- Malformed address format causes 400-level error
- Payment failure via x402 protocol prevents request from proceeding
- Contract deployed on a different chain than specified returns not-found error

## How this service works

ERC-20 token metadata

## Output

Token metadata for the specified ERC-20 contract, including fields such as token name, symbol, decimals, and potentially other on-chain metadata attributes for the given contract on Base mainnet or Base Sepolia testnet.

## 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": {
      "chain": {
       "enum": [
        "base",
        "base-sepolia"
       ],
       "type": "string",
       "default": "base"
      },
      "address": {
       "type": "string",
       "description": "ERC-20 contract"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "token": {
   "symbol": "USDC",
   "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "decimals": 6
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/basefeed-erc-20-token-metadata-035d4dc0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.basefeed.io](https://www.zero.xyz/host/api.basefeed.io/llms.txt)