Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Peel and chop

Stereo Cutting and Food Prep Data

Peeling and chopping vegetables with a knife is two hands doing different jobs on an item that changes with every step, and the knife, the vegetable and both hands keep covering one another. This page covers the stereo and container side of food prep robot training data for the one catalog row that names this work: what a calibrated stereo pair adds to stereo vegetable peeling and chopping video, what MCAP is according to its own documentation, and what the site does not state. We run custom kitchen data collection fast and on demand against a spec you write, as an egocentric knife work dataset when the spec names it, delivered as MCAP, as custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Catalog row
"Peel + chop vegetables"; Medium; Available on request
Environment
Working Kitchen Set (food prep)
Container
MCAP (.mcap), open source
License
Perpetual, buyer-owned

Why stereo and MCAP here

What do a stereo pair and an MCAP file add to peeling and chopping video?

01

Depth for a knife over a board

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the hands, the vegetable and the knife sit in one frame. The site gives no depth accuracy figure for this row and does not say how depth behaves around a blade or a small item.

02

Fingers behind a vegetable or a handle, flagged not guessed

The site states that fingers disappear behind objects and that the hands occlude the work. 3D hand pose carries a per-joint visibility flag, so a finger hidden behind a vegetable or a handle is marked as hidden rather than silently filled in.

03

Peel and chop as separate steps

The row words the work as peel and chop. Action segments carry start_ns, end_ns, verb and noun, so each step can be its own labeled span. Which verbs and nouns are used is set in the skill spec.

04

Several streams in one container

MCAP stores multiple channels of timestamped, pre-serialized data, so a stereo pair, hand pose and IMU can share one file on one log-time axis. Which streams go in the file is set in the skill spec.

Definition

What is stereo cutting and food prep data?

It is first-person video of a person peeling and chopping vegetables with a knife, recorded with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: food prep robot training data, stereo vegetable peeling and chopping video, an egocentric knife work dataset, or custom kitchen data collection at scale. They describe one request from different angles. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The site does not state that stereo is already running on this row. The catalog lists a multiview rig with handheld grippers as the capture setup, so a stereo pair is a capture choice agreed in the skill spec through the site’s general stereo offer and confirmed on a Spec Pilot. The data is human capture by paid, consented contributors, not robot or teleoperation data, so using it for a specific robot still needs your own retargeting step. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Catalog row

Which catalog row does this page rely on, and what is its status?

One, listed in lib/commercial-catalog-data.ts. "Peel + chop vegetables" sits in the Working Kitchen Set (food prep) environment of the Food & Beverage sector, which the catalog describes with these examples: stovetop, counter, sink, dishwasher, utensils and food props. Its description reads "Peel and chop vegetables with a knife." It is rated Medium, lists the capture setup "Multiview rig + handheld grippers", and its status is Available on request.

Available on request means the work is scoped and recruited to spec when a buyer asks. It is not a statement that footage of this task has been delivered, and the site states no delivered hours or stereo clips for it, so this page claims none. The first table below reproduces the row exactly as the catalog states it. The site does not describe a vegetable, a knife, a cutting board, a peeler, a cut type or a cut size for the row, so none is stated here.

The setting

What is the Working Kitchen Set environment?

Fourteen rows sit in it, and every one lists the same capture mode, a multiview rig with handheld grippers, and the same status, Available on request. Ten are rated Medium and four are rated Easy. The site describes this capture mode as a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector.

The site states that Firsthand does not capture at a customer’s own facility, so the kitchen is a capture setting arranged for the task, not your kitchen. Whether a stereo pair would be worn, mounted or combined with the multiview rig the catalog names is not stated, and is settled in the spec.

Nearby rows

Which other catalog rows sit next to peeling and chopping?

Three neighbouring rows in the same environment share parts of the job. "Slice + spread" reads "Slice bread and spread a condiment." "Crack + whisk eggs" reads "Crack eggs and whisk, then pour to pan." "Assemble a salad" reads "Tear greens, add toppings, dress, and toss a salad." Each is rated Medium, listed with Multiview rig + handheld grippers and Available on request.

These are separate rows, not steps of the peel and chop row. They are context only, and each is its own request. If your policy needs the step that follows the chopping, such as plating, that is a spec question for the neighbouring row, and the "Plate + garnish" row reads "Plate a portion and add garnish." It is rated Easy.

Difference

