- Watched objects — what you’re tracking (ticker, query, URL, text).
- Alert rules — conditions on watched objects (
price_above,price_below,econ_release,gov_action,semantic_match). - Webhook endpoints — where alerts get delivered.
Add to watchlist
identify resolves a free-text query, URL, or ticker into a canonical watched object. The CLI handles dedupe and lifecycle.
Create an alert rule
| Condition | Trigger |
|---|---|
price_above | Yes price ≥ threshold (cents) |
price_below | Yes price ≤ threshold (cents) |
econ_release | FRED series prints (e.g., CPI release) |
gov_action | Bill / nomination / treaty status change |
semantic_match | LLM-classified content match |
active, paused, or archived. Test with sf alerts test <id>.
Register a webhook endpoint
Delivery and dedupe
Alert delivery is idempotent per rule, channel, endpoint, and window. A rule should not re-fire the same condition more than once inside its dedupe window. Webhook receivers should also idempotency-key onX-SF-Delivery-Id.
Runtime architecture
The evaluator runs server-side. It uses live market data where available and falls back to REST snapshots when needed. Users configure watched objects, alert rules, channels, endpoints, and dedupe windows; they do not need to run a local process for server-side alerts.Next steps
Watch + alert API
Endpoint shapes and curl examples.
Webhook events
Every event payload shape.
Webhook receiver
Verification + retry handling code samples.
Webhooks
Endpoint registration and signing.