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

Apply to capture

Hard task

Stereo Titration and Reagent Weighing Data

Titrating a sample to a colour endpoint and weighing a reagent on a balance are two bench tasks the site’s task catalog lists as their own rows, both rated Hard. This page covers the stereo and MCAP side of those two rows: what a calibrated stereo pair adds to stereo titration video, what the catalog states about capture, what MCAP is according to its own documentation and what the site does not state. We collect it as custom lab data on demand, to a written skill spec, as custom lab data collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Catalog rows
Titrate to endpoint and Weigh reagent, in Wet Lab & Clinical Bench
Skill and status
Both Hard; both 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 titration and weighing video?

01

Depth for the sample, the vessel and the hands

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the sample, the vessel and the hands sit in one frame. It gives no depth accuracy figure for these rows.

02

Fingers hidden by small items, 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 hidden finger is marked as hidden rather than silently filled in.

03

Two tasks, each its own labeled span

Titrating to a colour endpoint and weighing a reagent are separate catalog rows. Action segments carry start_ns, end_ns, verb and noun, so each task can be its own 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 titration and reagent weighing data?

It is first-person video of a person doing the work named in two catalog rows, titrating a sample to a colour endpoint and weighing a reagent on a balance, recorded with two calibrated cameras and with hand pose and sensor streams alongside. People reach it through several phrasings: stereo titration video, reagent weighing robot data, a wet lab bench dataset or custom lab 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 these rows. The catalog lists a multiview rig with handheld grippers for both Wet Lab rows, so a stereo pair reaches them only through the site’s general stereo offer, agreed in the skill spec and confirmed on a Spec Pilot. The data is human capture by paid, consented contributors. It is not robot or teleoperation data, and this page makes no claim that any robot has been trained on it or that any robot titrates or weighs. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Catalog rows

Which catalog rows cover titration and reagent weighing, and what do they say?

Two rows sit in the Wet Lab & Clinical Bench environment, in the Healthcare & Life Sciences sector. "Titrate to endpoint" reads: "Titrate a sample to a colour endpoint." "Weigh reagent" reads: "Weigh a reagent on a balance." Both are rated Hard, both list the capture as Multiview rig + handheld grippers, and both are Available on request. The environment’s shared example line reads "Burette, pipettes, balance, labware, phantom for any invasive step". It is one line for every row in that environment, so it is quoted here rather than assigned to a single task.

A third row sits in the Pharmacy & Laboratory environment: "Lab protocols (pipetting, titration, sample handling)", which reads "Pipette reagents, titrate to endpoint and handle samples following the written protocol." It is rated Hard, lists Phone (head-mounted) / multiview rig and is Available on request. It is a broader row that mentions titration as one part of a written protocol, and it is covered in more depth on the stereo lab pipetting page. The first table below reproduces all three rows as the catalog states them.

Available on request means the work is scoped and recruited to spec when a buyer asks. It is a statement about the catalog row, not a promise of a delivery date, and it does not mean a stock of titration or weighing footage exists. This page claims no volume, hours or delivered stereo footage for either row. The rows name a sample, a colour endpoint, a reagent and a balance. They name no chemical, no concentration, no quantity and no instrument model, so if your program needs one, it is written into the skill spec rather than assumed.

Why it is hard

Why are titration and reagent weighing listed as Hard?

The site’s answer is the Skill column. The catalog rates both rows Hard, and that is all "Hard" means here. This page imports no outside rubric and states no failure rate, tolerance or claim about how skilled any worker is. What the site does say is in the row text. The titration row is defined by an endpoint that is a colour, so the end of the task is a visual state of the sample and not a count or a position. The weighing row is defined by a reagent on a balance. The site publishes no reading, no limit and no step list for either.

The site’s lab and capture copy adds two things that bear on stereo recording. The first is that the hands occlude the work and fingers disappear behind objects, which is why hand pose carries a per-joint visibility flag. The second is that depth degrades on wet and reflective surfaces, with a confidence map delivered so low-confidence regions can be masked. The failure-mode table below maps each difficulty to the stream or label the site already states, and says Not stated where nothing is.

Difference

How is this different from the egocentric titration page and the stereo lab pipetting page?

This page is the stereo and MCAP treatment of the same two rows the egocentric titration and reagent weighing page covers. That page is the first-person, non-stereo page for the task, and it is where the two Hard-row links in the hard-task hub point. This page does not replace it. It is for a buyer who wants a calibrated pair, depth and an MCAP file.

