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

Apply to capture

Wire wrapping

Stereo Jewelry Wire Wrapping Data

Bend wire, wrap it around a stone or a bead and shape it with pliers into jewellery: one catalog row, Wire wrapping, in which both hands, a small piece and a tool crowd into one close view that a single camera cannot hold. This page covers the stereo and container side of wire wrapping robot training data: what a calibrated stereo pair adds to stereo jewellery wire wrapping video, what MCAP is according to its own documentation, and what the site does not state. We run custom jewelry data collection fast and on demand against a spec you write, as an egocentric pliers and bead wrapping 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
Wire wrapping (Medium), in Jewelry & Metalsmithing Studio
Status
Available on request
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 wire wrapping video?

01

Depth for a small piece and a tool

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the wire, the stone or bead, the pliers and both hands sit in one frame. The site gives no depth accuracy figure for this row and does not state how depth behaves on thin wire.

02

Fingers hidden behind the piece, 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 folded behind a bead or a pair of pliers is marked as hidden rather than silently filled in.

03

Bends and wraps as separate steps

The row is worded as bending and wrapping wire around stones and beads. Action segments carry start_ns, end_ns, verb and noun, so each bend or wrap can be a 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 jewelry wire wrapping data?

It is first-person video of a person forming jewellery from wire at a bench, recorded with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: wire wrapping robot training data, stereo jewellery wire wrapping video, an egocentric pliers and bead wrapping dataset, or custom jewelry 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 head-mounted phone or a multiview rig as the capture setup, so a stereo pair is a capture choice agreed in the skill spec 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 under the Jewelry & Metalsmithing Studio environment in the Creative Workshops & Crafts sector, whose examples are goldsmith bench, gem setting, wire wrapping, soldering, engraving and polishing. The row "Wire wrapping" is described as "Bend and wrap wire around stones and beads with pliers to form jewellery." and is rated Medium.

It lists the capture setup "Phone (head-mounted) / multiview rig" and is Available on request. The site states no delivered hours and no delivered stereo footage for the row, so this page claims none. The first table below reproduces the row as the catalog states it.

Wire wrapping

How does the Wire wrapping row read, and what can a stereo spec label?

The row names three things: wire, stones and beads as the material, pliers as the tool, and jewellery as the result. It covers bending and wrapping wire by hand and with pliers, and it is rated Medium, the same rating as Polishing and below the three Hard rows of the studio. A spec that says "wrap a piece" gives one long action segment, while a spec that names each bend and each wrap, and says where each starts and ends, gives a sequence you can slice by step, with each segment carrying start_ns, end_ns, verb and noun.

That is all the site states. Wire gauges, metal types, stone and bead types, plier types and the finished designs are Not stated, so this page makes no claim about them. Whether an episode is one wrap, one piece or a whole session is a spec decision, not a default.

Difference

How is this different from the egocentric wire wrapping page and the other jewelry pages?

This page is the stereo and MCAP treatment of one row, Wire wrapping. The egocentric jewelry wire wrapping page covers the same row as first-person capture and does not have stereo as its subject; it remains the page for the first-person framing. The stereo jewelry and metalsmithing page covers all five studio rows as stereo capture and MCAP delivery, so wire wrapping is one of five there.

The stereo jewelry soldering and polishing page covers the Soldering and Polishing rows, and the stereo gem setting and engraving page covers Gem setting and Engraving. Those are different tasks at the same bench, and neither has wire wrapping as its subject. The second table below sets the pages side by side with their status as the site lists them.

Capture setup

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

The catalog lists "Phone (head-mounted) / multiview rig" for the row. The site does not state a stereo pair for it. 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 catalog does not say which of its two modes applies to a batch, so the setting is agreed in the spec. The site lists capture at your own facility as not offered.

The site describes two stereo setups and does not say which one an order for this row uses. 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. The hard-environments stack is a 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, depth at 848×480 and 30 fps, and a 200 Hz 6-DoF IMU. Camera count, resolution and frame rate for wire wrapping are Not stated.

Occlusion and depth

What do the hands, the wire and the pliers do to visibility and depth?

At a bench the hands sit between the camera and the work, and a small piece can vanish behind a finger, a pair of fingers closed around it or the pliers themselves. 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 an item, and why instance masks are recorded per frame.

The site states that metric depth on sub-centimetre parts is flagged rather than interpolated, and that depth degrades on wet and reflective surfaces, with per-frame confidence maps masking low-confidence regions. Whether wire, a bead or a stone counts as such a part or surface is Not stated. A Spec Pilot checks it on real footage rather than assuming it.

Hand pose and streams

What does a stereo wire wrapping episode contain?

Each episode follows the Firsthand episode schema, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events and frame-accurate action segments. Hand pose is delivered as handJoints[2][21][3] in metric units in the head-camera frame, two hands of 21 joints each, with a visibility flag per joint. For this row, hand pose tracks how the fingers hold and move the wire and the pliers, contact events mark when a finger or the pliers meet the wire, a stone or a bead, and action segments mark each step of the wrap.

