Choose Your Workflow - Trio

Endpoint Selection

If you need…	Use
A fast yes/no answer right now	`POST /check-once`
Condition detection over time	`POST /live-monitor`
Periodic narrative summaries	`POST /live-digest`

Delivery Mode Selection

Delivery mode	Best for	How to use
Synchronous JSON	Immediate answers	`POST /check-once`
Polling	Backend workers and scripts	Create job, then `GET /jobs/{job_id}`
Webhook	Event-driven automation	Send `webhook_url` in request body
SSE	Real-time client updates	Send `Accept: text/event-stream`

Practical Recommendations

Start with check-once to validate condition wording.
Move to live-monitor when you need trigger detection over time.
Use live-digest when you need summaries, not binary triggers.
Choose polling first for simple backend workflows.
Add webhooks or SSE when you need push delivery.

Delivery Behavior by Endpoint

`POST /check-once`

Returns one JSON result.
No job lifecycle to track.

`POST /live-monitor`

webhook_url present: webhook mode.
Accept: text/event-stream and no webhook_url: SSE mode.
Otherwise: polling mode (job_id + GET /jobs/{job_id}).

`POST /live-digest`

Accept: text/event-stream and no webhook_url: SSE mode.
webhook_url present: webhook mode.
Otherwise: polling mode.

Next Steps

Polling implementation: Use Polling
Webhook implementation: Use Webhooks
SSE implementation: Use SSE Streaming

First Successful Workflow Common Setup Issues