DOCS · ORACLE FEED · PREVIEW

Oracle feed.

Aviax pushes per-flight outcome events on a continuous stream and exposes the same schema as a historical Parquet archive. Both surfaces share field names, types, and resolution semantics. The feed is the substrate that drives prediction-market settlement, parametric-insurance triggers, and quant-fund signal generation.

Streaming feed

WebSocket subscribe with filters. Events are pushed at three lifecycle moments per flight: at scheduled departure (mint), at any moment a delay threshold crosses (interim update), and at settlement-window close (resolution).

Sample resolution event (preview shape)

{
  "event": "resolution",
  "flight_id": "UAL1283-2026-05-07",
  "scheduled_departure": "2026-05-07T14:23:00Z",
  "scheduled_arrival":   "2026-05-07T18:11:00Z",
  "actual_arrival":      "2026-05-07T18:46:00Z",
  "delay_minutes":       35,
  "outcomes": {
    "delayed_15min": true,
    "delayed_30min": true,
    "delayed_60min": false,
    "cancelled":     false,
    "diverted":      false
  },
  "settlement_window_close": "2026-05-07T18:41:00Z",
  "signal_attestation": "ed25519:..."
}

Historical archive

Eight years of flight pattern data delivered as Parquet exports. Same schema as the live feed, partitioned by date, airline, and region for efficient backtest scans.

Use cases: training detection models, backtesting trading strategies, calibrating insurance pricing, validating settlement decisions retroactively.

Archive partition layout (preview)

s3://aviax-archive/v0/
  ├── year=2018/month=01/region=NA/airline=*.parquet
  ├── year=2018/month=01/region=EU/airline=*.parquet
  ├── ...
  └── year=2025/month=12/region=APAC/airline=*.parquet

Settlement window mechanics

Each binary contract has a deterministic settlement window. The window opens at the flight's scheduled departure and closes at scheduled-arrival plus a fixed reconciliation buffer (default: 30 minutes after scheduled arrival).

The reconciliation buffer absorbs late telemetry observations and final airline status updates. After the window closes, the outcome is frozen and signed; no further updates are accepted for that contract.

Signal attestation

Every resolution event carries an ed25519 signature over the canonical event payload. Pilot partners receive Aviax's public key out-of-band; consumers verify signatures locally before settling contracts on top of the data.

This lets prediction-market platforms verify that a settlement signal came from Aviax, audit it independently against the underlying telemetry archive, and detect any tampering between Aviax's signing infrastructure and their own settlement engine.

Rate limits and SLA

Documented at GA. The intent is sub-second event delivery for live streaming subscribers and 99.9% monthly settlement-on-time for pilot partners. Specific tier definitions and incident credits will be in the pilot agreement.

Request pilot access