Monitor
Monitor
A standing watch on what you care about. Your agent doesn't poll; your webhook gets a POST.
What a monitor is
A monitor is a standing travel-disruption query SeaWeb keeps evaluating after you disconnect: chosen location + disruption types + minimum severity + webhook + end date. When it matches, your endpoint gets a signed POST. Create and stop monitors from the dashboard, or use the MCP tools in the agent reference.
The contract, in full
- Every monitor has an end.
stop_at(ISO-8601) is required at create. No monitor runs forever. - Webhook delivery is HTTPS only. One webhook URL per account receives events matched by that account’s active standing queries.
- Deliveries are signed. Browser setup shows the signing secret once; monitor lists never return it.
- Alerts inform, never execute. A monitor tells you something changed. It never books, buys, or acts on your behalf.
- Stop means stop. Stopping or reaching
stop_atremoves the standing query. The account webhook remains reusable for another monitor. - Growth required to create. Creating one commits SeaWeb to standing work. Listing and stopping your own monitors remains available after a plan change.
What it watches today
The live monitoring surface is travel disruption only: standing queries over geo areas for strikes, weather, closures, unrest, health, infrastructure, and safety events. Each emitted event is structured, severity-scored, and grounded in quoted source spans.