Etna Alpha

Agent workflows

Give agents market state they can inspect.

Etna Alpha returns a compact market_state.v1 packet with state, tags, reasons, confidence, evidence, replay, routes, feedback, and usage context. The agent starts from a bounded market read instead of trying to reconstruct context from venue events on every run. The same read-only context path is the right shape for MCP: latest packet, Workbench evidence, replay, freshness, and usage resources without order, billing, or execution authority.

Agent without Etna

The model receives event exhaust and has to guess the read.

Trades, depth, timestamps, and book changes arrive as ingredients. The workflow still has to decide what changed, what evidence matters, whether replay is available, and where the result should route.

events -> prompt glue -> uncertain context
Agent with Etna

The model receives the packet plus the path back to evidence.

The packet can be summarized, routed, challenged, replayed, or joined to rows without letting the agent invent a market read from partial context.

packet -> reasoned brief -> route / replay / feedback
Agent input market_state.v1
State
Pressure building
Reasons
What changed and why the label attached.
Evidence
Workbench and row handles stay connected.
Replay
The same event can be reopened later.
Routes
Agent brief, dashboard, webhook, feedback.
{
  "agent_context": "market_state_packet",
  "symbol": "BTCUSD-PERP",
  "state": "pressure_building",
  "agent_brief": {
    "what_changed": "pressure rose while visible depth thinned",
    "why_it_matters": "monitor, replay, and route context are attached",
    "allowed_actions": ["summarize", "route", "request_replay"],
    "forbidden_actions": ["execute_trade", "custody_funds"]
  },
  "evidence": "/packets/{event_id}/workbench",
  "usage": "metered account receipt"
}

MCP-ready context

Expose market context to agents without handing them execution.

Resources

Latest packet, packet history, Workbench evidence, replay context, public proof, freshness, watchlist state, and usage posture.

Boundaries

Read-only by default: no orders, no custody, no billing mutation, no private key handling, and no provider-data redistribution.

First path

Wire deterministic mock context, then switch the same resource names to live packets after API-plan key issuance.

Best first loop

Start with Pro when the agent needs repeated live context.

Builder is enough for a BTC/ETH proof loop. Pro is the natural first active workflow when an agent, dashboard, or alert system needs five approved symbols, replay, webhook tests, and daily packet review.

Proof object Open BTC packet Show the agent the exact state, reasons, evidence, replay, and route shape. Recommended Start Pro loop Five approved symbols for active agent, dashboard, alert, and review workflows. Implementation Read quickstart Wire mock packets before a live API-plan key is issued. MCP / system path Use five-minute integration Start with mock context resources, then switch to live latest and Workbench after checkout.