How to Access IncidentSource and Its Alerts

IncidentSource is accessible through three separate entry points, each serving a different need: the Radiant Glow platform for browsing AI-processed event intelligence, a Sign In option for returning users, and Squawster notifications for push-style alerts. An APIs link is also listed on the site for programmatic access. Which one you use depends on whether you want to browse events, receive alerts, or pull data into your own system.

The Three Access Paths

The homepage presents these options directly, and they are not interchangeable — each leads to a different capability.

Opening Radiant Glow

Radiant Glow is the platform itself — the interface where IncidentSource turns raw public safety radio traffic into structured event awareness. Selecting Open Radiant Glow is the path for viewing the live data rather than just receiving alerts.

Once inside, the platform organizes audio, event context, location, and escalation activity. The homepage preview of what this looks like shows a Recent Major Events table with columns for Date/Time, Major Event Type, Context, Location, and a View/Play action.

Signing In

The Sign In option is for existing users. The site does not state whether browsing Radiant Glow requires an account or whether sign-in unlocks additional features — if you need certainty on that, treat sign-in as the safe route for returning users and check the platform directly for guest access.

Getting Notified by Squawster

Get Notified by Squawster is the alert signup path. The homepage pairs it with the line "Squawster Incident Source alerts + Broadcastify audio in your pocket," which indicates alerts are delivered alongside Broadcastify audio. Choose this route if you want to be pushed major-event awareness instead of checking a dashboard.

APIs

The site lists APIs as a distinct option, described under "What we cover." This is the route for programmatic access — pulling event data into your own application or workflow rather than viewing it in the browser. The homepage does not publish endpoint details, authentication methods, or rate limits, so those would need to be confirmed after following the link.

What You'll See Once Inside

Understanding the data model helps you decide which access path fits. IncidentSource reports three live counters, all labeled "Last 24 hours":

• Signals: 170,447
• Events: 27,997
• Major Events: 768

The Recent Major Events view shows the last 20 major events with a stated 15 minute delay. Each row includes:

• Date / Time (UTC)
• Major Event Type — for example, MVA Extrication, Shooting, Structure Fire – Working Fire, Structure Fire – Multiple Alarm, Technical Rescue, MVA Major Roadway Shutdown
• Context — the responding agency, such as NC-Charlotte / Mecklenburg County Fire/EMS or AZ-Phoenix Fire
• Location — street address or block-level location
• View / Play — access to the underlying audio

This structure tells you what "event intelligence" means in practice: a classified event type, the agency context, a location, and playable source audio.

Choosing the Right Path

• If you want to browse and listen: Open Radiant Glow.
• If you already have an account: Sign In.
• If you want alerts without checking a dashboard: Get Notified by Squawster.
• If you're building something: Use the APIs link.

Practical Notes Before You Start

• Expect a 15 minute delay on the major events feed shown on the homepage. If your use case requires real-time awareness, account for that lag.
• Times are in UTC. Convert to your local timezone before acting on a timestamp.
• Locations can be approximate. Several entries show block-level addresses (for example, "12900 block Mysteria Dr") or intersections rather than exact addresses.
• The counters are rolling 24-hour figures, so they change continuously and are not cumulative totals.
• Pricing and account requirements are not stated on the homepage. Do not assume the platform or alerts are free — confirm terms after following the relevant link.