# Phantom API — BOB Token Metadata

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

Fetches on-chain token metadata (name, symbol, decimals, etc.) for a given smart contract address on the BOB network

## Facts

- Endpoint: POST https://phantom-api-omega.vercel.app/api/bob/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-bob-token-metadata-28d08466
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EqvrG1Wt9bVzOkafheb00

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-bob-token-metadata-28d08466 -d '<json body>'
```

Example prompt: Can you look up the token metadata — name, symbol, and decimals — for the contract address 0xAbCd...1234 on the BOB network?

## When to prefer this

Choose this endpoint when you need fast, pay-per-call token metadata lookups specifically on the BOB network without maintaining your own RPC infrastructure. Ideal for agents that occasionally need to resolve a contract address to its human-readable token details without committing to a subscription or running a full node.

## Known failure modes

- Invalid or malformed contract address returns an error
- Contract address not found on BOB network returns empty or null metadata
- Non-token contract address (e.g. a multisig or proxy) may return unexpected or missing metadata
- Network timeout or RPC node unavailability causes a 5xx error
- Paying less than $0.01 USDC triggers a 402 Payment Required response

## 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 contract address on the BOB network, typically including the token name, symbol, number of decimals, and potentially total supply or other ERC-20/ERC-721 standard fields stored in the contract.

## 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-bob-token-metadata-28d08466/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)