Watching a subject

A watch re-runs an analysis on an interval. Because change detection already runs inside every execution, a scheduled run produces a change report for free — that diff is the entire product of a watch.

curl -X POST https://api.molthood.org/api/v1/watches \
  -H "Authorization: Bearer mk_live_..." \
  -H "content-type: application/json" \
  -d '{
    "target": "token",
    "address": "0x5fc5360d04…",
    "label": "the one I keep an eye on",
    "interval_seconds": 3600
  }'

What it costs

The minimum interval is 15 minutes for this reason; the default is one hour. A one-minute interval would spend fifty units before lunch.

Scheduled runs skip the summary

The AI summary is over half the wall time, and hourly prose about a token that has not moved is pure cost. A monitored run produces the diff and stops there.

When a check fails

A failed check still records last_checked_at, or the watch would stay permanently due and retry in a tight loop against whatever is already broken. The reason is kept in last_error, so a watch that has gone quiet can say why rather than showing a stale timestamp that reads as "all clear".

Managing watches