webhooks on the alpha MCP: signed POSTs when signals fire
polling on 5-minute intervals, a form 4 cluster completing at 14:01 UTC waits for the next tick to reach your agent. that gap is enough to miss the spread close.
shipped webhooks this week. when any of 4 event sources crosses your threshold, your endpoint gets a signed POST. payload mirrors the tool response. dedup by event id so the same cluster does not fire twice.
dispatcher runs every 5 minutes. 15s delivery window. one retry after 60s on failure. 3 failures flips the sub to failing and I get paged.
events at v1:
-
insider_cluster (3+ filers, form 4 verified buy)
-
confluence (2+ signals stacked on the same asset)
-
material_8k (items 1.01, 1.03, 2.01, 2.02, 4.02, 5.02, 8.01)
-
etf_flow_milestone (|net flow| > $50M)
signature: HMAC-SHA256 of body against your API key, in the X-FalsifyLab-Signature header. verify before you act.
I built this because my own bots were polling every 5 minutes and missing windows on signals the API already had. one in production fires on insider_cluster, calls confluence_today, and acts inside one agent loop.
Pro Plus is $49/mo and includes 1 webhook URL. EARLY50 takes 50% off the first 3 months, capped at 25 redemptions.
falsifylab.com/pro
— research and educational content. not investment, legal, or tax advice. do your own research. positions and views may change without notice.
Originally published on FalsifyLab Substack.
Looking for comments…
Searching Nostr relays. This may take a moment the first time this article is opened.
Looking for comments…
Searching Nostr relays. This may take a moment the first time this article is opened.