How is this different from the egocentric cutting page, the line cooking page and the fryer page?

This page is the stereo and MCAP treatment of one working-kitchen row, Peel + chop vegetables. The egocentric cutting and food prep page covers the family of knife-work rows as first-person video, without stereo and MCAP as its subject, and it also lists the Restaurant & Commercial Kitchen rows and the Slice + spread row. Different tasks sit on other pages, and the rows are listed separately in the catalog.

The stereo commercial kitchen line cooking page covers the Restaurant & Commercial Kitchen rows, "Culinary Chef Work / Knife Work" (Hard) and a vegetable chopping and portioning row (Medium), both listed as Active collection. The stereo fast food fryer and grill page covers three quick-service rows, Fryer and grill operation, Order assembly and Counter service and packaging. The egocentric egg cracking page covers one separate row, Crack + whisk eggs. The second table below sets the pages side by side.

Capture setup

What capture setup does the row list, and where does stereo come in?

The catalog lists "Multiview rig + handheld grippers" for the row. The site does not state a stereo pair for it, and it does not describe this task as stereo capture. Stereo applies through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The site does not state a camera count for the row.

The site describes two stereo setups and does not say which one an order for this row uses. The hard-environments stack is a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps, and 200 Hz 6-DoF IMUs. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye, a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output. Whether either is used with the catalog’s multiview rig is not stated.

Why stereo

Why capture peeling and chopping in stereo?

The task is about how a knife and two hands act on a vegetable: where it is held, how it is peeled and how it is chopped. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the geometry sits in the same capture that shows the hands working. The site gives no depth accuracy figure for this row, so what a buyer does with that depth is their pipeline’s question.

A stereo pair adds depth, not a verdict. The site lists no cut-quality, thickness, uniformity or doneness label for this row, and none is claimed. The egocentric cutting page already supplies the first-person framing; stereo is the addition for a buyer who wants the depth and the MCAP file.

Steps

Which steps of peeling and chopping can a stereo spec label?

The row gives a natural cut: peel, then chop. A spec that says "do the food prep task" gives one long action segment. A spec that names the steps gives a sequence you can slice by step. The site’s skill-spec guide says to name the verb and the noun rather than a broad activity, which is why the row’s own two verbs are the place to start.

Whether peeling and chopping are one segment or two is a spec decision, not a default. The site does not set an episode length, so the spec says whether one episode is one vegetable, one batch or a peel-to-chop run. Contact events can mark when a hand meets an item, where the spec asks for them, and the spec decides what counts as the item, including whether the vegetable, the knife or the board qualifies.

Occlusion

What do the hands and a changing vegetable do to visibility?

A hand steadying a vegetable and a blade moving across it both put something between the lens and the work. The site states that the hands occlude the work and that fingers disappear behind objects. That is why each hand joint carries a visibility flag, why contact events mark when the hand meets the item, and why instance masks are recorded per frame. It also states that reach and grasp frames are where blur and occlusion show up, and the head camera in the hard-environments stack is global-shutter, which avoids rolling-shutter skew.

Vegetables change shape as they are peeled and chopped. The site states that ingredients change shape and state, and that masks propagated frame to frame do not track them well, so food prep captures ship per-frame instance masks. How a peeled or chopped item looks in depth is not stated for this row. If your policy depends on those frames, say so in the spec and settle it on a Spec Pilot.

Surfaces and light

What does the site say about glare, lighting and wet or reflective surfaces?

The site states that glare-heavy and low-texture scenes make single-frame depth worse, and that depth degrades on wet and reflective surfaces, with per-frame confidence maps masking low-confidence regions. A rinsed board or a metal sink can be wet or reflective, but the site does not say how depth behaves on one for this row, and a lighting setup for this row is not stated.

Where a program needs a specific counter layout, lighting or background, that goes into the spec and is checked on a Spec Pilot. An episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid, and for this job the spec decides what the manipulation region is at each step.

Safety and privacy

What does the site say about safety, compliance and privacy?

This page describes the hand work named in the catalog row, and nothing beyond it. It gives no knife-handling, food-safety, hygiene or kitchen-safety guidance and makes no certification claim. A contributor knife-handling protocol is not stated on this site, so this page does not describe one. The data carries no force, tactile or thermal reading, and it is not robot or teleoperation data.

