byte_subscription_health
Read-onlyIdempotent
Detect when a publisher pivots content or goes dormant by comparing recent 7-day activity against a 23-day baseline. Returns stability signal: stable, moderate, significant, or unknown.
Instructions
Get the content-drift signal for a publisher. Compares their last 7 days of publishing activity (cadence, message count) against their 23-day baseline (days 8-30). Returns 'stable' (steady publishing), 'moderate' (20-50% cadence shift or 24-48h silence), 'significant' (>50% shift or >48h silence), or 'unknown' (new publisher, insufficient baseline). Use this to detect when a publisher you subscribe to has pivoted content or gone dormant.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| publisher | Yes | Publisher address to check | |
| indexerUrl | No | Optional indexer URL override |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| publisher | No | Publisher address checked | |
| signal | No | Content-drift bucket for the publisher | |
| messages7d | No | Messages in the last 7 days | |
| messages30d | No | Messages in the last 30 days | |
| messages_7d | No | Messages in the last 7 days (indexer key) | |
| messages_30d | No | Messages in the last 30 days (indexer key) | |
| silence_hours | No | Hours since the last message (null if never) | |
| cadence_drift_bps | No | Cadence drift vs 23-day baseline (bps) | |
| volume_ratio_bps | No | 7d/baseline volume ratio (bps) |