Labelled robot video, back before your next training run.
Send your recordings. Talo returns boxes, tracksA box drawn around one hand or object in every frame, kept under the same name from start to end., action segmentsA stretch of time with one action name, such as grasp or pour, and exact start and end times. and task descriptions in the schemaThe file layout and field names your training code already expects. your pipeline already reads.
Problem
Robot experiments stall while recordings wait for labels.
Labels come back with no rules and no check record.
Every export needs converting.
How it works
Labelling moves off your team's desk.
Today
- Record
- Wait for labelsStall
- Convert formatStall
- Train
With Talo
- Record
- Talo labels, checks and formats
Label. Boxes, tracks, action segments and task descriptions.
Check. Checked against the rules you agreed, with a check log.
Format. Delivered in the schema your pipeline already reads.
- Train
- 1
Send a brief
Robot, tasks, labels, a few clips.
- 2
Agree the rules
Action names, segment boundaries, what counts as failure.
- 3
Check a pilot batch
You review a small batch before any larger order.
- 4
Receive each batch
Your schema, with the rules and a check log.
One episode, as delivered
Pick up the bottle with the right hand and pour water into the cup.
- Tracks right hand, bottle, cup
- Segments 4, no gaps or overlaps
- Check 28 frames, 9 corrections logged
"segments": [
{ "start_s": 0.0, "end_s": 2.5,
"action": "grasp",
"description": "Right hand closes on the bottle." },
...
],
"review": {
"frames_checked": 28,
"threshold_px": 4,
"corrections": [ ... ]
}
Who it's for
Teams that train manipulation policies on video.
Academic robotics labs
Humanoid and robotics startups
Sample
Check our work before you talk to us.
A demonstration clip labelled by Talo for this site; not customer work. Read the demo format and limitations.

Loading annotations…
Loading method…
Loading details…
Case study