Etna Alpha

Five-minute integration

Get from packet shape to first live loop without reading the whole API map.

Engineers can wire deterministic mock packets before payment, then swap the same route shape to live latest, Workbench, replay, feedback, and usage after API-plan key issuance. The goal is one useful packet loop, not the full API map on day one.

01

Mock packet

Wire the response shape without using live market-state capacity.

02

Latest packet

After checkout, call live latest with the x-market-state-api-key header.

03

Workbench

Open evidence, replay context, row joins, routes, and feedback handles.

04

Usage receipt

Review cost and capacity before expanding symbols or replay depth.

curl "https://api.etnaalpha.io/api/public/market-state/mock/latest?symbol=BTCUSD-PERP"
const base = "https://api.etnaalpha.io/api/public/market-state";
const headers = { "x-market-state-api-key": process.env.ETNA_API_KEY };

const latest = await fetch(`${base}/latest?symbol=BTCUSD-PERP`, { headers })
  .then((response) => response.json());

const workbench = await fetch(
  `${base}/packets/${latest.rows[0].event_id}/workbench`,
  { headers },
).then((response) => response.json());

Best first system path

Pro is the default when the integration needs repeated context.

Builder is enough to verify BTC and ETH. Pro is the first active workflow for dashboards, agents, alerts, and internal monitors that need five approved symbols and repeatable packet review.

What this resolves

The first integration should prove the packet loop, not every feature.

For agents

Pass a read-only packet brief with state, reasons, evidence, replay, and allowed routes.

For dashboards

Show the latest packet and Workbench link instead of rebuilding the market read from raw flow.

For research

Use replay and export routes after the first packet loop is working and metered.