# Synapse API — Arbitrum Token Metadata

> Synapse API — Arbitrum Token Metadata is a paid API for AI agents from synapse-api-brown.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

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

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/arbitrum/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/synapse-api-arbitrum-token-metadata-49409482
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZVfgn6JZyiTomIsazKO8z

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 synapse-api-arbitrum-token-metadata-49409482 -d '<json body>'
```

Example prompt: Can you look up the token metadata for the contract address 0xFF970A61A04b1cA14834A43f5dE4533eBDDB5CC8 on the Arbitrum network — I need the name, symbol, and decimals.

## When to prefer this

Use this endpoint when you specifically need on-chain token metadata from the Arbitrum network and want a pay-per-call model without managing RPC infrastructure. Prefer this over raw RPC calls when you need a simple, hosted, pay-as-you-go solution for Arbitrum token lookups.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty metadata
- Contract exists but is not a token contract (no ERC-20 interface) — may return null fields or an error
- Network or RPC issues causing a timeout
- Payment failure via x402 prevents the call from being processed

## How this service works

High-speed API suite for AI processing, web scraping, and smart data utilities across 57+ blockchain networks. Pay-per-call via x402.

## Output

Returns on-chain metadata for the specified Arbitrum token contract, typically including the token name, symbol, decimals, and possibly total supply or other ERC-20 standard fields stored on-chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contractAddress": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synapse-api-arbitrum-token-metadata-49409482/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from synapse-api-brown.vercel.app](https://www.zero.xyz/host/synapse-api-brown.vercel.app/llms.txt)