For every delivered episode the site states that faces and screens are blurred irreversibly, that a reviewer confirms no un-consented person is identifiable, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data, an undocumented bystander is a stated reject criterion, and every episode links to a signed contributor release. Whether a product label in view is blurred is not stated, so it is agreed in the spec. This is not legal advice, and the executed agreement controls.

MCAP

What is MCAP, per its own documentation?

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression.

Reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript, and the mcap CLI can inspect, merge and split files. The foxglove/mcap repository is MIT-licensed; that is the MCAP project licence, not the licence of a Firsthand delivery. The MCAP hub page and the glossary entry cover the format in full.

Streams

Which streams can ship in an MCAP delivery of peeling and chopping data?

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For this row the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments, per-frame instance masks and one task instruction per episode elsewhere. What it does not state is which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate.

No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The fourth table below sets each stream beside what the site states about it.

Failure modes

What goes wrong when you record knife work in stereo, and what does QA reject?

Hand occlusion by the vegetable and the knife is the first risk, under the visibility flag above. Weak depth on glare-heavy, wet or reflective surfaces is the second. Calibration is measured at the start and end of every session under a 0.28 px RMS gate, and an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for the manipulated object out of frame for more than 15 percent of the episode, for an undocumented bystander or for a mismatch against the named skill spec.

A reject log ships with every batch, and rejected items are recaptured at the provider’s cost. For a peel and chop task, the spec decides what the manipulated object is: the vegetable, the knife, the board, or a pair of them.

Scale and speed

How fast can custom stereo food prep data be collected at scale?

The row is Available on request, so this is custom collection, not an off-the-shelf purchase. The off-the-shelf stereo and hand-tracking video can still show the format before you write a spec.

It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. Where coverage is deep, the median time from signed spec to first validated batch is 48 hours; where it is thin, turnaround runs three to four weeks. The site does not say which applies to the working kitchen set, so the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Delivery and license

Which formats and license come with a stereo food prep order?

Delivery is MCAP, alone or beside the formats your stack already reads: RLDS, LeRobot, WebDataset, HDF5 or zarr, or raw streams with metadata. Readable converter source ships alongside the data so the schema can be retargeted to your own loader.

The license is perpetual, irrevocable and worldwide, with the data buyer-owned and non-exclusive by default. Training, evaluating, fine-tuning and deploying models, including commercial ones, is permitted, and exclusivity is available as a separate term. The executed agreement controls. The site does not publish a price list, a minimum order or a batch size for this task, so those are set in your quote.

Ordering

How do you order a stereo peel and chop dataset?

Describe the steps and where each starts and ends: peeling and chopping. Say whether an episode covers one vegetable, one batch or a peel-to-chop run, what counts as the object and what counts as a finished step, the privacy rule for the space, and name the variation your pipeline is missing. Then name the streams you want in the file, the topic naming and message encoding your reader expects, whether calibration ships inside the file or beside it, and whether MCAP is the only delivery or sits beside a training format.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The last table below shows what each spec element decides.

At a glance

What you get.

Catalog row: Peel + chop vegetables
"Peel + chop vegetables" (Working Kitchen Set (food prep), Food & Beverage); Medium; Available on request
Catalog description
"Peel and chop vegetables with a knife."
Catalog capture setup
Multiview rig + handheld grippers. The site states no stereo pair for this row, so a stereo pair is agreed in the skill spec through the general stereo offer
Stereo head rig (06)
Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAP
Hand pose
21 joints per hand with a per-joint visibility flag
Sync
Hardware-triggered onto one clock; 2.0 ms cross-stream ceiling
Vegetables, knife and board models, cut types and sizes, task times, error rates
Not stated; agreed in the skill spec
Knife handling or kitchen safety
Not stated; nothing here is safety guidance
MCAP topics, schemas, rates
Not stated on the site; agreed in the skill spec
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog row

Which catalog row covers peeling and chopping, and what is its status?

