# Phantom API — Sonic Token Metadata

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

Retrieves on-chain token metadata for a given contract address on the Sonic blockchain network

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/sonic/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-sonic-token-metadata-f8fe5a0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ckJ-ltZmOFfVZ4erUI29v

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-sonic-token-metadata-f8fe5a0f -d '<json body>'
```

Example prompt: What are the name, symbol, and decimals for the Sonic token at contract address 0xAbC123...?

## When to prefer this

Use this endpoint when you need fast, pay-per-call token metadata lookups specifically on the Sonic blockchain network without committing to a subscription. Prefer this over general-purpose block explorers when you need programmatic access in an agent workflow and want to pay only for what you use via USDC microtransactions.

## Known failure modes

- Invalid or malformed contract address returns an error response
- Contract address not found on Sonic network returns empty or null metadata
- Network congestion may cause slow or failed lookups
- Payment failure via x402 protocol results in 402 Payment Required response
- Non-token contract addresses may return incomplete or unexpected 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 specified Sonic network contract address, typically including the token name, symbol, decimals, and possibly total supply or other ERC-20/BEP-20 standard fields.

## 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-sonic-token-metadata-f8fe5a0f/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)