Set up Sentry alerts

Two facts that shape this entire guide:

Sentry has no subscription mechanism. No endpoint, no tool, no concept. Watches are configured server-side and read by polling.
On a master checkout the sentry module is absent, so all three tools return module_absent.

What Sentry watches

The control plane, not the price: mint authority, upgrade admin, freeze capability, ownership. Chains: ethereum, base, bsc, solana.

1. Confirm what is monitored

list_active_watches()

An empty list means nothing is being watched — not that nothing has changed.

2. Establish a baseline

check_authority_snapshot(chain="base", subject_id="0x...")

A change event only means something relative to a baseline that was actually captured. A subject with no prior snapshot has no history, and “no changes recorded” for it is not a statement about stability.

3. Poll for changes

get_watch_history(subject_id="0x...")

4. Build delivery yourself

Since nothing pushes, delivery is your loop:

import time

STATE = {}

def poll():
    watches = list_active_watches()
    if watches["state"] != "ok":
        alert_ops(f"Sentry unavailable: {watches['reason']}")   # <-- the important branch
        return

    for w in watches["data"]["watches"]:
        history = get_watch_history(subject_id=w["subject_id"])
        latest = history["data"]["events"][:1]
        if latest and latest[0]["id"] != STATE.get(w["subject_id"]):
            STATE[w["subject_id"]] = latest[0]["id"]
            dispatch(latest[0])

while True:
    poll()
    time.sleep(300)

The alert_ops branch is the one that matters. A monitoring loop that silently returns when the module is absent is a loop that reports “all clear” forever while watching nothing.Alert on the monitor being down at least as loudly as on a change it detects.

5. Dispatch to a chat surface

The workspace API pushes to a connected chat client:

Connect a destination

POST /integrations/slack/connect

Also available for discord and teams. See Slack.

Test it

POST /integrations/{id}/test

Confirm delivery before relying on it — a misconfigured destination fails silently at exactly the wrong time.

Dispatch

POST /integrations/dispatch

This is one-way into a chat client. It will not call an arbitrary URL of yours — there are no webhooks. See Webhooks.

Alert design

Alert on the monitor, not only the subject

“Sentry has not reported in 30 minutes” is a more urgent alert than most authority changes.

Rate-limit your poll

100 calls/minute across all tiers. A loop over 200 watches at 60s intervals exceeds it.

Alternative: dashboard alert rules

For price and signal conditions rather than authority changes, the dashboard has its own alert path:

POST /api/alerts/preview

Free tier alerts are delayed 15 minutes; Pro is real-time. See Pricing.

Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.

Get Started

Concepts

Guides

Set up Sentry alerts

What Sentry watches

1. Confirm what is monitored

2. Establish a baseline

3. Poll for changes

4. Build delivery yourself

5. Dispatch to a chat surface

Alert design

Alert on the monitor, not only the subject

Rate-limit your poll

Alternative: dashboard alert rules

​What Sentry watches

​1. Confirm what is monitored

​2. Establish a baseline

​3. Poll for changes

​4. Build delivery yourself

​5. Dispatch to a chat surface

​Alert design

Alert on the monitor, not only the subject

Rate-limit your poll

​Alternative: dashboard alert rules

What Sentry watches

1. Confirm what is monitored

2. Establish a baseline

3. Poll for changes

4. Build delivery yourself

5. Dispatch to a chat surface

Alert design

Alternative: dashboard alert rules