- Contracts decide ownership. A GreyOrange executive, writing in Automation World in October 2026, said customers usually keep raw data while vendors take a license to telemetry.
- Real robot interaction data cannot be scraped. Scale AI says DROID and Open X-Embodiment offer only about 5,000 hours combined.
- Buyers ask for synchronized camera, state and action streams, the robot type, calibration and a success label per episode.
- Shipping controlled technology abroad, or releasing it to a foreign person in the US, is an export under 15 CFR 734.13, so check before sharing control code with logs.
Who owns robot data under your customer and vendor contracts, and can it be licensed?
Robot data sits between at least three parties: the site where the robot works, the company that runs or integrated it, and the vendor that built it. Each has a contract with the others, and those contracts decide who may license the logs. Read them before anything else. The table sets out what the public record shows.
| Rule or source | What it says | What it means for you | Date checked |
|---|---|---|---|
| Column by a GreyOrange executive in Automation World (7 Oct 2026) | "The customer keeps title to raw data and facility specifics. The vendor takes a perpetual, royalty-free license to operational telemetry" | An integrator or operator may need the site customer's consent, and the vendor may already hold a license | 20 Nov 2026 |
| Same column, no-train clauses | No-train commitments are "often scoped to personal data rather than operational data" | Your vendor may already train on your fleet's operational data. Check before you license it as exclusive | 20 Nov 2026 |
| 15 CFR 734.13 and 734.7, export (EAR) | An export is "An actual shipment or transmission out of the United States", and releasing "technology" or source code to a foreign person in the US is a "deemed export"; published information is not subject to the EAR | Sending logs to a buyer abroad is an export. Logs alone are rarely controlled, but control code or design data shipped with them may be. Check classification | 20 Nov 2026 |
| Illinois BIPA, 740 ILCS 14/15 | A private entity needs written notice and a written release before it collects a biometric identifier, and may not "sell, lease, trade, or otherwise profit from" one | Face geometry or voiceprints derived from robot video of people in Illinois raise BIPA questions. Blur faces or leave such data out | 20 Nov 2026 |
| Scale AI on robot data (Sep 2025) | "Unlike text or images, robotic manipulation data can't be scraped from the web." | Real deployment data is scarce, which is why buyers pay to collect it | 20 Nov 2026 |
Sources: Automation World, 15 CFR 734.13, 15 CFR 734.7 and the Illinois Biometric Information Privacy Act, read on 20 November 2026; Scale AI's blog is listed in the sources below. For the vendor side in detail, see factory data rights in automation vendor contracts. This page is general information, not legal advice.
Can you sell robotics data for AI training?
Yes, and demand is real, but most deals are licenses, not sales. A fleet operator, integrator or robotics company grants an AI lab the right to train on copies of its logs and keeps the data. Who can grant that right is the first question. A company that builds and runs its own robots in its own facility owns its logs outright. An integrator running robots at a customer's warehouse usually needs the customer's agreement, because the logs show the customer's site, products and people.
Logs also carry things other than robot motion. Camera streams show workers, product labels and floor layouts. Maps reveal a building's plan. Error logs can expose a vendor's software. Each of those raises a separate permission question, so a license often covers a cleaned subset: joint states, actions and task outcomes, with video filtered or blurred.
Can you sell or license robot teleoperation data?
Yes, and it is the kind buyers ask for most. Teleoperation data is recorded while a person controls the robot remotely. Fortune reported on 10 November 2026 that Physical Intelligence "has tested combining human video with teleoperation data, which is recorded as people control robots remotely". A remote operator's corrections show the robot what to do when its own policy fails. See the glossary entry on teleoperation data for the term itself.
Two consents matter. The operators: if they are your staff, their employment terms and your privacy notice should cover recording and licensing their sessions; if they are contractors, their contract should. And anyone else on camera: workers and visitors at the site who appear in the robot's video. Where you cannot show notice and consent for the people in frame, blur faces or license only the non-video streams. In Illinois, the Biometric Information Privacy Act requires written notice and a written release before a business collects a "scan of hand or face geometry" or a "voiceprint", so never derive those from site video without counsel.
Interventions are worth keeping. The moments when a human took over, and why, are labeled examples of failure and recovery. A log that records each takeover with a reason code is more useful than hours of uneventful autonomous operation.
What do AI labs ask for in robotics data?
Open datasets show the format labs expect. Open X-Embodiment pooled data "from 22 different robots collected through a collaboration between 21 institutions, demonstrating 527 skills". DROID holds "76k demonstration trajectories or 350 hours of interaction data, collected across 564 scenes and 84 tasks". Both value variety: many robots, many places, many tasks.
The common file layout is set out in the LeRobotDataset v3 docs: "signals (states, actions, timestamps) stored in Apache Parquet", "Camera frames concatenated and encoded into MP4", and metadata describing schema, frame rates and episode boundaries. A buyer will ask four things of your logs.
- Modalities: which cameras (wrist, head, fixed), at what frame rate, plus joint states, actions, force and torque, and gripper state, all on one clock.
- Embodiment: the robot model, arm and gripper, and the control interface, because a model must know which body produced the data.
- Calibration: camera intrinsics and extrinsics and the robot's kinematic description, so actions line up with what the cameras saw.
- Success labels: whether each episode succeeded, with failure and intervention points marked, plus a short task description in plain language.
Real or simulated robot data: which do buyers want?
Real data is the scarce one. Scale AI wrote in September 2025 that DROID and Open X-Embodiment, two of the largest open datasets, "offer only about 5,000 hours of interaction data combined". That is Scale AI's count of those two datasets, not of all open robot data. Companies that run robots in production hold far more. PitchBook reported that Agility Robotics "has said it has trained its robots on more than 65,000 hours of real-world operation". That is a company claim, reported by PitchBook.
Simulation can generate data in volume, so a buyer will not pay much for synthetic episodes it could make itself. What it cannot make is the messiness of a real site: odd lighting, worn parts, unexpected objects and people walking through. A fleet operator's logs from real shifts are worth more for exactly that reason. Simulation logs still help when they come with matching real runs, because the pair shows where the simulator was wrong.
Some world-model labs train on gameplay rather than robot logs; our General Intuition review covers one such lab and what it publishes.
Teleoperation data or kinesthetic teaching: what is the difference?
Teleoperation means controlling the robot remotely, with a VR controller, a 3D mouse or a leader arm. Kinesthetic teaching means physically moving the robot's arm by hand while it records. A 2025 study on demonstration modality found that kinesthetic teaching "provides cleanest data for best downstream learning performance" but "is not preferred as the way for large-scale data collection due to the physical load".
The same study notes that "the majority of existing manipulation datasets were collected through teleoperation". For a seller, that means teleoperation logs fit the formats buyers already use, while kinesthetic demonstrations are rarer and cleaner but usually small. Label which method produced each episode.
Robot data collection services or licensing: what is the difference?
A data collection service records new data to order. A lab specifies the tasks and robots, and the service hires operators or contributors to record them. Fortune described one model in which "contributors take paid video-recording tasks to help train robots". The lab pays for labor and usually owns the result. Licensing is the reverse: you already hold the logs from running your business, and you grant rights to copies. For human first-person video, see selling video footage for physical AI and how robots learn from video.
An operator can do both. Logs from normal operation are licensed as they are, and the same fleet can record extra tasks to a buyer's specification for a separate fee.
Encord does both: it pays for recorded hours of real work and says it also buys data companies already capture. Our Encord review quotes those pages and what to settle before recording starts.
How do I start selling robotics data?
We help you license your data. Origin Data Partners is an independent data partner that helps business owners value and license their company records: the company pays Origin nothing, and a buyer may pay Origin when a deal completes. For a fleet operator or integrator the work usually runs like this.
- Count what you hold: robot models, hours logged, sites, tasks, camera setup and how long logs are kept before deletion.
- Read the customer site contracts and the robot vendor's terms for data ownership, telemetry licenses and no-train clauses.
- Check consent for operators and anyone on camera, and decide whether video is licensed, blurred or left out.
- Check export classification for any control code, design data or technical documents that would ship with the logs.
- Convert a sample of a few hundred episodes to a common format with calibration, embodiment notes and success labels.
Plant historians and PLC data have their own guide, licensing PLC, SCADA and historian data. When you have a rough count, check what your robot logs may be worth. Not the owner? Advisers can introduce the company.
How we checked this
We read every source on this page on 20 November 2026: the federal export regulations (15 CFR 734.13 and 734.7) on the official eCFR site, the Illinois Biometric Information Privacy Act on the state legislature's site, the research papers behind Open X-Embodiment, DROID and the demonstration-modality study, the official LeRobot documentation, Scale AI's own blog, reporting by Fortune and PitchBook, and an Automation World column by an executive of GreyOrange, a robotics software vendor.
What we could not verify: any price paid for licensed robot fleet logs, because no buyer or seller has published one we could find; the terms of individual robot vendor contracts beyond what Automation World quoted; and company claims about hours of data, which we report as claims.
Who buys robotics data?
Robot foundation model builders and AI labs. PitchBook reported that "AI labs like OpenAI, which has been hiring for robotics roles, are among the buyers for this data". Scale AI wrote in September 2025 that it is "already providing and enriching data for leading Physical AI companies, including Physical Intelligence, Generalist AI, Cobot, and others". Fortune reported in November 2026 that Physical Intelligence has tested combining human video with teleoperation data.
The pool is small, and it may not stay open. Sam Padilla, whose physical AI startup Eidon shut down this year, told PitchBook that "the buyer pool is tiny". He also said demand for collected data will fade, because as more robots are deployed "they can collect their own data". A small pool means each offer deserves a careful read, and exclusivity should be priced, not given away. Check any offer against what to review in a data licensing offer. Names here are dated market facts, not recommendations. Sources: PitchBook and Fortune.
Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.
Common questions
What does teleoperation mean in a robotics data license?
Teleoperation is a person controlling a robot remotely, and teleoperation data is the record of it: camera video, the operator's commands, the robot's joint states and the result. In a license it is usually its own category, because it shows how a human solved a task and carries extra consent questions about the operator. Label each episode as teleoperated, autonomous or mixed.
Do we need operator consent to license teleoperation video?
In practice, yes. Operators are recorded at work, and their voices, hands and sometimes faces appear in the data. Their employment or contractor terms and your privacy notice should cover recording and licensing those sessions. Workers and visitors who appear on the robot's cameras need the same thought. Where consent is unclear, blur faces or license only the robot's own sensor and action streams.
Can an integrator license data from robots it installed at customer sites?
Only with the right contracts. Published robotics terms often leave the site customer with title to raw data, so an integrator usually needs the customer's written agreement before licensing logs from its site. The robot vendor's terms may also give the vendor a license to telemetry. Read both, and expect to share proceeds or anonymize the site when the customer agrees.
Does export control apply to robot logs?
Rarely to the logs themselves, but check what ships with them. Under 15 CFR 734.13, sending items out of the US is an export, and releasing controlled technology or source code to a foreign person inside the US can be a deemed export. Information already published without restriction is outside the rules (734.7). Control software, design files or manuals bundled with a dataset may need classification first.
What format should robot logs be in for a buyer?
A common choice is the open LeRobotDataset layout: states, actions and timestamps in Parquet files, camera frames encoded as MP4 video, and metadata describing schema, frame rates and episode boundaries. Whatever the format, every stream should share one clock, each episode should carry a success label, and calibration files should travel with the data so a buyer can line up actions with images.
Are failed episodes and human interventions worth including?
Yes, often more than the successes. A failure followed by a human takeover shows where the robot's policy breaks and how a person recovers, which is what training needs most. Mark the moment of each intervention and, if you can, a short reason. Strip only episodes that show people or customer information you cannot license.
Sources and further reading
- Automation World: Who owns what robots learn? (7 October 2026)
- 15 CFR 734.13: Export (eCFR)
- 15 CFR 734.7: Published (eCFR)
- Illinois General Assembly: Biometric Information Privacy Act, 740 ILCS 14
- Scale AI blog: Expanding our data engine for physical AI (24 September 2025)
- arXiv: Open X-Embodiment, robotic learning datasets and RT-X models
- arXiv: DROID, a large-scale in-the-wild robot manipulation dataset
- Hugging Face docs: LeRobotDataset v3
- arXiv: How to train your robots? The impact of demonstration modality on imitation learning (2025)
- PitchBook: Physical AI's data boom is a race to get out of the data business
- Fortune: In the race for robot training data, a startup turns to gig workers with cameras (10 November 2026)
