Physical AI training data

Commission the egocentric demonstrations your policy is missing.

First-person human work, captured to your brief and delivered as rights-evidenced training data.

Machines are learning to work with their hands.

A robot learns a task the way a person does — by watching one.

The tasks people do without thinking are the ones machines find hardest.

Why this is hard

AI learned from the internet. The physical world was never on it.

A model can read every sentence ever published and watch every video ever uploaded, and still not know how much force a drawer needs. Physical intelligence is not written down anywhere; it is performed, by people, and then it is gone.

Language models

Billions of words

Already collected, already public. The corpus existed before the models did.

Vision models

Billions of frames

Images and video scraped from an internet that was already there. Again, found rather than made.

Physical AI

No corpus

Nothing equivalent exists. Egocentric capture of ordinary human work has to be recorded on purpose, by someone, with consent.

The first two were found. The third has to be made.

How it works

From one recording to a dataset.

Five steps, shown on a real clip we publish in full. Each one links to the page that explains it, and the whole method is on How it works.

Raw frame 150 of the reference clip, from the wearer's viewpoint: the left hand aligns and organizes fabric items on a workstation surface beside a sewing machine, the action the published annotation records for this segment. The same frame with FH-Ego v1 annotation drawn on: the left hand's 21 tracked joints, the connecting skeleton, its wrist triad axes, and a label giving per-hand confidence and the wrist position vector. Only the left hand is annotated in this frame. A header burnt into the image reads: Egocentric Bimanual Workstation Interaction, frame 150 of 1843, action organize_items.

50% annotated · raw at left, FH-Ego v1 overlay at right

Reference clip, sewing workstation · 21 3D joints per hand, left/right classified · the overlay is the engine's own output, untouched
  1. 1The recording arrives on our servers
  2. 2The face detector runs
  3. 3Faces it finds are blurred
  4. 4A person reviews the blurred copy

If the detector cannot run The recording stops at step 2, so no unblurred copy moves on.

— chunks · drawn at true frame positions · derived

FRAME 0276 / 1843 · loading…

The annotation engine's own output, on a clip we publish in full.

FRAME — / 1843 · — · — · speed — · conf — · loading…

sha256 of this file
—
file size
—
tracks
—
sampled every
— frames
Sampled every tenth frame by the pipeline, so the path is drawn point-to-point between sampled frames and nothing between them is invented. Positions and velocities are derived; they are the tracking model's own output, not an instrumented ground truth.

01 · Capture

A Capture Partner records the task.

For a commissioned brief, the task, the setting and the camera rig are fixed before anything is recorded. Drag the handle to compare the raw frame with the annotated one.

Consent receipt: none — recorded before the consent flow

How a recording is specified, consented and made

02 · Redact

Faces are blurred before anyone reviews it.

Faces the detector finds are blurred on our servers as the recording arrives. If the detector cannot run, the recording stops there, so no unblurred footage moves on.

What redaction covers, and what happens when it fails

03 · Segment

The recording is cut into labelled clips.

derived

Each clip carries an action code, so a dataset can be filtered by what happens in it. On this reference clip the cut is a fixed 120-frame window, shown at its true frame positions.

How one recording becomes usable clips

04 · Annotate

Both hands are tracked in 3D.

derived

21 joints per hand, each hand with a confidence score, on every tenth frame, so you can filter on quality rather than trust it. Drag the timeline to step through the sampled frames.

FH-Ego v1, field by field

05 · Deliver

You receive the files, and a hash that proves them.

Delivered as LeRobot v2.1, HDF5 or FH-Ego v1 JSON, with Zarr v2 and TFRecord on request. Rehash the annotation file you download and you get the digest shown here.

What arrives, and in what container

Catalogue

What you can commission.

Each brief below is a capture specification you can commission. Every one is delivered in one annotation schema, FH-Ego v1, so a dataloader you write once works across every delivery.

Price

A brief is scoped first, then priced against that scope.

Three things move the number, and each is fixed in the brief.

What moves the number · 1

The environment

An Indian household kitchen and an active distribution centre are not the same shoot. Access, scheduling and how many people have to consent all change with the room.

What moves the number · 2

The session

How long a session runs, how many of them, and how many Capture Partners the brief needs to reach the volume you are asking for.

What moves the number · 3

The annotation tier

Tier 1 is session metadata. Tier 3 is 21 3D joints per hand with per-hand confidence, and it costs more to produce and more to verify. You pick the tier in the brief.

Recording in India keeps a bespoke brief affordable.

Looking for paid recording work? This form is for labs buying data. Register as a Capture Partner →

For robotics and AI labs

Tell us what your robot or model must learn.
We’ll scope the dataset.

Describe the policy and the embodiment you are training it for. We scope the capture specification, price it against your volume and format, and come back with what we can commit to, including the parts we cannot. Our team reads every one of these.

What a brief costs is scoped before it is priced: how we price, and what moves the number.

Four fields are needed: your name, your work email, your lab, company or university, and what the data should teach your model. Add the two optional answers only if they are already decided.

Volume, timeline, the constraint that matters most. Whatever tells us whether we can help.

Prefer email? Write to labs@fourthuman.ai

When you send it, you get a reference id on screen, and usually a confirmation email. A person reads every brief, and we aim to reply within 1–2 business days. If our system cannot be reached, a button opens a pre-filled email to labs@fourthuman.ai instead.

FAQ

Frequently asked questions

Where does your data come from?
Every clip is recorded new, for a Capture Brief, by Capture Partners we recruit and pay in India. We never buy, license or resell footage from other vendors, data brokers or public datasets.
Why work with us?
Provenance you can check: every clip carries a consent receipt you can verify against our ledger, and any delivered release can be checked to show every clip in it is intact. One team runs the whole path, from capture through redaction, segmentation and annotation to delivery, so you receive format-ready training data rather than raw footage.
Is the annotation automated or human?
Automated: our engine annotates every clip to FH-Ego v1, our open schema. Every field a model generated is labelled derived in the schema, so model output is never presented as measurement.
How do you handle privacy and data protection?
Faces the detector finds are blurred on our servers before anyone reviews the footage, and a recording goes no further if the detector cannot run. Each Recording carries a consent receipt the Capture Partner can withdraw under India's DPDP Act 2023; what redaction covers and how we protect data are set out in full.