Cross-market assets

The same underlying exposure can appear under different tickers on different venues. Pulse maintains a canonical asset registry so cross-market questions (“which venues trade gold?”, “total OI on BTC across all dexes?”) return one coherent answer instead of needing you to dedup symbols yourself.

Vocabulary

Canonical — the economic-exposure identifier. Examples: GOLD, BTC, OIL.
Symbol — what appears on a specific venue. Examples: GOLD (native HL spot), xyz:GOLD, hyna:PAXG (a historical, legacy-dex symbol).

The registry maps every symbol to its canonical, including documented synonyms where two tickers track the same exposure.

Venue lists cover native Hyperliquid, xyz and the legacy dexes (flx, vntl, hyna, km, abcd, cash; delisted, zero open interest). io, mkts and para are not in the asset directory yet.

Known synonyms

Symbol	Canonical	Why
`PAXG`	`GOLD`	PAXG is gold-backed
`XAUT`	`GOLD`	XAUT is gold-backed
`XAGT`	`SILVER`	XAGT is silver-backed

Resolving symbols to canonical

The asset endpoints accept either form — canonical names or any symbol that resolves to one:

# Both return the same asset's venue breakdown
GET /assets/GOLD
GET /assets/PAXG     # resolves to GOLD
GET /assets/xyz:GOLD # also resolves to GOLD

The MCP tool equivalents (list_asset, pulse_cross_market_asset) accept the same flexible input.

Cross-market aggregation

When you want total exposure across every venue that trades an asset, use pulse_cross_market_asset. It joins per-venue live position breakdowns (longs, shorts, notionals, bias, unique wallets) onto the venue list and returns per-venue rows plus a roll-up.

GET /assets/BTC/cross-market

Sample shape:

{
  "query": "BTC",
  "resolvedCanonical": "BTC",
  "asset": { "canonical": "BTC", "synonyms": [], "crossMarket": true, "venueCount": 2 },
  "aggregate": {
    "totalOpenInterest": ..., "longPositions": 13071, "shortPositions": 10392,
    "longNotional": ..., "shortNotional": ..., "netBias": 0.114, "biasRange": 0.077,
    "totalUniqueWallets": ..., ...
  },
  "venues": [
    { "dex": "hl",  "symbol": "BTC",     "longPositions": 12431, "shortPositions": 9802, "netBias": 0.118, ... },
    { "dex": "xyz", "symbol": "xyz:BTC", "longPositions": 640,   "shortPositions": 590,  "netBias": 0.041, ... }
  ]
}

netBias here is position-count bias, (long - short) / (long + short). totalUniqueWallets is summed per venue, not deduplicated. An omitted venue metric means unavailable, not zero.

When to use canonical vs venue symbols

Question	Use
”What’s the BTC mark price on `xyz`?“	venue symbol (`xyz:BTC`)
“Which venues trade gold?“	canonical (`GOLD`)
“Total OI on BTC across all dexes?“	canonical (`BTC`) → cross-market
”Is PAXG the same as GOLD?“	resolve via `list_asset`
”Show me cohort bias on `xyz:SILVER`”	venue symbol (live data is per-venue)

Live position / cohort data is always per-venue — live_cohort_bias expects a specific symbol, not a canonical. Use cross-market endpoints only when you explicitly want the aggregation.

Discovery

Tool / endpoint	Returns
`list_assets` / `GET /assets`	Full directory of canonicals with their venue lists; also returns `venues`, the builder dexes the directory covers
`list_asset` / `GET /assets/:c`	One canonical’s venue breakdown (accepts synonyms)

Getting started

MCP

Concepts

Vocabulary

Known synonyms

Resolving symbols to canonical

Cross-market aggregation

When to use canonical vs venue symbols

Discovery

​Vocabulary

​Known synonyms

​Resolving symbols to canonical

​Cross-market aggregation

​When to use canonical vs venue symbols

​Discovery

Vocabulary

Known synonyms

Resolving symbols to canonical

Cross-market aggregation

When to use canonical vs venue symbols

Discovery