Skip to main content
Base URL:

​
Health

Returns service status and the public endpoint list. The production health payload currently advertises:

​
Analyze Frame

Form fields: Query params:

​
Analyze Timestamp

Extracts a frame from the configured source video and runs the same spatial analysis path as frame upload. The hosted VPS does not bundle the full source video, so this endpoint can return 404 or 503 in production. Use /cii/frames or /eval for hosted, cached evidence. Query params:

​
Analyze Batch

Body:
Runs timestamp analysis for up to 32 events. Each event must be an object with a numeric timestamp_s in the 0 to 3600 second range.

​
Demo

Local convenience endpoint that runs five fixed timestamps against the configured video. On production, the full source video is intentionally not bundled; the endpoint returns 503 video_unavailable with alternate endpoints: /api/cii/frames, /api/cii/summary, and /api/eval.

​
CII summary

Returns Productive, Contributory, and Non-Contributory counts and wrench-time percentage. Current production summary is 30 total frames, 26 productive, 0 contributory, 4 non-contributory, 86.7% wrench time, and 11 raffle tickets.

​
CII frames

Returns the cached per-frame CII classifications.

​
Spatial Zones

Returns zone-level productivity metrics and a short spatial narrative.

​
Eval

Returns temporal eval claims, proof-frame citations, and baseline comparison. The payload includes a source field: reference when served from the bundled fallback and live after a successful temporal run.

​
Temporal Frame

Serves extracted temporal frames referenced by /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

Runs live temporal reasoning with cooldown protection. The frontend falls back to cached reference results if live inference is paused or unavailable. 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.