COVERAGE/KRAKEN
Phase 3 · 2028 · planned, subject to a data agreement

Kraken

Kraken is planned for Phase 3, 2028, subject to a data agreement with Kraken. The plan covers spot pairs, including fiat quotes, and perpetuals, at every depth from L2 to L4.

Phase32028
StatusPlannedsubject to agreement
Capture2regions
Matrix5of 6 columns

What we plan to offer on Kraken.

Coverage of Kraken begins once a data agreement with Kraken is in place, and the final scope follows that agreement.

SPOT · PLANNEDSpot markets

All spot pairs, including USD, EUR, GBP, CAD, JPY and CHF quotes.

PERP · PLANNEDPerpetuals & futures

Linear multi-collateral and inverse perpetuals.

FUND · NOT PLANNEDFunding

Not planned at launch.

L2 · PLANNEDL2 depth

Full-depth snapshots and deltas, merged across two regions by venue sequence number.

L3 · PLANNEDL3 order events

Order adds, modifies and deletes, plus fills, normalized to the shared event types.

L4 · PLANNEDL4 attributed flow

L3 plus a participant id, if the data agreement with the venue includes participant-level data.

How we plan to capture Kraken.

Once a data agreement with Kraken is in place, we capture Kraken independently from two regions and merge the two streams by venue sequence number, as we do for every venue. Production capture starts at least 90 days before early access, so depth history covers three months or more on day one.

Venue type
Centralized exchange
Funding interval
Not planned at launch
Integrity
Venue sequence numbers, and book checksums where the feed includes them, verified at capture
Snapshots
A full-depth book snapshot at the top of every UTC hour (the 00:00 snapshot opens each daily file), plus the venue's own snapshots on reconnect, flagged with is_snapshot and snapshot_reason
Timestamps
Microseconds in ts_exchange. ts_capture is int64 nanoseconds from a PTP-disciplined clock.
Regions
Two independent regions, assigned once the data agreement is in place
Participant id
Offered if the data agreement includes participant-level data
Marketvenue_symbolsymbol
SpotXBT/USDBTC-USD
SpotETH/EURETH-EUR
Linear perpetualPF_XBTUSDBTC-USD-PERP
Inverse perpetualPI_XBTUSDBTC-USD-INV-PERP

Kraken uses XBT for bitcoin in some symbols. symbol always uses BTC; the native spelling stays in venue_symbol. Multi-collateral perpetuals are quoted in USD, hence BTC-USD-PERP. The full rules are in symbology.

  • Asset codes such as XXBT and ZUSD are mapped to BTC and USD in instruments.
  • Fiat pairs in six currencies are kept as separate instruments, so BTC-USD and BTC-EUR never mix.
  • Spot and perpetual instruments share one instruments table, with the market type in instruments.venue_market.

Where history starts.

The history available for Kraken depends on the agreement with Kraken. Data we capture ourselves starts on the first day of production capture, which begins once that agreement is in place.

TableOfferedHistory fromsourceNote
trades●Per agreementfdc_capture
candles●Per agreementfdc_capture
quotes●Per agreementfdc_capture
book_l2●Per agreementfdc_capture
book_l3●Per agreementfdc_capture
book_l4●Per agreementfdc_captureIf the agreement includes participant-level data
funding○··Not planned at launch
open_interest●Per agreementfdc_capture
liquidations●Per agreementfdc_capture
mark_index●Per agreementfdc_capture
extended●Per agreementcomputed from fdc_capture
instruments●Per agreementvenue reference data
gaps●Per agreementfdc_capture

History for Kraken follows the agreement with Kraken. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.

Derived fields on Kraken.

Extended fields are computed on ts_capture and published on a 100 ms grid. A field is available on a venue when its source data is.

KeyNameFromOffered
ofi_mlOFI-MLL2●
vpinVPINtrades●
queueQUEUEL3●
cxl_fillCXL/FILLL3●
resilRESILL2●
lambdaLAMBDAtrades●
markoutMARKOUTtrades●
partPARTL4●

Query it.

The same calls work on every venue; only venue and symbol change. Endpoints go live with Phase 1, and the v1 spec is a draft until then.

from fdc import Client

fdc = Client(api_key="fdc_live_...")

# L4 order events with participant ids
book = fdc.book(
    venue="kraken",
    symbol="BTC-USD",
    depth="L4",
    start="2028-09-04",
    end="2028-09-04T01:00:00",
)
df = book.to_polars()

Compare with.

All 12 venues

Shape what ships next.

Pre-registered partners vote on which venues and datasets ship first. Add Kraken to your pre-registration to register your interest.

EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →