The caller's own live watches -- what is currently subscribed on their customer, newest first, canceled ones excluded.

A "Watch this search" signup lands with a watch already installed, and this is where its owner confirms what it watches and which endpoint it delivers to. Not billable, like the other self-serve introspection reads (/webhook-deliveries): reading your own subscriptions is account management, not metered corpus access.

Each watch also reports fires_last_hour against its declared max_fires_per_hour, and rate_limited when the two have met: fires past that cap are DROPPED rather than queued, so this is the only place a saturated watch can be told from a quiet one.

And each reports its heartbeat -- last_fired_at, fires_last_7d, fires_last_30d and a one-word status -- so a watch that is silent because nobody is hiring reads differently from one that is silent because its criteria can never match, its plan stopped it, or its endpoint is down. Absence is the customer's only evidence a watch is mis-specified, and for a metered product it is also the receipt for the months where the honest answer is "nothing matched".

Requires the webhooks scope.