Sentinel Docs
Simple reference for sources, logic, auth, delivery, and routes.
Contents
A signal request is an HTTP wrapper around one `definition` object. Keep delivery, cooldown, and metadata outside the DSL itself.
name
Human label for the signal.
definition.scope
Chains, markets, addresses, and protocol.
definition.window
Evaluation lookback window.
definition.logic
Top-level `AND` or `OR` across conditions.
definition.conditions[]
The actual checks Sentinel evaluates.
delivery | webhook_url
Managed delivery or explicit override.
cooldown_minutes
Minimum gap between repeat notifications.
Source of truth
Example request
POST /api/v1/signalsContent-Type: application/jsonX-API-Key: sentinel_... { "name": "High Utilization", "definition": { "scope": { "chains": [1], "markets": ["0xM"], "protocol": "morpho" }, "window": { "duration": "1h" }, "logic": "AND", "conditions": [ { "type": "threshold", "metric": "Morpho.Market.utilization", "operator": ">", "value": 0.9, "chain_id": 1, "market_id": "0xM" } ] }, "delivery": { "provider": "telegram" }, "cooldown_minutes": 5}