Strategy Alerts

Consume persisted Mist strategy alert events through backend APIs. Fetch pending alerts and record delivery success or failure without evaluating strategy rules or querying datasource services.

mist-trade Updated

File contents

Strategy Alerts

Consume strategy alerts already generated by the Mist backend scheduler or manual strategy scan APIs.

Helper Functions

Import the shared helpers from an environment where shared/ is available:

from shared.strategy_alerts import (
    list_pending_strategy_alerts,
    mark_strategy_alert_delivered,
    mark_strategy_alert_failed,
)

Consumption Flow

  1. Call list_pending_strategy_alerts() to fetch events from /v1/strategy-alert-events?status=pending.
  2. Deliver the alert through AstrBot or the active bot runtime.
  3. On success, call mark_strategy_alert_delivered(event_id, delivery_result).
  4. On failure, call mark_strategy_alert_failed(event_id, delivery_result).

delivery_result should be a small object such as:

{"channel": "astrbot", "messageId": "msg-1"}

or:

{"channel": "astrbot", "error": "bot unavailable"}

Guardrails

  • Do not execute strategy rules in AstrBot.
  • Do not query datasource, raw provider, TDX, or QMT APIs.
  • Do not create strategy signals from this skill.
  • Treat operator acknowledgement as a separate backend/UI action.

mist-trade/mist-skills/tree/main/skills/strategy-alerts commit 3faf173ab2

Frequently asked questions

npx skillmds@latest add mist-trade/strategy-alerts