One row, stated exactly
The catalog lists a single lace row, "Thread lace eyelets", described as "Thread a lace through eyelets." It is rated Hard and is Available on request, so capture is scoped and recruited to your spec.
Now recruiting capture teams worldwide. Get paid to record first-person video of real work.
Apply to captureTask family
Requirements
The catalog lists a single lace row, "Thread lace eyelets", described as "Thread a lace through eyelets." It is rated Hard and is Available on request, so capture is scoped and recruited to your spec.
A lace is long and thin and has no single shape, so position and orientation alone do not describe it. The labels that carry the task are hand pose, contact events, action segments and, where the spec calls for them, per-frame instance masks.
The lace end, the eyelet and the fingers occupy a small part of the frame. Hand pose carries a per-joint visibility flag, so a finger hidden behind the lace or the shoe is marked as hidden rather than guessed.
Where a threading pass starts and stops, and what counts as finished, is not a default. The written spec states it, and QA checks episodes against it.
Definition
It is first-person video of one person threading a lace through eyelets, recorded from that person’s own point of view while they work. A paid, consented contributor wears the capture rig and performs the task written in a skill spec, and each attempt is delivered as an episode with synchronized streams, hand pose and labeled action segments. It is human capture. It is not robot or teleoperation data, and it is not a fixed corpus you download.
The target query is a shoelace query, but the catalog row is written more narrowly. It says "Thread a lace through eyelets." It does not name a shoe, a boot, a lace type or a bow. This page keeps to the row as written and treats anything more specific, such as a particular lacing pattern or tying a finished bow, as a spec question settled in a Spec Pilot.
The page is about buying a custom collection of those demonstrations: how the row is specified, how the capture is set up, how each attempt is labeled and what the site does not state. It makes no claim about a trained model, a benchmark or a success rate.
Catalog row
One row counts. "Thread lace eyelets" sits in the Deformables & Textiles Bench, in the Manufacturing & Workshops sector, whose examples read "Cloth-and-cable bench: garments, towels, cables, form boards, bags." The row is described as "Thread a lace through eyelets." and is rated Hard. Its capture setup is "Multiview rig + handheld grippers" and its status is Available on request.
Available on request is the site’s wording for a task that is scoped and recruited to spec when a buyer asks for it, as opposed to Active collection or Ready to deploy. So this page does not claim delivered hours, a stock of footage or a published dataset for this task. It describes what can be collected for you.
The first table below reproduces the row as the catalog states it, with the neighbouring fastening rows from the same bench shown as context only. The environment page for the Deformables & Textiles Bench lists the same rows, and the catalog row is the authority if the two ever read differently.
What the row does not say
No row in the catalog describes tying a shoelace or tying a knot. The existing rope and cord page says so plainly, and this page agrees: the lace row covers threading a lace through eyelets, and tying a bow after threading is not part of its description.
The row also names no footwear. The environment examples are garments, towels, cables, form boards and bags, and the row does not say whether the eyelets are on a shoe, a garment, a bag or a form board. Where the lace is threaded, how many eyelets there are and which lacing pattern applies are not stated, so a spec names them.
That matters for a buyer. If your policy needs a lace threaded through a shoe and then tied, the spec has to say so, with where each step starts and ends, and a Spec Pilot proves it against your conditions before you scale. If your policy only needs the threading pass, the row as written already describes it. The second table lists what is and is not stated.
Neighbouring rows
Three further rows on the same bench are fastening or cable tasks and are mentioned here as context only, not as claims of this page. "Fasten buttons/snaps" is described as "Fasten a row of buttons or snaps." and is rated Hard. "Open/close zipper" is described as "Start and run a zipper closed." and is rated Medium. "Coil + Velcro cable" is described as "Over-under coil and strap a cable." and is rated Medium. A fourth, "Route + clip cables", routes cables to a form board and is rated Medium.
All of them use the same capture setup, "Multiview rig + handheld grippers", and are Available on request. The bench lists twelve rows in all; the rest cover folding, flattening, hanging, socks, a duvet cover and wrapping, which handle fabric but do not thread anything.
If your project needs several of these fastening tasks together, the buttons, zippers and fasteners page treats the four fastening rows as its subject. This page takes the lace row on its own, so the spec language, the labels and the failure modes below are written around threading.
Why it is hard
The site makes the central point in its own words: a cable has no single shape, and a lace shares that property. A lace is a long, thin, flexible object, so its form changes as the hands move it, and a camera sees a different shape every few frames. Three consequences show up in the data, and each is something the site already addresses.
First, occlusion. Fingers disappear behind objects in manipulation, which is why 3D hand pose carries a per-joint visibility flag. In a threading task the fingers close around the lace end and the eyelet at the same time, so a hidden joint is the normal case rather than an exception. The flag marks joints that were not seen instead of presenting a guess as a measurement.
Second, coordination. One hand holds the item with the eyelets while the other feeds the lace, so both hands need to be in frame at once. First-person capture keeps both hands and the work in view across the whole attempt, and hand pose is delivered for both hands.
Third, tracking. The site states that clothing, bedding and bags do not track well with masks propagated frame to frame, so deformable captures ship per-frame instance masks where the spec calls for them. A lace is not named in that statement, so whether a lace task asks for them is a spec decision. Metric depth on sub-centimetre parts is flagged rather than interpolated, but whether an eyelet or a lace tip counts as a sub-centimetre part is not stated, and the site gives no mask accuracy figure for laces.
Firsthand captures people, not robots. There is no robot joint-angle log and no teleoperation data for this task, and using the episodes for a specific robot means your own retargeting step.
Capture setup
The catalog lists the capture setup per row, and for "Thread lace eyelets" it is "Multiview rig + handheld grippers". The site explains that setup 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 catalog lists no stereo pair for this row, so this page does not describe the capture as stereo.
The wider stack the site documents is ten streams: a head-mounted global-shutter 4K camera at 60 fps with a 120 degree lens, two wrist-mounted cameras at 1080p and 60 fps, depth, 6-DoF IMU data at 200 Hz, 3D hand and body pose, instance segmentation and action labels, hardware-triggered onto a single PTP clock domain and aligned under 2 ms. The rig is calibrated at the start and end of every session, and an episode is accepted only if RMS reprojection stays under 0.28 px.
Which of those streams apply to a given lace collection, how many cameras are used and what the grippers are is set in the skill spec. The site states no camera count, resolution or frame rate specific to this row, and no gripper detail beyond the sentence above. Force and tactile readings are not among the standard streams.
Episodes and labels
Each attempt is delivered as one episode, and a lace task needs a decision up front about what one attempt is: one eyelet, one pair of eyelets, one full lace threaded through every eyelet, or a threading pass followed by a finishing step. The site does not set that length, so the skill spec does.
Inside the episode, action segments divide the recording into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun. The site states a taxonomy of 97 verbs and 512 nouns, annotated to the frame and human-reviewed. A spec that says only "thread the lace" gives you one long segment. A spec that names the individual steps gives you a sequence you can slice. As an illustration of how a spec can cut an episode, and not as steps the catalog states, it could name laying out the lace, passing it through an eyelet, pulling it through and moving to the next eyelet.
The other standard fields are hand_joints and hand_visible for 3D hand pose, 21 joints per hand with a per-joint visibility flag, contact_events for the moment a hand meets an item, objects, and instance_masks stored at the depth resolution of 848×480 so they line up with the depth stream. Every episode carries int64 nanosecond timestamps per stream, camera intrinsics and extrinsics.
The site lists no label for the lace itself: no threaded or unthreaded state, no eyelet count, no lace tension and no completion score, and no contact force reading. If your pipeline needs one, it is scoped in the spec rather than assumed.
Comparison
Several existing pages touch this task. The buttons, zippers and fasteners page counts four fastening rows, and the lace row is one of them; this page takes that one row as its main subject. The rope and cord page covers the cord-like rows together and states that no knot or shoelace row is listed. The deformable object page covers laundry, bed-making and bag tie. The shoe and footwear repair page covers a different row, "Shoe repair", in the Repair Shop environment, and is about repairing a shoe rather than threading a lace.
The comparison table below sets those pages next to this one. It states each row as the site states it and makes no claim beyond that. If your question is about a single fastener type, this page and the buttons page overlap; if it is about cord handling in general, start with the rope and cord page.
Privacy
Only what the site already states applies. Every participant signs a written release granting commercial training rights before capture begins, and consent artefact IDs link each episode to it. Faces, plates and screens are detected and irreversibly blurred at ingest, speech is scrubbed of names, addresses and card numbers while ambient audio is kept, and a human reviewer confirms that no un-consented person is identifiable in any frame.
Footage that cannot be de-identified is discarded rather than shipped, and the anonymization record is delivered with the data. A second person in frame follows the same rule, and the spec settles the details for your bench. This is not legal advice, and the executed agreement controls.
Speed and licence
The site states one published timeline: from a signed spec to a first validated batch, a median of 48 hours where coverage is deep, and typically three to four weeks where it is thin and contributors need to be recruited first. The site does not say which timeline applies to the Deformables & Textiles Bench, and the row is Available on request, so ask when you request the quote.
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. Collections are billed per validated hour, rejected episodes and recaptures are never billed, and the site states no price list or minimum order for this task. Capture at your own facility is listed as not offered.
Getting started
Start with the free, ungated sample pack to check the loader and the label quality, then move to a Spec Pilot: a small first batch against the written spec that proves the fill rate and the reject rate on your conditions before you scale.
A good brief names the task, the item the eyelets are on, the order of steps, how each step starts and ends, what counts as threaded, whether tying a bow is in scope, and what counts as a reject. The site’s skill-spec guide says to name the verb and the noun rather than a broad activity. Then request a custom dataset, and we quote reach, timeline and price against the spec.
At a glance
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 rows
| Task (as listed) | Description (as listed) | Environment | Skill | Capture setup | Status | Role on this page |
|---|---|---|---|---|---|---|
| Thread lace eyelets | Thread a lace through eyelets. | Deformables & Textiles Bench | Hard | Multiview rig + handheld grippers | Available on request | The row this page covers |
| Fasten buttons/snaps | Fasten a row of buttons or snaps. | Deformables & Textiles Bench | Hard | Multiview rig + handheld grippers | Available on request | Nearby context only |
| Open/close zipper | Start and run a zipper closed. | Deformables & Textiles Bench | Medium | Multiview rig + handheld grippers | Available on request | Nearby context only |
| Coil + Velcro cable | Over-under coil and strap a cable. | Deformables & Textiles Bench | Medium | Multiview rig + handheld grippers | Available on request | Nearby context only |
Row wording
| Topic | What the site states | Where it is settled |
|---|---|---|
| Threading a lace through eyelets | Stated: "Thread a lace through eyelets." | Catalog row |
| Shoelace and footwear | The row names no shoe, boot or footwear | Written skill spec |
| Tying a bow or a knot | No catalog row describes tying a shoelace or a knot | Written skill spec and Spec Pilot |
| Lace type, length or material | Not stated | Written skill spec |
| Eyelet type, count or lacing pattern | Not stated | Written skill spec |
| Attempt length (one eyelet, one pair, one full lace) | Not stated | Written skill spec |
| Task times, success rates, episode or hour counts | Not stated | Quote |
Capture setup
| Part | What the site states |
|---|---|
| Catalog capture setup | Multiview rig + handheld grippers |
| What that setup means | 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 |
| Head camera | Global-shutter 4K at 60 fps with a 120 degree lens |
| Wrist cameras | Two wrist-mounted cameras at 1080p and 60 fps |
| IMU | 6-DoF at 200 Hz |
| Sync | Hardware-triggered onto one PTP clock domain; aligned under 2 ms |
| Calibration | Re-solved at the start and end of every session; accepted only under the 0.28 px RMS reprojection gate |
| Stereo pair | Not stated for this row |
| Camera count, resolution, frame rate and gripper detail for this row | Not stated |
Comparison
| Page | Main subject | Lace threading on that page | How this page differs |
|---|---|---|---|
| This page | The "Thread lace eyelets" row | The main topic | Takes the single lace row and writes the spec, labels and failure modes around threading |
| Egocentric buttons, zippers and fasteners data | Four fastening rows on the cloth bench, all Available on request | One of four rows | That page covers buttons, snaps, a zipper, a lace and a cable strap together |
| Egocentric knot tying and rope handling data | Cord-like rows: cable coil, lace thread, cable route and clip, cable-comb dressing | One of several cord rows | That page states no knot or shoelace row is listed and is about cord handling in general |
| Egocentric deformable object manipulation data | Laundry, bed-making and bag tie | Not its main task list | That page is about soft, shape-changing household items |
| Egocentric shoe repair video data | The "Shoe repair" row in the Repair Shop environment, Hard, Available on request | Not covered | That page is about removing, gluing and stitching shoe parts, not threading a lace |
| Egocentric sewing and textile handling data | Sewing and textile rows | Not covered | Sewing rows join fabric with thread; no lace row is claimed there |
Streams and labels
| Stream or label | What it gives a lace episode | Status |
|---|---|---|
| 3D hand pose, 21 joints per hand, per-joint visibility | Carries how the fingers hold the lace end and the eyelet; occluded fingers flagged | Delivered |
| Contact events | The moment a hand meets an item | Delivered |
| Action segments (start_ns, end_ns, verb, noun) | One labeled span per step; 97 verbs and 512 nouns, human-reviewed | Delivered; frame-accurate |
| Depth with confidence maps | Geometry of the item and the lace, with low-confidence regions masked | Delivered |
| Per-frame instance masks (848×480) | Masks for the lace and the item where the spec calls for them | Delivered where specified |
| Threaded state, eyelet count, lace type | Not listed | Not stated |
| Lace tension, contact force, tactile readings | Not among the standard streams | Not stated |
| Robot or teleoperation data | Human first-person demonstrations only | Not captured |
Spec checklist
| Spec item | Question to settle | How it is settled |
|---|---|---|
| Scope | Threading only, or threading followed by tying a bow | Written in the spec and proven on a Spec Pilot |
| Item | What the eyelets are on | Named in the spec; the row does not say |
| Attempt length | One eyelet, a pair, or a full lace | Named in the spec |
| Step boundaries | Where each action segment starts and ends | Verb and noun per step |
| Accept criteria | What counts as threaded, and what is a reject | Written before capture; QA checks against it |
| Masks | Whether per-frame instance masks are needed for the lace | Decided in the spec |
| Delivery format | How the data is packaged | RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams |
| Privacy | How anyone, faces and screens in frame are handled | Faces, plates and screens blurred at ingest; other items agreed in the spec |
| License | Who owns the dataset | Perpetual, irrevocable, buyer-owned, non-exclusive by default |
Privacy
| Step | What the site states |
|---|---|
| Consent | A signed written release per contributor; consent artefact IDs link each episode to it |
| Faces, plates and screens | Detected and irreversibly blurred at ingest |
| Speech | Scrubbed of names, addresses and card numbers; ambient audio is kept |
| Review | A human reviewer confirms no un-consented person is identifiable in any frame |
| Failures | Footage that cannot be de-identified is discarded |
| Delivered with the data | The anonymization record |
Formats
| Format | What the official documentation states | Used for here |
|---|---|---|
| RLDS | A dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README) | Episode-based training loaders |
| LeRobot | LeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation) | LeRobot dataset format and tooling |
| WebDataset | Tar files in which files that belong together share a basename, split into numbered shards (WebDataset README) | Sharded streaming for large training runs |
| HDF5, zarr and Rerun .rrd | Stated by Firsthand; see the official sites under Sources | Array storage and synchronized playback for review |
Example footage
One real clip already published on this site, shown as a format example: ten seconds of first-person home cooking with faces blurred. It does not show lace threading, eyelets or a cloth bench, and it is not a deformable-object clip.
No lace or eyelet threading clip is published on the site, so this is labelled as a format example. Request a sample to see delivered files. See sample data outputs, request an egocentric data sample.
FAQ
Sources
Tell us the threading steps and where each starts and ends, what the eyelets are on, whether an episode covers one eyelet or a full lace, whether tying a bow is in scope, what counts as threaded, the privacy rule for the bench and for anyone in frame, and the delivery format your stack reads. We will quote reach, timeline and price against a written spec, with a first validated batch proven on a Spec Pilot.