Source existing data
Browse by use case; review available subsets, sample fields and licensing.
Build a catalog shortlist →Home / Embodied AI data services
PHYSICAL AI · DATA & CAPTURE
Start with what your robot needs to learn. Align data sourcing, custom capture and equipment through task definition, a pilot, annotation and versioned delivery.
Review samples and licensing before confirming volume, price and schedule.
WAYS TO WORK
Browse by use case; review available subsets, sample fields and licensing.
Build a catalog shortlist →Define tasks, target embodiment, counting units and acceptance. Validate feasibility with a pilot.
Build a project brief →Explore TOBI equipment for your own capture, or use the partner channel for sites, expertise and capture capacity.
Compare capture equipment →Have data, sites or specialist services to offer? Explore expert and supplier collaboration →
CHOOSE THE DATA
The three paths need different hardware, fields and validation.
Study human workflows, scene semantics and interactions. Define observations separately from robot-action labels.
Record manipulation with a sensorized handheld gripper. UMI projects require feasibility review and trajectory validation for the target robot.
Record operator commands and robot states on specified hardware. Recheck interfaces and action space when the robot or control setup changes.
UMI is a public research method; project evaluation does not establish off-the-shelf availability. Method reference: Universal Manipulation Interface.
EVIDENCE BEFORE SCALE
A specification states requirements. Samples and checks establish what was delivered.
ILLUSTRATIVE DELIVERY STRUCTURE
batch_manifest.json episodes/episode_id/ observations/ timestamps/ calibration/ labels/ quality/checks.json metadata/data_card.json README + version notes
This is a discussion structure, not a delivered dataset. Agree fields, formats and acceptance thresholds for the project.
BUILD YOUR BRIEF
Prepare requirements here, then add contact details on the next page to submit to our team.
BEFORE YOU BUY
The catalog helps match requirements. Confirm usable quantities, duration, field completeness and permissions for a specific batch.
Public previews illustrate capture and processing. Raw files, annotations, licensing and model suitability require a separate review.
Cost depends on tasks, contributors, sites, sensors, embodiment, usable-episode requirements, annotation, rights and schedule. Agree counting units and a pilot before pricing.
Submit your configuration and tasks for review. Agree interfaces, synchronization, permissions, safe operation and acceptance before defining scope.