The only language data the site ties to Firsthand capture is one task instruction per episode. Object labels use the terms your spec sets. Force or tactile data, and success or quality labels for a finished piece, are Not stated for this row, and this page does not offer them as deliverables. The site offers a tactile glove tier as a pilot-ready option, but it does not state that the tier has been used on jewelry work.

Not stated

What does the site not state about stereo jewelry wire wrapping?

Wire gauges, metal types, stone and bead types, plier types and brands, piece sizes, tolerances, cycle times, error rates, item counts and what a finished wrapped piece means are Not stated. No jeweler, maker, studio, client, piece or commission is named for the row, and none is used here. They are set in the written spec, and this page claims none of them.

Safety and privacy

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

Pliers and tool safety are Not stated on the site. It states no contributor safety protocol and no trade certification for the studio rows, so this page describes none and gives no safety instructions. Who performs the work and under what conditions is something to raise when you scope the order.

For every delivered episode the site states that faces, plates and screens are detected and irreversibly blurred at ingest, that a reviewer confirms the result before anything ships, 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 through a documented consent chain. 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 wire wrapping 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. The third table below maps each stream to what the site states.

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.

Failure modes

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

Hand occlusion by the piece and the pliers is the first risk, handled by the visibility flag above. 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 more than 35 percent invalid depth pixels in the manipulation region, for an undocumented bystander or for a mismatch against the named skill spec.

For this row, what counts as the manipulated object, the wire, the piece or the pliers, is a spec decision, and it decides how the out-of-frame rule applies. A reject log ships with every batch, and rejected items are recaptured at the provider’s cost. The fourth table below lists each failure mode with what the site states.

Scale

How do off-the-shelf coverage and custom collection combine for wire wrapping?

The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets, of which stereo is ~64,800 hours across 9 datasets. The site names no jewelry wire wrapping dataset among them, so this work 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 a median of 48 hours; where it is thin, turnaround runs three to four weeks. The row is Available on request, so the site does not say which applies, and the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Ordering

How do you order a stereo jewelry wire wrapping dataset?

Describe the task and where it starts and ends: bending wire, wrapping it around a stone or bead and forming the piece with pliers. Say whether an episode covers one wrap, one piece or a whole session, what counts as the object and as a reject, the setting and lighting, and the privacy rule.

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: Wire wrapping
"Wire wrapping": "Bend and wrap wire around stones and beads with pliers to form jewellery."; Jewelry & Metalsmithing Studio, Creative Workshops & Crafts; Medium; Available on request
Catalog capture setup
Phone (head-mounted) / multiview rig. 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
Wire gauges, metal types, stone and bead types, plier types, piece sizes, cycle times
Not stated; agreed in the skill spec
Pliers and tool safety
Not stated beyond the privacy steps listed below; 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 jewelry wire wrapping, and what is its status?

One row from lib/commercial-catalog-data.ts, reproduced as the catalog states it. The row does not state a stereo pair.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Wire wrappingBend and wrap wire around stones and beads with pliers to form jewellery.Jewelry & Metalsmithing StudioMediumPhone (head-mounted) / multiview rigAvailable on request

Comparison

How does this page compare with the neighbouring jewelry pages?

The existing pages closest to this topic, set against this page by capture framing, rows covered and row status as the site lists it.
PageCaptureWhat it coversRow status as listedRelation to this page
This page: stereo jewelry wire wrapping dataStereo pair through the general offer; MCAP deliveryOne row: Wire wrappingAvailable on request (Medium)Wire wrapping as the main topic, in stereo
Egocentric jewelry wire wrapping dataEgocentric, not stereoOne row: Wire wrappingAvailable on request (Medium)The same row as first-person capture; not stereo as its subject
Stereo jewelry and metalsmithing dataStereo, agreed in the spec; MCAP focusAll five studio rowsAll five Available on request (three Hard, two Medium)The whole bench in stereo; wire wrapping is one of five there
Stereo jewelry soldering and polishing dataStereo, agreed in the spec; MCAP focusTwo rows: Soldering and PolishingBoth Available on request (Hard, Medium)A different pair of rows at the same bench; covers no wire wrapping
Stereo gem setting and engraving dataStereo, agreed in the spec; MCAP focusTwo rows: Gem setting and EngravingBoth Available on request (both Hard)A different pair of rows at the same bench; covers no wire wrapping
Stereo wire crimping and harness assembly dataStereo, agreed in the spec; MCAP focusElectrical wire work, not jewelrySee that pageCrimping and harness assembly, not wrapping wire around stones and beads
Egocentric stereo data in MCAPThe stereo and MCAP hub across tasksNot applicableNot applicableGeneral stereo and MCAP treatment; not specific to jewelry

Stream map