The stereo lab pipetting and sample handling page covers seven rows centred on pipetting, liquid handling and sample tubes, and it names titration only as part of the broader lab protocols row. Here the subject is the two rows, Titrate to endpoint and Weigh reagent. The second table below sets the pages side by side.

Capture setup

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

The catalog lists Multiview rig + handheld grippers for both Wet Lab & Clinical Bench rows and Phone (head-mounted) / multiview rig for the broader Pharmacy & Laboratory row. The site describes the first 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 does not state a stereo pair for any of these rows. Stereo applies through the general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The site also states that Firsthand does not capture at a customer’s own facility, so the setting is agreed in the spec.

The site describes two stereo setups and does not say which one an order for these rows 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 a stereo pair is worn, mounted or combined with the handheld grippers named in the catalog is Not stated, and so is how hand pose is recorded when the operator holds a gripper. Confirm all of it in the skill spec.

Why stereo

Why capture titration and reagent weighing in stereo?

Bench work is about where the hands meet small items: how a vessel is held, how a sample is steadied, where a reagent sits relative to a balance. 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 these rows, so what a buyer does with that depth is their pipeline’s question.

A stereo pair adds depth, not a verdict. The titration row ends on a colour, and a depth stream does not label a colour. The site lists no colour, endpoint, reading, volume or result label for these rows, and none is claimed. The egocentric titration page already supplies the first-person framing; stereo is the addition for a buyer who wants depth from a calibrated pair and the MCAP file.

Steps and episodes

What does an episode contain, and which steps can a stereo spec label?

The standard episode carries action segments, 3D hand pose for both hands with a per-joint visibility flag, contact events that mark when a hand meets an item, an objects list, and per-frame instance masks stored at the depth resolution of 848×480. Hand pose is 21 joints per hand, 3D, in metres in the head-camera frame. Action segments divide an episode into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun.

The two rows give a natural cut: one titration task and one weighing task. A spec that says "do the protocol" gives one long action segment. A spec that names the steps gives a sequence you can slice by step. Whether an episode covers one weighing, one titration or a longer run of both is a spec decision, because the site sets no episode length. The site lists no label for the outcome of a step, such as whether an endpoint was reached or what a balance displayed, so ask for any such label in the spec.

Occlusion and surfaces

What do the hands, small items and wet or reflective surfaces do to visibility?

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.

The site states that depth degrades on wet and reflective surfaces and that glare-heavy and low-texture scenes make single-frame depth worse, with confidence maps masking low-confidence regions. It does not state how depth behaves on glassware, on a liquid in a vessel or on a balance display, and the catalog row text does not describe the vessel material. If your policy depends on any of these, say so in the spec and settle it on a Spec Pilot. Lighting and bench layout for these rows are Not stated.

Validation

How is the data validated and accepted?

Validation runs against signed accept criteria written into the spec before capture, and a reject log ships with each batch. Calibration is solved at the start and end of every session under a 0.28 px RMS reprojection gate. Episodes are machine-checked against stated reject criteria, such as a sync breach beyond the ceiling for more than three consecutive frames, the manipulated object out of frame for more than 15 percent of the episode, or more than 35 percent of depth pixels in the manipulation region invalid, and a human reviewer then checks each one. Only footage that clears the criteria is billed as a validated hour.

For these rows, the spec has to say which item counts as the manipulated object at each step and where the manipulation region is, because the sample, the reagent and the balance are different items at different moments. What counts as a reached endpoint or a finished weighing is also written down, since the site states no outcome definition. Rejected items are recaptured at the provider’s cost, and the site states no accuracy figure for step labels, so what counts as a pass for a step boundary is set in the accept criteria.

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 egocentric stereo data in MCAP page and the glossary entry cover the format in full.

Streams

Which streams can ship in an MCAP delivery of titration and weighing data?

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For these rows 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 stream-map table below sets each stream beside what the site states about it.

Delivery and license

Which formats and license apply?

Delivery is in the format your stack already reads: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams with metadata, with readable converter source alongside, and MCAP can be the only delivery or sit beside one of them. The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term. The executed agreement controls.

Official documentation for MCAP, RLDS, LeRobot and WebDataset is linked in the sources below. Because the data is human capture, using it for a specific robot still needs your own retargeting step.

Capture and privacy

How are contributors and their work protected?

Every contributor signs a written release, and each delivered episode links to it through consent artefact IDs. At ingest, automated detection finds faces, plates and screens and blurs them irreversibly, and speech is scrubbed of names, addresses and card numbers. A human reviewer confirms that no un-consented person is identifiable in any frame, footage that cannot be de-identified is discarded, and the anonymization record ships with the data.

