Venues in DQL
These are the venues a query can name today. The list is read from GET /v2/venues when this page is
built, not typed — so if a venue is missing here, it is missing from the language too.
| venue | name | listings | collected | since |
|---|---|---|---|---|
ASTER-PERP |
Aster Perpetuals | 644 | 26 | 2026-09-26 |
AVANTIS-PERP |
Avantis | 200 | 45 | 2026-09-26 |
BINANCE-USDM |
Binance USD-M Futures | 946 | 42 | 2026-09-24 |
BITGET-PERP |
Bitget Perpetual Futures | 884 | 22 | 2026-09-24 |
BYBIT-PERP |
Bybit Perpetuals | 930 | 42 | 2026-09-22 |
COINBASE-INTX |
Coinbase — legacy API, migrated | 264 | 24 | 2026-09-24 |
DERIBIT-PERP |
Coinbase Global Derivatives | 196 | 11 | 2026-10-12 |
DYDX-PERP |
dYdX v4 | 296 | 25 | 2026-09-24 |
EDGEX-PERP |
edgeX | 93 | 5 | 2026-10-11 |
GATE-PERP |
Gate Perpetual Futures | 1081 | 23 | 2026-09-24 |
GMX-PERP |
GMX v2 (Arbitrum) | 124 | 36 | 2026-09-26 |
HYPERLIQUID |
Hyperliquid | 561 | 194 | 2026-09-21 |
KRAKEN-FUTURES |
Kraken Futures | 219 | 98 | 2026-09-20 |
LIGHTER-PERP |
Lighter | 243 | 5 | 2026-10-11 |
MEXC-PERP |
MEXC Perpetual Futures | 1204 | 40 | 2026-09-24 |
NADO-PERP |
Nado Perpetuals | 83 | 21 | 2026-09-24 |
OKX-PERP |
OKX Perpetual Swaps | 543 | 29 | 2026-09-22 |
SYNTHETIX-PERP |
Synthetix Perps | 11 | 10 | 2026-09-26 |
WEEX-FUTURES |
WEEX Futures | 1042 | 24 | 2026-09-24 |
Read at 2026-11-11T12:24:01.693Z. Ask https://api.debyko.com/v2/venues for the list as it stands now; it needs no key.
listings is what the venue lists; collected is what the platform gathers. A listing that is not
collected can still be named in a query — it answers off, with the reason, rather than pretending to be
missing data. The difference between a choice and a fact is never merged here.
What a venue code is for
Section titled “What a venue code is for”A venue code is the platform’s, not the exchange’s. It is what you write in a query:
any(venues where venue = ASTER-PERP and funding > 0)The exchange’s own symbol for a listing — PF_XBTUSD, BTC-USDT-SWAP — is what you send to the exchange,
and it comes back in every answer as venue_symbol. The two are kept apart on purpose: one is the platform’s
vocabulary, the other is the venue’s, and confusing them is how a bot sends the wrong instrument.