Perception by machine, judgment by human

Omni Responder is a computer vision tool that analyzes roadside camera footage to detect possible emergency situations and then notifies a human supervisor to investigate further.

Transport authorities operate many thousands of roadside cameras. Although the feeds are often broadcast publicly, few are regularly monitored by a human. This raises concerns about both privacy and effectiveness. Our tool addresses these by observing and processing footage on the edge in a local AI system that runs on the same network as the cameras. The only data that leaves the system is strictly focused on emergency response.

The benefit is that human attention is focused where it matters most.

A low-resource motion scan runs across the footage first, looking for moments where something changed and then stayed changed. These moments are then passed to a vision-language model, which describes the scene and rates the potential severity of the incident.

That description then fans out to three domain agents. One checks visible hazard indicators and returns isolation distances and protective-equipment levels. One drafts roadway closure and detour advisories. One assembles a dispatch brief of the kind an emergency call-taker would read. The result arrives as a live dashboard for human review and response.

All of the AI models run on a local device, the Nvidia DGX Spark. The footage is analyzed on that single machine, which could sit on the same network as the cameras, so no video is sent anywhere. Only information about a possible emergency is sent over the network.

Created along with Bilal Khan and Vishal Shah.

See it for yourself at GitHub.


Context

Omni Responder was built as part of the NVIDIA Spark Hack Series in Seattle, August 2026, on an NVIDIA DGX Spark. This device can hold a vision model and a video buffer in the same memory at the same time, which is what makes the local analysis practical.

Technical
Input Roadside traffic camera footage, decoded at one frame per second.
Detection Exposure-normalized pixel differencing over the whole clip to rank candidate moments — changes that persist rather than passing traffic. No model involved; this stage is deterministic and cheap.
Perception Candidate moments are sent as multi-frame bursts to NVIDIA Cosmos Reason 2, an 8-billion-parameter vision-language model served locally, which returns a written description, a severity rating, and visible hazard indicators.
Reasoning Rule-based orchestration fans the description out to three domain agents: hazardous-material lookup against the 2024 Emergency Response Guidebook, roadway closure and detour advisories, and a computer-aided-dispatch brief.
Output A live web dashboard and a Telegram alert to a human monitor: what was seen, how severe it appears, and what response the incident may call for.
Built with Python, ffmpeg, NVIDIA Cosmos Reason 2, NVIDIA NIM, NVIDIA DGX Spark (GB10 Grace Blackwell), FastAPI, Telegram Bot API
Sources

Video: project developed and trained using the roadside camera footage from the AI City Challenge 2021, Track 4 (traffic anomaly detection), together with additional traffic clips and simulated incident scenarios.

Hazard data: Emergency Response Guidebook (2024), U.S. Department of Transportation — used for UN substance numbers, isolation distances, and protective-equipment levels.