# Pocket Network Token Metadata

> Pocket Network Token Metadata is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Returns canonical ERC-20 token metadata (symbol, decimals, name, logo, provenance) for a given token contract address across 6 EVM chains, sourced from curated token lists.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/token-metadata?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-token-metadata-e510fcd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AOhtdA4QzylItUvBHAETx

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 pocket-network-token-metadata-e510fcd7 -d '<json body>'
```

Example prompt: What's the name, symbol, and number of decimals for the token at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum mainnet (chain ID 1)?

## When to prefer this

Choose this endpoint when you need fast, deterministic, curated token metadata (symbol, decimals, name, logo) for ERC-20 tokens across major EVM chains without managing an API key or account. It is ideal for DeFi agents, portfolio apps, or transaction formatters that need reliable token information sourced from well-known token lists rather than raw on-chain calls. Prefer it over rolling your own token-list parsing or calling individual chain explorers.

## Known failure modes

- Token address not found in any supported token list — returns empty or 404 response
- Unsupported chain ID — only 6 EVM chains are supported; requests for others will fail or return no data
- Malformed 0x address — invalid checksums or non-hex characters cause validation errors
- Payment failure — insufficient USDC or x402 protocol error prevents the call from completing
- Token exists on-chain but is not listed in the curated token lists — metadata unavailable

## How this service works

Canonical token metadata across 6 EVM chains: symbol, decimals, name, logo, and token-list provenance. POST /v1/token with {address, chain_id} and get one JSON object back. Deterministic per token-list vintage. Pay per request in USDC; no account, no API key.

## Output

A single JSON object containing the token's canonical symbol, full name, decimal precision, logo image URL, and the token-list source that provided the data. The response is deterministic per token-list vintage — the same address and chain ID always returns the same metadata for a given list version.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "description": "Token contract address, 0x-prefixed."
  },
  "chain_id": {
   "type": "integer",
   "description": "EVM chain id (default 1)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "portal": {
   "serviceId": "token-metadata",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-token-metadata-e510fcd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)