Signals
Signal Catalog
The signals you can subscribe to, and the data each one delivers
GET
GET /signals returns the catalog — every signal, its allowed target types, and its sub-events. Use it to discover what you can monitor.
Signal payloads
Every signal is delivered with the unified envelope; below is thedata body.
post_engagement
New reactors and commenters on a watched author’s posts — your warmest pool.watch is the author’s profile URL. data:
baseline is true only for the one-time backlog batch delivered right after you start watching an author (see Pricing); false for ongoing engagement.
Only new engagers are sent (never the same person twice for the same post). new_comments includes replies — parent_comment_id is null for a top-level comment, otherwise the comment it replies to. A viral post arrives across several webhooks (chunk).
What’s monitored
For each watched author we track their 10 most recent posts. Every cycle we detect:- new posts (and their reactions/comments), and
- new reactions/comments on their older posts — as long as the post is still among the 10 most recent.
Pricing
post_engagement is usage-based, charged per engager delivered (each reaction or comment). You’re only charged for engagers actually delivered to you (deduplicated; never billed twice for the same person on the same post). Creating a monitor and watching an author are free.
| Rate | |
|---|---|
Backlog — existing engagement, delivered once when you start watching an author (baseline: true) | 0.2 credits / engager |
Go-forward — engagement that happens after you subscribe (baseline: false) | 0.5 credits / engager |
If you run out of credits, the monitor is paused automatically.

