# Phantom API — Token Metadata Lookup

> Phantom API — Token Metadata Lookup is a paid API for AI agents from phantom-api-omega.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Fetches on-chain token metadata (name, symbol, decimals, supply, etc.) for a given smart contract address across 57+ blockchain networks

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/adi/token/metadata?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-token-metadata-lookup-039e4b25
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9_xXCcIluGTi518ERLz8W

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 phantom-api-token-metadata-lookup-039e4b25 -d '<json body>'
```

Example prompt: Can you look up the token metadata for contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 — I want to know the token name, symbol, and decimals?

## When to prefer this

Choose this endpoint when you need fast, pay-per-call on-chain token metadata without a long-term API subscription — ideal for agents that occasionally resolve contract addresses to human-readable token details across a wide variety of EVM-compatible and other blockchain networks. Prefer it over general blockchain RPC calls when you want a structured metadata response rather than raw contract ABI interaction.

## Known failure modes

- Invalid or malformed contract address returns an error
- Contract address exists but is not a standard token contract (e.g. raw EOA or non-ERC-20), resulting in empty or partial data
- Network not supported among the 57+ chains may return an error or null result
- Rate limits or payment failures via x402 protocol block the request
- Contract deployed on a different chain than expected yields incorrect or no metadata

## How this service works

Lightning-fast access to blockchain data, smart contract insights, and Web3 infrastructure across 57+ networks. Pay-per-call via x402.

## Output

Returns on-chain token metadata for the given contract address, typically including token name, ticker symbol, number of decimals, total supply, and possibly additional contract-level information sourced directly from the blockchain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contractAddress": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phantom-api-token-metadata-lookup-039e4b25/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phantom-api-omega.vercel.app](https://www.zero.xyz/host/phantom-api-omega.vercel.app/llms.txt)