The row exactly as lib/commercial-catalog-data.ts states it, followed by three neighbouring rows from the same environment, shown for context only. Items the catalog does not list are marked Not stated.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Peel + chop vegetablesPeel and chop vegetables with a knife.Working Kitchen Set (food prep)MediumMultiview rig + handheld grippersAvailable on request
Slice + spread (nearby, context only)Slice bread and spread a condiment.Working Kitchen Set (food prep)MediumMultiview rig + handheld grippersAvailable on request
Crack + whisk eggs (nearby, context only)Crack eggs and whisk, then pour to pan.Working Kitchen Set (food prep)MediumMultiview rig + handheld grippersAvailable on request
Assemble a salad (nearby, context only)Tear greens, add toppings, dress, and toss a salad.Working Kitchen Set (food prep)MediumMultiview rig + handheld grippersAvailable on request
Vegetable, knife, board or peeler type; cut type or size; cut-quality labelsNoneNot stated as rowsNot statedNot statedNot stated

Compared pages

How does this page differ from the egocentric cutting, line cooking, fryer and egg pages?

Each page and the catalog rows it covers. Statuses are as the site lists them; none of these pages is claimed to hold delivered hours here.
PageWhat it coversRow status as listedRelation to this page
This page: stereo cutting and food prep dataPeel + chop vegetablesMedium, Available on requestStereo pair and MCAP delivery for one working-kitchen row
Egocentric cutting and food prep video dataThe knife-work rows across Restaurant & Commercial Kitchen and the Working Kitchen Set, including Peel + chop vegetablesPer row; see the catalogThe first-person page for the family; stereo and MCAP are not its subject
Stereo commercial kitchen line cooking dataCulinary Chef Work / Knife Work and a vegetable chopping and portioning row, in Restaurant & Commercial KitchenHard and Medium, Active collectionDifferent rows and environment; line work rather than the working kitchen set
Stereo fast food fryer and grill dataFryer and grill operation, Order assembly, Counter service and packagingMedium and Easy, Available on requestDifferent task; quick-service kitchen rows
Egocentric egg cracking and whisking dataCrack + whisk eggsMedium, Available on requestDifferent task in the same environment
Egocentric stereo data in MCAPThe stereo and MCAP hub across tasksNot applicableGeneral stereo and MCAP treatment; not specific to food prep

Stated vs not stated

What the site states about stereo capture for peeling and chopping

Left to right: the item, what the site states, and what that means for a peel and chop order. “Not stated” means the site does not say.
ItemWhat the site statesFor a peel and chop order
Catalog capture setupMultiview rig + handheld grippers on the rowNo stereo pair is stated for this row; a stereo pair is a spec choice through the general stereo offer
Stereo head rig (dataset 06)Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAPWhether an order uses it: Not stated
Hard-environments stack4K/60 head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMUWhether an order uses it: Not stated
Hands, contacts and masksPer-joint visibility flag on hand pose; contact events; per-frame instance masks stored at 848×480Stated; what counts as the object is set in the spec
Hand occlusionThe hands occlude the work and fingers disappear behind objects; visibility flags and instance masks address itStated; how often it occurs on this row is Not stated
Ingredients that change shapeMasks propagated frame to frame do not track them well, so per-frame instance masks shipStated; behaviour on a peeled or chopped item in depth is Not stated
Depth on wet or reflective surfacesDepth degrades on wet and reflective surfaces; confidence maps mask low-confidence regionsStated; behaviour on a rinsed board is Not stated
CalibrationMeasured every session and shipped with the episode; 0.28 px RMS reprojection gateStated
SynchronizationHardware-triggered onto one clock; 2.0 ms cross-stream ceilingStated
Row statusMedium, Available on requestNo volume, hours or delivered stereo footage is claimed on this page
Vegetable, knife, board or peeler; cut type or sizeNot statedNot claimed; set in the spec
Cut-quality, thickness, uniformity or doneness labelNot stated; no such label is listed for the rowNot claimed; set in the spec
Knife handling, food safety, certificationNot statedNot claimed on this page
Cycle time, error rate, task durationNot statedNot claimed on this page
MCAP topics, schemas, ratesNot statedAgreed in the skill spec

Stream map

Streams for peeling and chopping and what the site states about an MCAP file

Left to right: the stream or item, what the site states about it, and what the site states about it in MCAP. “Not stated” means the site does not say.
Stream or itemWhat the site statesIn an MCAP delivery, as the site states it
Stereo pairDual fisheye, 1080p per eye, 62 mm baseline (dataset 06)Dataset 06 is stated as shipped as MCAP; channel layout not stated
Depth with confidence mapsRecovered from the calibrated stereo pair; confidence map masks low-confidence regionsNot stated
Hand pose21 joints per hand with a per-joint visibility flagChannel layout and joint order not stated
IMU9-axis (dataset 06); 6-DoF at 200 Hz (hard-environments stack)Channel layout and rate not stated
Contact events, action segments, instance masksListed in the site episode schema; masks stored at 848×480Not stated
Task instructionOne per episodeNot stated
CalibrationMeasured every session and shipped with the episodePlacement in the file not stated
Topic names, schemas, encoding, ratesNot statedAgreed in the skill spec

