# Operant

> Custom Data Collection for Robotics and Physical AI.

Operant designs and runs custom real-world data collection for robotics and physical AI teams, multi-sensor capture, teleoperation, and edge-case scenarios built to your spec.

Operant is **not** a dataset marketplace, catalog, or data broker. Every engagement is a custom capture program scoped to a client's robot, sensors, environments, and evaluation goals, delivered from pilot to production with documented provenance and data ownership.

## Services
- [Edge-Case Data Collection for Robotics](https://www.operantdata.com/services/edge-case-scenarios): Capture rare failures, near-misses, recoveries, and long-tail behaviors so evaluation reflects operational risk, not just clean demos.
- [Imitation Learning Data Collection](https://www.operantdata.com/services/imitation-learning-data-collection): Scope, capture, and QA robot demonstrations for imitation learning, with guidance on teleoperation, episode boundaries, labels, and evaluation.
- [Multimodal Robotics Data Collection](https://www.operantdata.com/services/multi-sensor-sync): Capture tightly synchronized RGB-D, LiDAR, IMU, force/torque, and proprioception data with documented calibration and drift controls.
- [Physical AI Data Collection](https://www.operantdata.com/services/physical-ai-data-collection): Real-world capture programs for physical AI, robots, sensors, environments, and evaluation slices that match deployment, not internet-scale proxies.
- [Robot Demonstration Data](https://www.operantdata.com/services/robot-demonstration-data): Capture demonstration data matched to your robot, environment, and evaluation goals, not generic datasets with mismatched action spaces.
- [Robotics Data Collection for Physical AI](https://www.operantdata.com/services/robotics-data-collection): Custom robotics data collection programs, teleoperation, synchronized sensors, edge cases, QA, and pilot-to-production delivery built to your spec.
- [Robotics Training Data](https://www.operantdata.com/services/robotics-training-data): A buyer-focused guide to robotics training data, demonstrations, teleoperation, synchronization, labels, evaluation slices, and deployment-fit collection.
- [Sim-to-Real Data Collection for Robotics](https://www.operantdata.com/services/sim-to-real-gap): Close simulation gaps with targeted real-world capture in lighting, contact, wear, and human-interference conditions that break policies after deployment.
- [Teleoperation Capture](https://www.operantdata.com/services/teleoperation-capture): Human-guided teleoperation and demonstration logging for imitation learning and policy fine-tuning, with multi-camera sync, metadata, and QA gates.

## Industries
- [Autonomous Vehicle Data Collection](https://www.operantdata.com/industries/autonomous-vehicles): On-road and closed-course multimodal AV capture for lighting tails, weather, interventions, and geospatially documented evaluation slices.
- [Humanoid Robot Data Collection](https://www.operantdata.com/industries/humanoid-robotics): Whole-body teleoperation, manipulation, locomotion, and recovery capture for humanoid training pipelines in homes, labs, and industrial settings.
- [Industrial Manipulation Data Collection](https://www.operantdata.com/industries/industrial-manipulation): Assembly, insertion, and material-handling capture in factory cells, with force/torque traces, vision occlusions, and tool-change episodes.
- [Warehouse Robotics Data Collection](https://www.operantdata.com/industries/warehouse-automation): Capture teleoperation, pick-place, AMR, pallet, and conveyor data in real warehouse settings with operational variability and synchronized sensors.

## Data scenarios
- [AMR aisle navigation with dynamic obstacles](https://www.operantdata.com/datasets/amr-aisle-obstacle-navigation): AMR navigation with dynamic obstacles in warehouse aisles
- [Autonomous driving rain and low-light LiDAR-camera](https://www.operantdata.com/datasets/av-rain-lidar-camera): Rain and low-light LiDAR-camera driving logs
- [Bin Picking Teleoperation Capture](https://www.operantdata.com/datasets/bin-picking-teleoperation-capture): Teleoperated bin picking from cluttered totes and mixed SKU bins
- [Defective SKU pick failure library](https://www.operantdata.com/datasets/defective-sku-pick-failures): Pick failures on defective or unusual packaging
- [Dual-arm kitchen manipulation in homes](https://www.operantdata.com/datasets/dual-arm-kitchen-manipulation): Dual-arm kitchen manipulation in residential environments
- [Humanoid home navigation and reach](https://www.operantdata.com/datasets/humanoid-home-navigation): Humanoid navigation and reach in furnished homes
- [Humanoid stair ascent and descent](https://www.operantdata.com/datasets/humanoid-stair-ascend): Humanoid stair climbing in public and residential stairs
- [Industrial peg-in-hole with force traces](https://www.operantdata.com/datasets/industrial-peg-insertion-force): Peg-in-hole insertion with force-torque sensing
- [Laboratory pipetting dexterity capture](https://www.operantdata.com/datasets/lab-pipetting-dexterity): Pipetting and micro-manipulation in lab benches
- [Outdoor rough-terrain locomotion](https://www.operantdata.com/datasets/outdoor-rough-terrain-locomotion): Rough-terrain legged locomotion outdoors
- [Retail shelf restocking teleoperation](https://www.operantdata.com/datasets/retail-shelf-restock): Retail shelf restocking via teleoperation
- [Warehouse conveyor handoff episodes](https://www.operantdata.com/datasets/warehouse-conveyor-handoff): Robot-to-conveyor handoff in distribution centers
- [Warehouse pallet pick teleoperation capture](https://www.operantdata.com/datasets/warehouse-pallet-pick-teleoperation): Teleoperated pallet picking in operational warehouse aisles

## Guides and insights
- [Metrics that prove sim-to-real gap closing](https://www.operantdata.com/blog/sim-to-real-metrics): Track deployment KPIs on targeted real slices before declaring sim-to-real victory.
- [Teleoperation capture best practices for imitation learning](https://www.operantdata.com/blog/teleoperation-best-practices): Small teleop pilot mistakes become expensive at scale, calibrate early.
- [Building evaluation benchmarks from real-world tails](https://www.operantdata.com/blog/eval-benchmarks-real-world): Benchmarks copied from training distributions hide failures you will see in production.
- [Privacy and consent for on-site robotics capture](https://www.operantdata.com/blog/privacy-consent-on-site): On-site capture needs clear consent, minimization, and transfer controls, not afterthoughts.
- [Running robotics data collection like a production pipeline](https://www.operantdata.com/blog/collection-ops-playbook): Pilots, QA gates, and operator runbooks turn one-off demos into reliable data supply.
- [What "good" physical AI data looks like](https://www.operantdata.com/blog/physical-ai-data-quality): Episode volume alone does not predict deployment success, sync, calibration, and tail coverage matter.

## FAQ
- [How is Operant different from buying an open dataset?](https://www.operantdata.com/faq#different-from-open-dataset): Open datasets rarely match your robot, sensors, or deployment environment. Operant designs capture around your evaluation goals, not a fixed catalog download.
- [Do we own the data?](https://www.operantdata.com/faq#data-ownership): Yes. Engagements grant your organization ownership of captured data with terms documented during scoping.
- [What sensors do you support?](https://www.operantdata.com/faq#supported-sensors): RGB-D, LiDAR, IMU, force/torque, and proprioceptive streams are common. We finalize the sensor list on your discovery call.
- [How long does a collection program take?](https://www.operantdata.com/faq#timeline): Pilots often run 2–4 weeks. Production scales over months depending on diversity targets and geographies.
- [What happens on a discovery call?](https://www.operantdata.com/faq#discovery-call): We review your stack, behaviors, sensors, volume, and quality bar, then outline a pilot and commercial framework.
- [How do you handle privacy and consent on site?](https://www.operantdata.com/faq#privacy-consent): We follow your policies and applicable regulations with consent workflows and secure transfer agreed before capture.
- [What deliverables and formats do you provide?](https://www.operantdata.com/faq#deliverables-formats): Time-synchronized logs, calibration files, metadata, and optional labels in formats your training pipeline expects.
- [Who is Operant for?](https://www.operantdata.com/faq#who-is-this-for): Robotics and physical AI teams with defined milestones who need auditable real-world data, not generic bulk downloads.
- [How is pricing structured?](https://www.operantdata.com/faq#pricing-model): Custom projects are scoped fixed-fee or milestone-based after discovery, aligned to environments, sensors, and volume tiers.
- [What geographies can you operate in?](https://www.operantdata.com/faq#geographic-coverage): We run programs in North America and Europe by default; other regions are available with lead time for permits and staffing.
- [Do you provide labeling and annotation?](https://www.operantdata.com/faq#labeling): Yes, label schemas, QA, and tooling integrations can be included when defined in scope.
- [What do we need for a pilot?](https://www.operantdata.com/faq#pilot-requirements): Target behaviors, sensor list, a staging environment, and an engineering point of contact for format validation.
- [How do you QA captured data?](https://www.operantdata.com/faq#quality-assurance): Automated sync checks, sample review gates, and acceptance tests tied to the statement of work before scale.
- [Will our project stay confidential?](https://www.operantdata.com/faq#ip-confidentiality): NDAs and restricted-access delivery are standard for commercial robotics programs.
- [Can data integrate with our sim pipeline?](https://www.operantdata.com/faq#simulation-integration): We deliver metadata and formats compatible with sim-to-real workflows and can align episode IDs with your sim domains.
- [Do you support ongoing collection after handoff?](https://www.operantdata.com/faq#ongoing-collection): Yes, retainer-style programs maintain diversity and refresh tail behaviors as your product evolves.
- [Is there a minimum engagement size?](https://www.operantdata.com/faq#minimum-volume): Pilots are designed to be meaningful but bounded; production scale follows proven pilot metrics.
- [Do you provide robots or only operators?](https://www.operantdata.com/faq#hardware-provided): We typically capture on client or lessor hardware; operator staffing and rigging are part of scope.
- [Can you target specific failure modes?](https://www.operantdata.com/faq#failure-modes): Yes, failure taxonomy and sampling ratios are defined explicitly for eval-oriented programs.
- [Do you support teleoperation programs?](https://www.operantdata.com/faq#teleoperation-support): Teleoperation and demonstration capture are core offerings with multi-camera synchronization.
- [Is Operant a dataset marketplace?](https://www.operantdata.com/faq#marketplace-clarification): No. Operant runs custom capture programs for your environments and robots, we are not a broker or off-the-shelf catalog.

## Full content
- [Full text of every page (llms-full.txt)](https://www.operantdata.com/llms-full.txt): complete page bodies for answer engines

## Contact
Book a discovery call at https://www.operantdata.com/book to scope sensors, environments, volumes, and timelines.