# Phantom API — zkSync Token Metadata

> Phantom API — zkSync 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-14).

Retrieves token metadata (name, symbol, decimals, etc.) for a given smart contract address on the zkSync network

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/zksync/token/metadata
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phantom-api-zksync-token-metadata-1d94c41a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3fMkK3pt5ZBCzsng9XRkW

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-zksync-token-metadata-1d94c41a -d '<json body>'
```

Example prompt: What's the name, symbol, and decimals for the token at zkSync contract address 0x3355df6D4c9C3035724Fd0e3914dE96A5a83aaf6?

## When to prefer this

Choose this endpoint when you specifically need token metadata from the zkSync (zkSync Era / ZK Stack) Layer 2 network, rather than Ethereum mainnet or other L2s. Ideal for DeFi apps, portfolio trackers, block explorers, and wallet UIs that need to display human-readable token information for zkSync-native or bridged tokens.

## Known failure modes

- Invalid or malformed contract address returns an error
- Contract address exists but is not a token contract (e.g. a generic smart contract) may return empty or error
- Non-existent address on zkSync returns not-found error
- Network or RPC unavailability causes timeout
- Rate limiting or payment failure blocks the request

## 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 token metadata for the specified zkSync contract address, typically including the token name, symbol, number of decimals, and potentially additional contract-level information such as total supply or token standard.

## 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-zksync-token-metadata-1d94c41a/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)