# Synapse API — Hyperliquid Token Metadata

> Synapse API — Hyperliquid 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-10-16).

Retrieves token metadata for a given contract address on the Hyperliquid blockchain network

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/hyperliquid/token/metadata?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-api-hyperliquid-token-metadata-9afbec66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MqBHo0BHbJeFHNWogQs2p

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-hyperliquid-token-metadata-9afbec66 -d '<json body>'
```

Example prompt: Look up the token metadata for the Hyperliquid contract address 0xabc123... — I need the name, symbol, and decimals.

## When to prefer this

Choose this endpoint when you need on-chain token metadata specifically from the Hyperliquid network and want a simple pay-per-call REST interface without managing your own RPC node or Hyperliquid SDK integration.

## Known failure modes

- Invalid or malformed contract address returns an error or empty result
- Contract address not deployed on Hyperliquid returns not-found response
- Network timeout or upstream Hyperliquid RPC unavailability causes failure
- Payment not provided or insufficient USDC results in 402 payment required

## 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 structured token metadata for the specified Hyperliquid contract address, typically including the token name, symbol, number of decimals, and other on-chain identifiers associated with that contract.

## 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-hyperliquid-token-metadata-9afbec66/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)