# Token Metadata

> Token Metadata is a paid API for AI agents from stablecrypto.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Retrieves metadata for a token contract on a specified blockchain network via Alchemy

## Facts

- Endpoint: POST https://stablecrypto.dev/api/alchemy/token/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/token-metadata-f0a75a76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ez0Id1mbab6S3Q1y31y2P

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

Example prompt: Can you look up the token metadata for contract address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on eth-mainnet so I can see its name, symbol, and decimals?

## When to prefer this

Use this endpoint when you need to resolve token identity (name, symbol, decimals) from a raw EVM contract address on a specific network. Ideal for enriching DeFi transaction data, validating token contracts, or displaying human-readable token info. Prefer over generic RPC calls when you want structured token metadata without writing raw eth_call logic.

## Known failure modes

- Invalid contract address returns an error or empty response
- Unsupported network slug returns a 400 or error
- Contract address exists but is not a token contract — may return null or incomplete metadata
- Rate limiting or Alchemy upstream errors causing 5xx responses
- Non-checksummed or malformed address may fail validation

## How this service works

Pay-per-request access to CoinGecko, DefiLlama, Alchemy, and Etherscan APIs. No auth, no subscriptions.

## Output

Returns a JSON object containing token metadata such as name, symbol, decimals, logo URL, and other contract-level properties for the specified token on the given network.

## Example request

```json
{
 "network": "eth-mainnet",
 "contractAddress": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "network": {
   "type": "string",
   "description": "Alchemy network slug, e.g. eth-mainnet, base-mainnet"
  },
  "contractAddress": {
   "type": "string",
   "description": "Token contract address"
  }
 }
}
```

## More

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