Etna Alpha

Packet example

The BTC market read your systems should receive directly.

This is the shape Etna Alpha sells: a compact market_state.v1 object with state, reasons, confidence, evidence, replay, routes, and usage context attached. Your system starts from the market read instead of rebuilding it from venue flow every run.

Open in Monitor Open Workbench preview Mock the packet shape Use in agent workflow
Replay preview 30m review window The public page shows the shape; live access opens account-scoped replay cursors and Workbench evidence.
After checkout latest -> Workbench -> replay -> route The first loop should end with a usage receipt and one route or webhook test, not a vague API key.
API calls GET /latest · /packets/{event_id}/workbench · /replay Use the same packet identity across monitoring, review, and automation.

BTC tape to packet proof

Same move. From raw tape to market-state context.

Rows show what happened. Etna Alpha keeps the state, reasons, evidence, replay identity, and routes attached.

Provider rows BTC books, trades, timestamps, and context arrive as ingredients.

The live proof route fills in row counts and the remaining synthesis work.

Etna packet sequence BTC state path, event class, reasons, confidence, replay identity, and routes load from retained packet lineage.

Proof stays redacted and bounded; live packet routes remain after-key and metered.

Why this packet sells the API

A Pro loop turns this artifact into a live operating surface.

The public page proves the packet shape. Paid access makes the same read current, keyed, metered, replayable, and ready to route across the approved symbols your workflow actually watches.

What the buyer receives

A usable market read, not just the ingredients.

What changed

BTC moved into a pressure-building state while nearby depth became more fragile inside the review window.

Why it matters

The packet carries the label, reasons, confidence posture, and replay cursor as one reviewable object.

What routes next

A monitor, agent, webhook, dashboard, or notebook can consume the same packet and point back to the same evidence.

BTCUSD-PERP market_state.v1
State
Pressure building
Tags
crowding watch, depth fragile, replay ready
Reasons
Book pressure rose while visible depth thinned across the review window.
Confidence
Calibrating, evidence attached
Routes
Workbench, replay, webhook, feedback, usage receipt
{
  "packet_type": "market_state.v1",
  "symbol": "BTCUSD-PERP",
  "state": "pressure_building",
  "tags": [
    "crowding_watch",
    "depth_fragile",
    "replay_ready"
  ],
  "reasons": [
    "pressure rose inside the current review window",
    "visible depth thinned near the active price band"
  ],
  "evidence": {
    "workbench": "/packets/{event_id}/workbench",
    "rows": "/events/{event_id}/evidence"
  },
  "replay": {
    "cursor": "current_review_window",
    "route": "/replay?symbol=BTCUSD-PERP"
  },
  "routes": ["webhook", "agent_brief", "dashboard"]
}
01

Inspect the state

Read the compact state, tags, reasons, and confidence posture before wiring it into a workflow.

02

Open evidence

Use the Workbench/evidence routes to inspect why the packet was labeled that way.

03

Replay the window

Reopen the same event window for research, desk notes, follow-up alerts, or review.

04

Route the object

Send the packet to dashboards, agents, webhook consumers, notebooks, or internal receipts.

From packet proof to live API

Pick the plan for the loop you want to prove.

The packet page shows the artifact. Paid access turns that same shape into live latest packets, Workbench evidence, replay cursors, webhook tests, feedback, usage receipts, and first-packet setup support.

Open in Monitor Open Workbench preview Inspect proof path View mock workflow Start this packet loop live · Compare live plans