Skip to content

Robotics data

Robotics data: what the review checks, and how to license yours

Rightmark reviews robot and machine records: teleoperation and demonstration logs with synced cameras, joint states and force readings, and factory sensor data with commands, responses and faults. You start with a few answers on the appraisal and a description of each collection in words, with no files yet.

A robotics review starts on the Robotics path of the appraisal: answer a few questions about the data and send them for review. Then describe each collection in words through the contact page: what it holds, the robots and sensors, the labels, the format and who holds the rights. Rightmark asks for a sample only after the review, under NDA.

  • For teleoperation logs, the appraisal's Robotics path lists robotics lab license and paid collection contracts as routes, and says timing depends on the buyer and is confirmed after review. Rightmark,
  • A venture firm's analysis calls the shortfall of robot training data the central bottleneck in physical AI today. Stellaris VC, (opens in a new tab)

Updated

On this page

What fits: synced, labeled robot records

Robot and machine records: teleoperation and demonstration logs with synced cameras, joint states and force readings, and factory sensor data with commands, responses and faults.

  • Labeled failures and recoveries, and calibrated multi-camera views.
  • Commands and responses logged together, with labeled faults and maintenance notes.
  • Many machines in one format, over long histories.

First-person task video, filmed from the head or chest while people work with their hands, fits too. It goes through the Video and images path of the appraisal, and the first-person video page covers it.

What does not fit, or needs a flag first

Say so in the description if any of these apply.

  • Logs from robots at customer sites when the deployment contract gives the customer the rights.
  • Proprietary robot designs: share logs and video, not designs.
  • Machine data an equipment maker's or customer's contract already claims.

What the review checks

The review asks these questions first.

What the review checks (table)
CheckWhat the review looks for
Robot and handsThe robot, whether it moves on a base or stays in place, how many arms it has, and the gripper or hand on each arm.
CamerasHow many cameras there are, where each one sits, such as on the head, on a wrist or in a fixed view, and whether the calibration files are kept.
Robot state and actionsJoint positions and the commands sent, recorded throughout each episode, and whether actions are joint moves or end-effector moves.
Time syncWhether the cameras, the robot state and the other sensors share one clock, so every frame lines up with what the robot did.
Other sensorsForce and torque, touch, depth and audio streams, kept with the video rather than dropped.
Tasks and labelsTask names, a plain-language instruction for each episode, and where each step of a task starts and ends.
Failures and recoveriesWhether failed attempts are kept and labeled, and how the robot or the operator recovered.
Quality checksWhat was checked before delivery, and how much of it a person checked.
Format and deliveryWhether episodes come in one consistent, documented format that loads without your own tools.
RightsWho holds the rights to each collection, and whether a customer, partner or equipment contract claims any of it.

For first-person video

  • Where the camera is worn: on the head, the chest or a wrist.
  • How often hands are at work in frame, counted on a random sample of clips.
  • How many people, places and countries the video covers.
  • Which labels exist today, such as hand poses, task names or narration.
  • Whether faces, voices and home interiors appear, and how they are masked.

What to put in the description

Write it in your own words, one collection at a time, and send it through the contact page, where a person on the Rightmark team reads every message. A blank is better than a guess: the review asks about what is missing.

  • What the collection holds: teleoperation, demonstrations, autonomous runs or first-person video, and the tasks it covers.
  • How much there is: episodes or hours, and the total size.
  • When and where it was recorded, and where it is stored now.
  • The robots, cameras and other sensors, as in the checks above.
  • The labels that exist today, and whether failed attempts are kept.
  • The format it is stored in, and how a copy would be delivered.
  • Whether people appear on camera, and how their consent was recorded.
  • Who holds the rights: your company, a partner or a customer, and under which contract.
  • Whether you can record more of the same, and how quickly.

If Rightmark asks for a sample

Rightmark asks for a sample only after the review, and reports and samples stay under NDA. Take the sample from across the collection, so its tasks, sites and robots appear in about the shares the collection holds.

What to send

  • Whole episodes with every stream they recorded: all cameras, the robot state, the actions and the other sensors.
  • The calibration files and a description of the format, so the episodes load without your tools.
  • Failed attempts and recoveries, not only clean successes.
  • The labels and quality notes as they exist today.
  • Copies made for the review, never your only masters.

What to leave out

  • Logs from robots at customer sites when the deployment contract gives the customer the rights.
  • Proprietary robot designs: share logs and video, not designs.
  • Machine data an equipment maker's or customer's contract already claims.
  • Footage of identifiable people without their consent, unless their faces are masked first.

What comes back after the review

Rightmark reviews your answers against the Price Index and public deal records, and replies with a verified range, the likely routes and the next steps.

A range always comes with a confidence level. Indicative estimate, not an offer. A firm offer can follow after an NDA and due diligence.

How a license works

  1. You answer a few questions on the Robotics path, send them for review, and describe each collection in words.
  2. If a collection fits, Rightmark asks for a sample, under NDA.
  3. With your approval, Rightmark offers the collection for license on the route that suits it, such as a robotics lab license.
  4. You approve each agreement: what is licensed, for how long, and what happens to the data at the end. Nothing is licensed until you sign.

Can you record new data to order?

If you can record new data to a brief, say so: for teleoperation, the appraisal's Robotics path lists paid collection contracts as a route. Be ready to answer:

  • Which robots you run or can match, and how many.
  • Which capture rigs and sensors you can deploy, and how they are synced and calibrated.
  • How many hours or episodes a week you could commit.
  • How long it takes from a signed brief to the first delivered batch.
  • What the quality report for each batch contains.

Know a company with robot data?

If you know a company that runs robots, teleoperation rigs or first-person capture, you can introduce it as a Rightmark Scout. Rightmark decides fit at review, so a Scout never tells the owner that the data fits.

Questions

Should I send files or a sample now?

No. Start with a few answers on the appraisal and a description in words of each collection: what it holds, the robots and sensors, the labels, the format and who holds the rights. Rightmark asks for a sample only after the review, under NDA.

Do failed attempts count?

Yes. Label failures and recoveries; they are scarcer than successes. Keep each failed episode with a label for what went wrong and how the robot or the operator recovered.

Does first-person video of people at work fit?

Yes. It goes through the Video and images path of the appraisal, not the Robotics path. People on camera must have agreed to be filmed, or their faces are masked before delivery.

What about logs from robots at customer sites?

Say so in the description. Deployment contracts decide who holds those logs, and some laws give users rights over data from connected products, so the review reads those terms first. Logs the contract gives to the customer do not fit.

Do I need to share my robot's designs?

No. Share logs and video, never your hardware designs. The review needs the recordings and how they were made, not the hardware behind them.

Can we record new data instead of licensing what we hold?

Yes. For teleoperation, the appraisal's Robotics path lists paid collection contracts as a route. Say which robots and rigs you can run and how much you could record each week, and the review starts from there.

Sources

  1. Rightmark: Appraisal
  2. Stellaris VC: Physical AI Has a Massive Data Problem (opens in a new tab)

Start a robotics review on the appraisal.

Answer a few questions about the data, send them for review, then describe each collection in words. No files yet.

Find out what your data could be worth.

Start with an indicative appraisal. No files or system access needed.

Appraise your data

What brings you to Rightmark?