What is the VMukti Visual Bot API?
The VMukti Visual Bot API exposes the platform's 26+ on-board AI models — including ArcisGPT generative search, ANPR, facial recognition, crowd analytics, PPE compliance, and fire/smoke detection — as programmable autonomous agents. Developers and system integrators define a bot once (camera scope, schedule or trigger, inspection rule, output destination) and it runs continuously inside the VMukti cloud control plane without an operator at the console. Typical agents include hourly PPE-compliance sweeps of a factory floor, perimeter ANPR scans of a logistics yard, and ArcisGPT-driven daily incident summaries delivered to a customer's SOC. The API is REST + webhook, secured by OAuth2, and deployable in both commercial and NDAA-889-safe configurations.
What a Visual Bot is
A Visual Bot is an autonomous AI agent built on the VMukti platform. Each bot is a declarative specification:
- Camera scope — one camera, a site, a zone, or a fleet
- Trigger — schedule (cron) or event (motion, line-cross, third-party signal)
- Inspection — one or more on-platform AI models, optionally chained
- Output — webhook, email, ticket-system, ArcisGPT summary, ICCC alert
Common agent patterns
| Pattern | Models used | Example | | --- | --- | --- | | Scheduled compliance sweep | PPE, behaviour | Every hour, scan the loading bay and flag any worker without a hard hat | | Perimeter watch | ANPR, intrusion | When a vehicle enters the yard, run ANPR + watchlist check, alert the gate office | | Post-incident summarisation | ArcisGPT | When an alarm fires, generate a one-paragraph summary of the 10 minutes before and after | | Forensic recall | ArcisGPT, face | Search the last 30 days for a person matching a description | | KPI reporting | crowd, dwell | Daily report of footfall, dwell time, and queue length per zone |
Why it matters
Operators stop being the bottleneck. A SOC of three people can run hundreds of bots that each do the inspection work of one full-time monitor. This is the same productivity unlock as moving from manual log review to a SIEM — except for video.
Integration profile
- API style — REST + webhook, OAuth2 secured.
- Identity — service accounts with role-scoped permissions; bots run under their own identity for audit clarity.
- Deployment — commercial cloud, AWS GovCloud / Azure Government, or on-premise for air-gapped use.
- Compliance — every bot decision is logged with the model version, confidence score, and the frame(s) used as evidence — important for regulated industries and US federal deployments.
Where to start
Most customers begin with one of three first bots: PPE compliance, perimeter ANPR, or ArcisGPT daily summary. Each takes under a day to configure and immediately removes a recurring operator task.
Last reviewed: 2026-05-20