Etna Alpha

Retained packet stories

Packet stories that make the market-state API tangible.

Each example shows the same buyer object: state, tags, reasons, confidence posture, evidence route, replay context, and workflow routes. The point is not a screenshot. The point is retained packet lineage your systems could inspect, route, replay, and challenge live after API-plan key issuance. Recurring delayed public tape appears only when public packet rows are available.

Loading retained public packet stories. Static packet examples remain available if the proof route is unavailable.

BTCUSD-PERP

Pressure building

Book pressure rose while visible depth thinned across the review window.

Open BTC packet
HYPEUSD-PERP

Crowding shift

A logged state change with evidence and replay context, not a loose alert.

Open HYPE packet
ETHUSD-PERP

Fragile depth watch

Research and operations get a compact packet set they can replay and audit.

Open ETH packet
DOGEUSD-PERP

Routine / noise case

Ordinary packets stay reviewable so feedback can separate useful changes from noise.

Open DOGE packet

From packet story to live API

Choose the first loop your system will actually run.

Use public packet stories to verify state, evidence, replay, and route semantics. Then start the paid live plan that matches your symbol coverage and workflow depth.

Builder BTC + ETH first loop Live latest packet, Workbench, replay, webhook test, feedback, and usage receipt for the first two symbols. Pro Recommended live loop Five approved symbols for agents, dashboards, alerts, and repeated packet review. Research Replay/export workload Active launch universe, longer replay windows, exports, and heavier research loops.

Recurring proof surface

Use the public tape to understand the object before paying for live access.

For outreach and evaluation

Send one packet page, not the whole homepage. A buyer should see what changed, why the state attached, and which live loop would use it.

For technical diligence

Open the proof path, mock workflow, and docs after the packet page. Raw JSON stays available for builders, but the product is the packet.

For paid activation

Paid plans unlock current timing, account-scoped symbols, Workbench evidence, replay depth, route receipts, exports, and usage limits.

Buyer paths

Send the packet to the workflow the buyer already recognizes.

The same packet can sell different jobs: agent context, desk monitoring, research replay, or content/KOL explanation.

Agents Market context for systems Give an agent a bounded read with reasons, evidence, replay, and allowed routes. Desks Five-symbol review loop Keep a watchlist open, route changes, inspect receipts, and review replay windows. Research Replay and export context Compare tagged packet behavior across symbols, events, and available history. Monitor Operate the packet loop Open the hosted surface that carries latest, Workbench, replay, route, feedback, and usage together. Integration Wire the first system loop Mock before key, then live latest, Workbench, replay, and usage after checkout.
Open Workbench preview Start this packet loop live Inspect proof path View integration path