Streams for wire wrapping data 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

Failure modes and QA

What goes wrong in wire wrapping capture, and what QA does about it

Left to right: the failure mode, what the site states, and what a buyer sees. “Not stated” means the site does not say.
Failure modeWhat the site statesWhat a buyer sees
Fingers hidden behind the piece or the pliersPer-joint visibility flag on hand pose; wrist views and a multiview angle available in the specA hidden joint flagged as hidden, not guessed
Piece or pliers out of framePer-frame instance masks; episode rejected when the object is out of frame for more than 15 percent of itReject log per batch; what the object is gets set in the spec
Small parts and thin wireMetric depth on sub-centimetre parts is flagged rather than interpolatedWhether wire or a bead counts: Not stated; test on a Spec Pilot
Reflective surfacesDepth degrades on wet and reflective surfaces; confidence maps mask low-confidence regionsBehaviour on metal wire and stones: Not stated; test on a Spec Pilot
Invalid depth in the manipulation regionEpisode rejected when more than 35 percent of depth pixels are invalidReject log per batch; confidence maps ship with depth
Bystander in frameFaces, plates and screens blurred and reviewer-confirmed; undocumented bystander rejected; footage that cannot be de-identified is discardedReject log per batch; anonymization record ships with the data
Calibration driftSolved at the start and end of every session; 0.28 px RMS gateCalibration shipped with the episode
Sync breachRejected beyond the 2.0 ms ceiling for more than three consecutive framesReject log per batch
Spec mismatchRejected for a mismatch against the named skill specReject log per batch

Stated vs not stated

What the site states about stereo capture for jewelry wire wrapping

Left to right: the item, what the site states, and what that means for a wire wrapping order. “Not stated” means the site does not say.
ItemWhat the site statesFor a wire wrapping order
Catalog capture setupPhone (head-mounted) / multiview rig 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
Row statusWire wrapping is Available on requestNo volume, hours or delivered stereo footage is claimed on this page
Calibration and synchronizationMeasured every session, 0.28 px RMS gate; hardware-triggered, 2.0 ms cross-stream ceilingStated
Wire, metal, stone, bead and plier details; piece sizesNot statedNot claimed; set in the spec
Pliers and tool safetyNot stated; no contributor safety protocol or trade certification for the studio rowsNot claimed; no safety instructions are given
Task time, error rate, piece qualityNot statedNot claimed on this page
MCAP topics, schemas, ratesNot statedAgreed in the skill spec

Skill spec

What the skill spec fixes for a stereo wire wrapping 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
RowWire wrapping, worded as the catalog words itSet per program; Available on request
Steps and orderWhat one step is: a bend, a wrap, a holdEpisode boundaries and action segments; set per program
Episode scopeOne wrap, one piece or a whole sessionSet per program; the site does not state an episode length
Object definitionWhether the wire, the piece or the pliers count 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 bench 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 signage in frame are handledFaces, plates 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 wire wrapping or any jewelry task.

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

No wire wrapping 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 jewelry wire wrapping data, answered.

What is stereo jewelry wire wrapping data?
First-person video from two calibrated cameras of a person bending and wrapping wire around stones and beads with pliers to form jewellery, with depth and hand pose alongside.
Which catalog row covers it, and what is its status?
One, under Jewelry & Metalsmithing Studio: "Wire wrapping" (Medium). It lists "Phone (head-mounted) / multiview rig" and is Available on request. This page claims no delivered hours.
Is stereo already captured on this row?
Not stated. The catalog lists a head-mounted phone or multiview rig and no stereo pair. 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 wire wrapping page?
The egocentric page covers the same Wire wrapping row as first-person capture that is not stereo as its subject. This page is stereo capture of that row with MCAP delivery. The stereo jewelry page covers all five studio rows.
Is there an off-the-shelf wire wrapping dataset?
No listed dataset names jewelry wire wrapping. Stereo wire wrapping data 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 wire gauges, bead types or safety guidance?
Not stated. The site names wire, stones, beads and pliers in the row and lists no wire gauges, metal, stone or bead types, plier types, piece sizes, cycle times or error rates, and gives no pliers or tool safety guidance, so none is claimed.
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.
Is the footage anonymized and consented, and who owns it?
Every contributor signs a written release, and each episode links to it by consent artefact ID. Faces, plates and screens are blurred irreversibly, and footage that cannot be de-identified is discarded. The license is perpetual, irrevocable and buyer-owned.

Sources

Where is MCAP documented?

Request a custom stereo jewelry wire wrapping dataset delivered as MCAP.

Tell us the task and where it starts and ends, whether an episode covers one wrap, one piece or a whole session, what counts as the object, the setting and lighting, the privacy rule, the streams you want in the file and whether MCAP sits beside RLDS, LeRobot or WebDataset. We will quote reach, timeline and price against a written spec, with a first validated batch proven on a Spec Pilot.