Alert rules
Build rules over probability, 24h move, volume, expiry, or UMA status. Active rules show on this page; firing rules surface as a banner on Home; the triggered-history list at the bottom records every past firing.
Delivery channels
Alert rules and the firing history are stored locally in your browser. In-app banners on Home fire as soon as any rule is satisfied. Server-side email cron is fully implemented and runs every 5 minutes; deliveries currently land in structured logs (dry-run) until RESEND_API_KEY is set on production. Subscribed rules will resume real delivery with no UI change the moment the channel flips on.
Email digest
dry-run · channel not yet configuredMirror your local alert rules to a server-side cron so digests keep firing while your tabs are closed. Only price / change-24h / volume / expiry / UMA-status rules deliver server-side today — watchlist, theme, wallet, and signal-fired rules stay client-only. The cron evaluates every 5 minutes and writes a structured log entry per fired rule. Email delivery activates as soon as the channel goes live — your subscription will keep working without changes.
No server-eligible rules yet — create a price / change-24h / volume / expiry / UMA-status rule below to enable the digest.
Create alert
From any marketQuick start · market presets
1Target
Search by question text, category, or slug. The list filters the top 300 markets by 24h volume.
2Condition
3Delivery
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 20 retained.
- · When fired
- · Market & condition
- · Delivery (in-app / email)
Advanced automation · Webhook deliveryConfigure
Power-user automation. When any of your alert rules fire in this browser, Orrery POSTs a stable JSON payload to every active endpoint below. Fully client-side — no server-side delivery yet, so an endpoint only fires while an Orrery tab is open. Use it for personal Zapier/n8n hooks, Discord webhook URLs, custom Lambda Function URLs.
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" }
}