# Tokenvault — ERC-20 Token Metadata on Base

> Tokenvault — ERC-20 Token Metadata on Base is a paid API for AI agents from oraclepost.higgsfield.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-18).

Returns live ERC-20 token metadata (name, symbol, decimals, total supply) from a contract on Base by making direct eth_call reads with no cache or third-party API.

## Facts

- Endpoint: GET https://oraclepost.higgsfield.app/api/premium/token
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tokenvault-erc-20-token-metadata-on-base-373fc15f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lj-xnXsURLKb8zhMFKUwQ

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 tokenvault-erc-20-token-metadata-on-base-373fc15f
```

Example prompt: Look up the token metadata for the contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base — I need the name, symbol, decimals, and total supply straight from the contract.

## When to prefer this

Choose this endpoint when you need authoritative, uncached ERC-20 metadata (name, symbol, decimals, total supply) for a specific contract address on the Base network. It is ideal when freshness matters, when you cannot trust indexed or cached sources, or when verifying a contract's identity directly from the chain. Prefer it over generic block explorers or token registries when you need programmatic access to raw on-chain metadata without third-party data dependencies.

## Known failure modes

- Invalid or non-ERC-20 contract address returns an error or empty/reverted call result
- Contract on a network other than Base will not resolve correctly
- Malformed 0x address format causes a validation or RPC error
- Token contract that does not implement standard ERC-20 metadata functions (name/symbol/decimals) may return partial or no data
- RPC node unavailability on Base causes a timeout or network error

## How this service works

ERC-20 token metadata on Base, read live from the contract: name, symbol, decimals and total supply. Pass ?token=0x… (the token contract address). One eth_call set, no third-party API, no cache.

## Output

Returns the four standard ERC-20 metadata fields read live via eth_call from the Base chain: token name (string), symbol (string), decimals (uint8), and total supply (uint256). Data is real-time with no caching layer or third-party intermediary.

## 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": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "token"
     ],
     "properties": {
      "token": {
       "type": "string",
       "description": "ERC-20 contract address on Base, 0x-prefixed"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tokenvault-erc-20-token-metadata-on-base-373fc15f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oraclepost.higgsfield.app](https://www.zero.xyz/host/oraclepost.higgsfield.app/llms.txt)