Packet example

Routine packets matter because feedback needs an object.

The product is not only dramatic alerts. Ordinary reads stay structured so teams can separate useful changes from noise and improve routing.

Replay preview Routine/noise window The public page shows that quiet reads stay reviewable instead of disappearing into loose alerts.

After checkout latest -> feedback -> usage receipt Pro turns noise review into a repeatable watchlist and routing-tuning loop.

API calls GET /latest · POST /feedback/packet · GET /usage/estimate Keep ordinary packet outcomes available for agents, monitors, and threshold tuning.

DOGEUSD-PERPmarket_state.v1

State: Routine / noise case
Tags: quiet flow, stable depth, feedback ready
Reasons: No major pressure or fragility change crossed the current review threshold.
Confidence: Calibrating, evidence attached
Routes: Feedback, watchlist tuning, usage receipt

{
  "packet_type": "market_state.v1",
  "symbol": "DOGEUSD-PERP",
  "state": "routine_noise_case",
  "tags": ["quiet_flow", "stable_depth", "feedback_ready"],
  "reasons": [
    "no major pressure change crossed the review threshold",
    "ordinary packets remain reviewable for routing feedback"
  ],
  "evidence": {"workbench": "/packets/{event_id}/workbench"},
  "replay": {"route": "/replay?symbol=DOGEUSD-PERP"},
  "routes": ["feedback", "watchlist_tuning", "usage_receipt"]
}

From packet proof to live API

Pick the live loop that matches the workflow.

Routine packets matter when feedback, thresholds, and routing need a stable object. Paid plans unlock live packets, Workbench evidence, replay context, webhook tests, feedback, and usage estimates.

Builder BTC + ETH first loop Use when the immediate goal is proving one live packet loop before adding broader symbols. Pro Five-symbol active workflow Best fit for DOGE watchlists alongside BTC, ETH, SOL, and HYPE workflow coverage. Research Noise review at scale Active launch universe, longer replay, exports, and heavier packet-set review.