CityAlert

License the incident feed

CityAlert.live continuously ingests police, fire and EMS open-data feeds, disaster and weather alert agencies, and geocoded media reports across hundreds of regions — then deduplicates, categorizes and normalizes it all into one stream. That stream is what the map, the alerts and the API all read from, and it's available to build on.

The hard part of this data is collection and normalization — hundreds of upstream formats, schemas and reliability quirks, handled. If your product needs to know what's happening where, you can start reading it in the next five minutes.

Who it's for

Newsrooms & local media

A metro-level incident wire that never sleeps: police CAD calls, fire dispatches, road closures and geocoded reports arriving in minutes. Use it as an assignment-desk feed, publish per-city Atom feeds alongside coverage, or iframe a live incident widget into articles.

Per-city Atom feeds and the embed widget are free with attribution; the API adds search, history and bulk pull for data desks.

Security & operations teams

Push incident alerts into your ops channel instead of watching a map. Outbound webhooks POST filtered incident batches to Slack, Discord or any HTTPS endpoint — geo-fenced by bbox, severity and category, with cluster mode for event-driven notifications.

The Business alerts plan delivers to 25 team endpoints; the Pro API tier adds webhook delivery at 50k requests/day.

Insurers, real estate & risk analysts

Historical incident records are the asset here: the archive holds every incident every feed has returned — queryable by region, category, bbox and date range — plus per-city crime-year datasets and trend endpoints for year-over-year comparisons.

Developer-plan keys unlock the archive and deep history; Pro adds the trend and crime-year tools via API and MCP.

Municipalities & public agencies

A white-label deployment of the whole platform — your city's feeds, your branding, residents get the same live map and alert experience. Includes feed integration for your open-data portal where one exists.

Municipal plans start at $1,500 CAD/yr — see the municipal page for scope and the demo request path.

Ways to consume it

  • REST API

    GeoJSON incidents with region/category/bbox/date filters, the full historical archive, trends and per-city crime-year datasets. Self-serve keys, metered per UTC day — see the developer docs.

  • Outbound webhooks

    Instead of polling, register HTTPS endpoints that receive signed incident batches matching your region/category/severity filters — with bbox geo-fencing and a cluster mode that fires a single alert when a threshold of matching incidents accumulates. Built for ops-channel delivery.

  • Per-city Atom feeds & embeds

    Every city page publishes an Atom feed of recent incidents, and the embeddable widget drops a live incident summary into any page — free with attribution.

  • White-label / municipal

    The full platform branded and fed for your city — see municipal plans starting at $1,500 CAD/yr.

API tiers

  • Free

    60 requests/day — shared ~15-minute snapshot (responses carry meta.delayed); real-time refresh, archive, deep history and MCP history tools require a paid plan.

  • Developer — $99/mo

    5,000 requests/day — GET /api/archive; days>7 on /api/incidents; real-time refresh.

  • Pro — $499/mo

    50,000 requests/day — everything in Developer; get_trends + get_crime_year MCP history tools; outbound webhook delivery.

Anonymous use gets the shared ~15-minute snapshot. Free keys are instant — sign in and create one under Account → API keys; paid tiers upgrade through Stripe on the same page and can be cancelled any time via the billing portal.

Get a free API keyCompare all plans →

What the license covers

  • Free tier: personal and evaluation use with attribution — cite CityAlert.live and the upstream source on each incident.
  • Paid API tiers: commercial use in your product or internal tooling — dashboards, apps, alerting pipelines, research.
  • Redistribution: republishing raw incident data at volume — e.g. a competing feed or a public dataset resale — needs a written license; reach out below.
  • Media-sourced incidents are approximate block-level locations — preserve that caveat wherever you republish them.
  • This is an aggregation and awareness feed. For emergencies your users should always defer to official authorities.

Bulk, custom & enterprise

Need a bulk export, a dedicated region, guaranteed SLAs, an on-behalf integration or redistribution rights? Tell us the use case and volume — [email protected] or the contact page. For municipal deployments the municipal page has the dedicated scoping path.