Skip to main content
Use this page for a high-level view of sources in the Polaris catalog, grouped by venue category. For exact market identifiers, time bounds, and live availability, use Catalog.

Coverage by category

These tables are a point-in-time snapshot of the complete, paginated GET /catalog response from api.polaris.supply, refreshed on August 27, 2026 at 20:37:03 UTC. The snapshot contains 3,723 markets across 50 sources. Market counts, source IDs, example market IDs, and access states come directly from catalog metadata. Access states:
  • Open means the listed markets are broadly accessible through Polaris.
  • Preview exposes a bounded public range around public_cutoff_date; other dates may require an API key or upgraded access.
Catalog snapshot: 2026-08-27T20:33:10.112Z. Counts and access states can change after this timestamp. The options tables were refreshed from the public Catalog at 2026-08-29T15:40:40.625Z; other categories retain the snapshot above.

Hyperliquid + HIP-3 DEXes

This category includes the Hyperliquid core book and HIP-3 builder-deployed DEXes that run their own markets on Hyperliquid’s order book. HIP-3 market IDs are namespaced by builder, with prefixes such as xyz:, cash:, and io:.

Perpetual and order-book exchanges

This category covers other perpetual and order-book venues, including CLOBs across L2s and app-chains, spot markets, real-world asset (RWA) markets, prediction markets, and compute markets.

Options exchanges

Options markets use the underlying asset as the catalog market ID. Each market can contain many venue-native option contracts; see Option Tickers for the distinction between a market and an instrument. Paradex appears here and in the preceding table because its catalog coverage includes both options and perpetuals.

PropAMMs

PropAMM sources publish standardized quote-ladder events for the ethereum market. See PropAMM Quote Ladders for the shared event schema and source-specific contract metadata.

Intent and RFQ venues

Intent sources use intents as their catalog market ID. See Intents and RFQs for the canonical event shape.

How to use this page

  • Use the source ID and an example market ID together when you build an API or SDK request.
  • Use the market count to compare the breadth of each source within its category.
  • Use the access column to distinguish open markets from preview markets.
  • Always confirm the exact source and market pair in Catalog before you build requests because catalog coverage changes over time.
  • Use the API overview if you know the market but not the right delivery surface.

Next steps