Metadata on every item
Short clips and brand films, each with duration, resolution, content type, and collection ID.
Short-form and brand video, vlog, 4K stock and camera-movement footage, sports clips with three-level temporal annotation, and egocentric sessions with seven annotation types — each item shipped with structured metadata.
Short clips and brand films, each with duration, resolution, content type, and collection ID.
4K stock footage plus FPV, aerial, and handheld camera-movement sets, organized by shot type.
Clip, phase, and action annotated on one timeline, with timestamp tables in JSONL.
Master video, proxy, and annotated preview per session: actions, arm pose, camera motion, hands, objects, hand–object interaction, and keysteps.
Clip-level instruction pairs for video-understanding training.
| Annotation layer | What it marks |
|---|---|
clip · phase · action | Three nested temporal levels, each with start and end times. |
arm_pose | Arm posture spans within a session. |
camera_motion | Movement type per span. |
hands · objects | Hand and object references tied to the same timeline. |
hand_object_interaction | Contact and manipulation spans. |
keysteps | Procedure steps, in order, inside a session. |
| Stage | How it is used |
|---|---|
| Continued pre-training & alignment | Footage and egocentric sessions with synchronized annotations. |
| SFT | Clip-level instruction pairs for video understanding. |
| Evaluation | Held-out clips with reference labels. |
| Layer | Contents |
|---|---|
| manifest.json | Every file with name, size, date, and collection ID. |
| UTF-8 JSONL | One record per line for text and annotations. |
| Documents | Data card, field schema, and a PDF spec for each collection. |
| Original + proxy media | Master files at capture resolution, plus proxy files for review. |
Tell us the source type, annotation layers, and volume. We reply within one business day. Sample packs, data cards, and field schemas are shared after your request is reviewed.
Annotations carry start and end times in seconds. Granularity is confirmed per collection before delivery.
Yes. Each source type is a separate collection, so projects often start with one and extend after acceptance.
Annotation fields, sampling, and delivery format can be adjusted to your pipeline.