# Phantom API – Avalanche Token Metadata

> Phantom API – Avalanche Token Metadata 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-09-15).

Fetches on-chain token metadata (name, symbol, decimals, etc.) for a given ERC-20 or token contract on the Avalanche network.

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/avalanche/token/metadata
- 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/phantom-api-avalanche-token-metadata-4fcb91d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Gxfh-jvBB2RSnLqBafE8T

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-avalanche-token-metadata-4fcb91d3 -d '<json body>'
```

Example prompt: Can you look up the on-chain token metadata — name, symbol, and decimals — for the Avalanche contract at 0x60781C2586D68229fde47564546784ab3fACA982?

## When to prefer this

Choose this endpoint when you need fast, pay-per-call metadata resolution for Avalanche token contracts without managing your own RPC node or indexer. Ideal for one-off lookups or agent workflows that need to enrich a contract address with human-readable token details on Avalanche specifically.

## Known failure modes

- Invalid or malformed contract address returns an error
- Contract address does not correspond to a token contract (e.g. it's a wallet or non-token contract)
- Network congestion or RPC node unavailability causes a timeout
- Contract exists but does not implement standard metadata functions (name/symbol/decimals)
- Payment failure via x402 if USDC balance is insufficient

## 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 specified Avalanche contract address, typically including token name, symbol, decimal precision, and possibly total supply or other contract-level fields stored in the token's ERC-20 or native token interface.

## 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-avalanche-token-metadata-4fcb91d3/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)