Alerts

Alert rules

Build probability, volume, expiry, UMA, whale, and signal rules from one focused builder. Active rules stay here; fired rules surface on Home and in history.

Production delivery: in-app + server automation

In-app banners on Home fire as soon as any rule is satisfied. Server-side alert cron runs every 5 min: email digests send when the email channel is active, and user-provided webhook URLs are delivered from the server with retry, idempotency, and audit logging.

In-app banneractive
Emailactive
Webhookunsigned server
Telegramnot connected
Discordnot connected

Rule builder

Pick a target, choose the trigger, then decide where the alert should surface. Verification workflow only; never trade actions.

From any market

Templates

Market and watchlist rules

6 presets
1

Target

Search by question text, category, or slug. The list filters the top 300 markets by 24h volume.

2

Condition

¢
Server-side eligibleFires while your tab is open and from the server cron, even if the browser is closed.
3

Delivery

Telegram plannedDiscord planned

Will deliver

Active in-app bannerAvailable server webhook if an endpoint is attachedPlanned Telegram / Discord

Local history keeps the last 200 browser events; server audit uses the delivery log when configured.

Active rules

No active rules yet

Start with a preset or create a custom rule. When any rule fires, an in-app banner appears on Dashboard; email delivery ships next.

  • · Big 24h move — the absolute 24-hour change crosses a threshold.
  • · Resolution within 24h — market is about to settle.
  • · Volume surge — 24h volume crosses a threshold.
  • · UMA status flip — UMA dispute / settlement state changes.
  • · Whale trade — a single trade ≥ $10k lands.
  • · Signal fires — any research signal becomes active.

Triggered history

No triggers yet. Fired alerts appear here with a timestamp, the market, the condition that fired, and the delivery status — most recent 200 retained in this browser. The KV-backed server delivery audit log (last 1000 events, cross-device) lights up once KV is configured.

  • · When fired
  • · Market & condition
  • · Delivery (in-app / email)
Advanced automation · Browser-local webhookstab-open onlyConfigure
Webhook subscriptions · browser-localtab open only

Power-user automation. When any of your alert rules fire in this browser, Orrery POSTs a stable JSON payload to every active endpoint below. This browser-local path only fires while an Orrery tab is open. For closed-browser delivery, attach a server webhook in the Server delivery panel above.

Filter to kinds (optional — empty = all)

Payload format
POST <your-url>
Content-Type: application/json
X-Orrery-Event: alert.fired
X-Orrery-Schema: 1

{
  "type": "alert.fired",
  "schema_version": 1,
  "fired_at": "2026-04-30T12:00:00.000Z",
  "alert": {
    "id": "...",
    "rule_id": "...",
    "kind": "price_above",
    "threshold": 0.6,
    "message": "Probability 62¢ ≥ 60¢",
    "current_value": 0.62,
    "reasons": [...]
  },
  "market": {
    "slug": "...",
    "question": "...",
    "url": "https://orrery.me/markets/..."
  },
  "source": { "app": "orrery", "docs": "https://orrery.me/docs/agents" }
}
Alerts | Orrery