Container labels and the readout of a balance in frame are not listed as blur categories, so this page does not claim they are blurred. Raise them in the spec if they matter. The catalog notes that the Pharmacy & Laboratory work requires regulatory compliance, and this page makes no regulatory, laboratory-practice, biosafety, clinical or diagnostic claim of its own. It gives no instructions for any step. None of this is legal advice.

Speed and scale

How fast and at what scale can a custom stereo titration and weighing dataset be collected?

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 titration or reagent weighing 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.

Titration and reagent weighing are custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. From signed spec to first validated batch, the published timeline is a median of 48 hours where coverage is deep and three to four weeks where it is thin and contributors need to be recruited first. Both rows are Available on request, so the range that applies is confirmed when the spec is quoted. After a first batch, on-demand top-ups run against the same accept criteria. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Ordering

How do you order a stereo titration and reagent weighing dataset?

Describe the steps and where each starts and ends, what you expect to see as the sample, the reagent and the balance, whether an episode covers one task or a run of both, what counts as the object and what counts as a finished step, the privacy rule for the space and 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 RLDS, LeRobot or WebDataset.

Most programs begin with a Spec Pilot, a small, fast first batch that proves the spec and the accept criteria on real footage before volume scales. The last table below shows what each spec element decides. Our skill spec guide walks through how to write one.

At a glance

What you get.

Catalog row: Titrate to endpoint
"Titrate to endpoint" (Wet Lab & Clinical Bench, Healthcare & Life Sciences): "Titrate a sample to a colour endpoint."; Hard; Multiview rig + handheld grippers; Available on request
Catalog row: Weigh reagent
"Weigh reagent" (Wet Lab & Clinical Bench, Healthcare & Life Sciences): "Weigh a reagent on a balance."; Hard; Multiview rig + handheld grippers; Available on request
Broader catalog row
"Lab protocols (pipetting, titration, sample handling)" (Pharmacy & Laboratory): "Pipette reagents, titrate to endpoint and handle samples following the written protocol."; Hard; Phone (head-mounted) / multiview rig; Available on request
Catalog capture setup
The site states no stereo pair for these rows, 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
Reagent, chemical or concentration names, balance or glassware brands, accuracy or precision figures
Not stated; agreed in the skill spec
Colour, endpoint or balance-reading labels
Not stated; no such label is listed
GLP, laboratory-practice, safety or regulatory claims
Not stated
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.

Live catalog rows

Stated row × description × skill × capture × status

The two Wet Lab rows and the broader Pharmacy & Laboratory row as the task catalog states them, reproduced without change.
TaskDescriptionEnvironmentSkillCaptureStatus
Titrate to endpointTitrate a sample to a colour endpoint.Wet Lab & Clinical BenchHardMultiview rig + handheld grippersAvailable on request
Weigh reagentWeigh a reagent on a balance.Wet Lab & Clinical BenchHardMultiview rig + handheld grippersAvailable on request
Lab protocols (pipetting, titration, sample handling)Pipette reagents, titrate to endpoint and handle samples following the written protocol.Pharmacy & LaboratoryHardPhone (head-mounted) / multiview rigAvailable on request

Compared pages

How does this page differ from the egocentric titration and stereo pipetting pages?

Each page and what it covers. Statuses are as the site lists them; none of these pages is claimed to hold delivered hours here.
PageWhat it coversWhere titration and weighing appearRelation to this page
This page: stereo titration and reagent weighing dataThe Titrate to endpoint and Weigh reagent rows, with a stereo pair and MCAP deliveryThe whole pageStereo pair and MCAP treatment of the two rows
Egocentric titration and reagent weighing dataThe same two rows as first-person videoThe whole pageNot stereo as its subject; the page the hard-task hub rows link to
Stereo lab pipetting and sample handling dataSeven rows: pipetting, liquid handling, lab protocols and four sample-tube rows, with a stereo pair and MCAPNamed only inside the broader lab protocols rowSame stereo and MCAP treatment, different bench tasks
Egocentric lab pipetting and sample handling dataFourteen lab rows as first-person videoTwo of fourteen rowsBroader first-person page for the same bench
Stereo microbiology slide and plate streaking dataPrepare a slide and Swab + streak plate, in stereoNot coveredNeighbouring Hard rows, not titration or weighing
Egocentric stereo data in MCAPThe stereo and MCAP hub across tasksNot specific to lab workGeneral stereo and MCAP treatment

Stated vs not stated

What the site states about stereo capture for titration and reagent weighing

