Health
Analyze Frame
| Field | Type | Required |
|---|---|---|
file | image file | yes |
| Param | Values | Default |
|---|---|---|
prompt | vima, baseline | vima |
timestamp | float seconds | 15.0 |
event_id | string | NC event candidate |
Analyze Timestamp
404 or 503 in production. Use
/cii/frames or /eval for hosted, cached evidence.
Query params:
| Param | Type | Notes |
|---|---|---|
timestamp | float seconds | required; must be finite and between 0 and 3600 |
event_id | string | optional label for the analyzed event |
cloud_path | string | optional local/reconstruction artifact path |
Analyze Batch
timestamp_s in the 0 to 3600 second range.
Demo
503 video_unavailable with alternate endpoints:
/api/cii/frames, /api/cii/summary, and /api/eval.
CII summary
CII frames
Spatial Zones
Eval
source field: reference when served from the bundled
fallback and live after a successful temporal run.
Temporal Frame
/eval when the frame path is
inside an allowed local artifact root. Most clients should follow the
vima.frame_urls values in the /eval response instead of constructing these
URLs manually.
Temporal Run
n must be between 1 and 12. A successful run writes
temporal-results.json, which means later GET /eval calls read the live run
until that file is replaced or removed. The endpoint returns structured error
payloads for cooldown, auth, timeout, and pipeline failures.