Question 1

How is Operant different from buying an open dataset?

Accepted Answer

Open datasets rarely match your robot, sensors, or deployment environment. Operant designs capture around your evaluation goals, not a fixed catalog download.

Question 2

Do we own the data?

Accepted Answer

Yes. Engagements grant your organization ownership of captured data with terms documented during scoping.

Question 3

What sensors do you support?

Accepted Answer

RGB-D, LiDAR, IMU, force/torque, and proprioceptive streams are common. We finalize the sensor list on your discovery call.

Question 4

How long does a collection program take?

Accepted Answer

Pilots often run 2–4 weeks. Production scales over months depending on diversity targets and geographies.

Question 5

What happens on a discovery call?

Accepted Answer

We review your stack, behaviors, sensors, volume, and quality bar, then outline a pilot and commercial framework.

Question 6

How do you handle privacy and consent on site?

Accepted Answer

We follow your policies and applicable regulations with consent workflows and secure transfer agreed before capture.

Question 7

What deliverables and formats do you provide?

Accepted Answer

Time-synchronized logs, calibration files, metadata, and optional labels in formats your training pipeline expects.

Question 8

Who is Operant for?

Accepted Answer

Robotics and physical AI teams with defined milestones who need auditable real-world data, not generic bulk downloads.

Question 9

How is pricing structured?

Accepted Answer

Custom projects are scoped fixed-fee or milestone-based after discovery, aligned to environments, sensors, and volume tiers.

Question 10

What geographies can you operate in?

Accepted Answer

We run programs in North America and Europe by default; other regions are available with lead time for permits and staffing.

Question 11

Do you provide labeling and annotation?

Accepted Answer

Yes, label schemas, QA, and tooling integrations can be included when defined in scope.

Question 12

What do we need for a pilot?

Accepted Answer

Target behaviors, sensor list, a staging environment, and an engineering point of contact for format validation.

Question 13

How do you QA captured data?

Accepted Answer

Automated sync checks, sample review gates, and acceptance tests tied to the statement of work before scale.

Question 14

Will our project stay confidential?

Accepted Answer

NDAs and restricted-access delivery are standard for commercial robotics programs.

Question 15

Can data integrate with our sim pipeline?

Accepted Answer

We deliver metadata and formats compatible with sim-to-real workflows and can align episode IDs with your sim domains.

Question 16

Do you support ongoing collection after handoff?

Accepted Answer

Yes, retainer-style programs maintain diversity and refresh tail behaviors as your product evolves.

Question 17

Is there a minimum engagement size?

Accepted Answer

Pilots are designed to be meaningful but bounded; production scale follows proven pilot metrics.

Question 18

Do you provide robots or only operators?

Accepted Answer

We typically capture on client or lessor hardware; operator staffing and rigging are part of scope.

Question 19

Can you target specific failure modes?

Accepted Answer

Yes, failure taxonomy and sampling ratios are defined explicitly for eval-oriented programs.

Question 20

Do you support teleoperation programs?

Accepted Answer

Teleoperation and demonstration capture are core offerings with multi-camera synchronization.

Question 21

Is Operant a dataset marketplace?

Accepted Answer

No. Operant runs custom capture programs for your environments and robots, we are not a broker or off-the-shelf catalog.

Frequently asked questions

Getting started

Legal

Technical

Commercial

Operations