Left to right: the item, what the site states, and what that means for an order. “Not stated” means the site does not say.
ItemWhat the site statesFor a titration and weighing order
Catalog capture setupMultiview rig + handheld grippers on both Wet Lab rows; Phone (head-mounted) / multiview rig on the Pharmacy & Laboratory rowNo stereo pair is stated for these rows; 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
Stereo with handheld grippersNot statedNot claimed; confirmed in the skill spec and on a Spec Pilot
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
Depth on wet or reflective surfacesDepth degrades on wet and reflective surfaces; confidence maps mask low-confidence regionsStated; behaviour on glassware, a liquid in a vessel or a balance display 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 statusBoth Wet Lab rows and the broader row are Available on requestNo volume, hours or delivered stereo footage is claimed on this page
Sample, reagent, chemical or concentration names; balance or glassware brandsNot statedNot claimed; set in the spec
Colour, endpoint or balance-reading labelsNot stated; no such label is listed for the rowsNot claimed; set in the spec
Accuracy, precision, cycle time, error rateNot statedNot claimed on this page
Laboratory-practice, safety or regulatory claimsNot stated; the catalog notes only that pharmacy and laboratory work requires regulatory complianceNot claimed on this page
MCAP topics, schemas, ratesNot statedAgreed in the skill spec

Stream map

Streams for titration and weighing 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 stereo bench 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 hide the sample or the reagentPer-joint visibility flag on hand pose; per-frame instance masksA hidden joint flagged as hidden, not guessed
Sample or balance out of frameEpisode 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
Reaching a colour endpointThe end of the titration is a colour; no colour or endpoint label is listedAction segments and instance masks; any outcome label is set in the spec
Reading the balanceNo label for a displayed value is listedNot claimed; raise in the spec
Weak depth on wet or reflective surfacesDepth degrades on wet and reflective surfaces; confidence maps mask low-confidence regionsBehaviour on a given vessel or bench surface: Not stated
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 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
Grip and handling forceNo force or tactile stream is listedNot claimed on this page

Skill spec

What the skill spec fixes for a stereo titration and weighing 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
RowsTitrate to endpoint, Weigh reagent or both, worded as the catalog words themSet per program; Available on request as listed
Steps and orderWhat one step is, and where each starts and endsEpisode boundaries and action segments; set per program
Episode scopeOne task or a run of bothSet per program; the site does not state an episode length
Object definitionWhether the sample, the reagent or the balance counts as the object at each stepContact events and the out-of-frame reject rule; set per program
Finished-step definitionWhat counts as a reached endpoint or a finished weighingAccept criteria; the site states no outcome definition
Items and materialsWhich samples, reagents and equipment appearSet per program; names, brands and quantities are Not stated on the site
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 these rows
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 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 titration, weighing, a lab bench or any lab work.

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

No titration or weighing 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 titration and reagent weighing data, answered.

What is stereo titration and reagent weighing data?
First-person video from two calibrated cameras of a paid, consented contributor titrating a sample to a colour endpoint and weighing a reagent on a balance, with depth and hand pose alongside.
Which catalog rows cover it, and what is their status?
Two rows in Wet Lab & Clinical Bench: "Titrate to endpoint" ("Titrate a sample to a colour endpoint.") and "Weigh reagent" ("Weigh a reagent on a balance."). Both are rated Hard and both are Available on request. This page claims no delivered hours.
Is stereo already captured on these rows?
Not stated. The catalog lists Multiview rig + handheld grippers for both Wet Lab rows. 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 titration page?
The egocentric titration and reagent weighing page covers the same two rows as first-person video, not stereo as its subject. This page is the stereo and MCAP treatment, and the hard-task hub rows keep linking to the egocentric page.
Does the data include endpoint, colour or balance-reading labels?
Not stated. The site lists action segments, hand pose, contact events and instance masks, and no label for a colour change, a reached endpoint or a displayed reading. Ask for any such label in the spec.
Is there an off-the-shelf titration or weighing dataset?
No listed dataset names titration or reagent weighing. This is custom collection, at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
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.
How fast can a fast, on-demand stereo titration and weighing dataset arrive?
A median of a median of 48 hours from signed spec to first validated batch where coverage is deep, and three to four weeks where it is thin. Both rows are Available on request, so the range is confirmed when the spec is quoted.

Sources

Where is MCAP documented?

Request a custom stereo titration and reagent weighing dataset.

Tell us the steps and where each starts and ends, what you expect to see as the sample, the reagent and the balance, whether an episode covers one task or a run, 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.