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 |
|---|---|---|---|---|
HYPERLIQUID |
Hyperliquid | 234 | 5 | 2026-09-21 |
KRAKEN-FUTURES |
Kraken Futures | 298 | 7 | 2026-09-20 |
Read at 2026-09-23T21:03:21.124Z. 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 = HYPERLIQUID 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.