Skill spec

What the skill spec fixes for a stereo peel and chop order

Spec element and where a buyer can see it in the delivery. “Set per program” means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
RowPeel + chop vegetables, worded as the catalog words itSet per program; Available on request as listed
Steps and orderWhat one step is: peel, chopEpisode boundaries and action segments; set per program
Episode scopeOne vegetable, one batch or a peel-to-chop runSet per program; the site does not state an episode length
Object definitionWhether the vegetable, the knife, the board or a pair counts as the objectContact events and the out-of-frame reject rule; set per program
Rig and streamsStereo pair, multiview angles, wrist views, hand pose, IMU and any othersThe channels you can read; confirm on the Spec Pilot
Setting and lightingWhere capture runs and how the counter is litSet per program; the site states no lighting setup for this row
MCAP topics and encodingWhat your reader expectsSet per program
Delivery formatHow the data is packagedMCAP alone, or beside RLDS, LeRobot, WebDataset, HDF5 or zarr
Accept criteriaWhat passes QA, including what counts as a rejectReject log per batch
PrivacyHow people, screens and printed labels in frame are handledFaces and screens blurred at ingest; other items agreed in the spec
LicenseWho owns the datasetPerpetual, irrevocable, buyer-owned, non-exclusive by default

Example footage

What does egocentric stereo capture look like?

One real clip already published on this site, shown as a format and rig example: a head-mounted stereo capture with hands in frame. It does not show peeling, chopping, a knife or a kitchen, and it is not an example of the multiview rig with handheld grippers this row lists.

egocentric_stereo_sample.mp4 · head-mounted stereo · hands in frame · 1920 × 1080 web preview · rig example, not a peel or chop clip

No peeling or chopping clip is published on the site, so this is labelled as a format and rig example. Request a sample to see delivered files. See stereo sample page, stereo + wrist-cam example videos, request an egocentric data sample.

FAQ

Stereo vegetable peeling and chopping video, answered.

What is stereo cutting and food prep data?
First-person video from two calibrated cameras of a person peeling and chopping vegetables with a knife, with depth and hand pose alongside.
Which catalog row covers it, and what is its status?
"Peel + chop vegetables" in Working Kitchen Set (food prep): "Peel and chop vegetables with a knife." It is rated Medium, listed with Multiview rig + handheld grippers, and its status is Available on request. This page claims no delivered hours.
Is stereo already captured on this row?
Not stated. The catalog lists a multiview rig with handheld grippers for the row. A stereo pair is agreed in the skill spec through the general stereo offer and confirmed on a Spec Pilot.
How is this different from the egocentric cutting page and the line cooking page?
The egocentric cutting page covers the family of knife-work rows as first-person video. The line cooking page covers the Restaurant & Commercial Kitchen rows, which are listed as Active collection. This page covers one working-kitchen row with a stereo pair and MCAP delivery.
Is there an off-the-shelf peeling and chopping dataset?
No. The row is Available on request, so this is custom collection, at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Does the data include vegetable, cut-type or quality labels?
Not stated. The site lists no vegetable, cut type, cut size, thickness, uniformity or doneness label, and no force reading, so none is claimed. These are set in the spec.
How fast can a custom stereo food prep dataset be collected?
From signed spec to first validated batch, a median of 48 hours where coverage is deep and three to four weeks where it is thin. The site does not say which applies to the working kitchen set, so it is quoted against your spec.
Can it be delivered as MCAP, and what is in the file?
Yes. Firsthand offers MCAP delivery. Topic names, message schemas and rates are not stated on the site and are agreed in the skill spec.

Sources

Where is MCAP documented?

Request a custom stereo cutting and food prep dataset delivered as MCAP.

Tell us the steps and where each starts and ends, whether an episode covers one vegetable, one batch or a peel-to-chop run, what counts as the object, the setting and lighting, the privacy rule for the space, the streams you want in the file and whether MCAP sits alone or beside a training format. We will quote reach, timeline and price against a written spec.