SPEC LIBRARY · LOADING
Loading contentSPEC LIBRARY · LOADING
Loading contentREFERENCE · SPECS & FAQ
A shared reference for the baseline capture, quality, delivery, and rights requirements that physical AI buyers post on truelabel. Individual bounties can override any of these — the bounty’s own capability checklist is always the authoritative requirement list.
SECTION 1
truelabel brokers two economic tracks in parallel. Buyers post a bounty, deposit an escrowed budget, and accept exactly one supplier bid per bounty. Delivery runs through the buyer's storage of record; samples stay on-platform so the buyer's reviewer can validate scope before unlock.
SECTION 2
The spec library covers the modalities most physical-AI labs request. Suppliers check the capabilities they can meet once; truelabel matches each capability vector against every active bounty's requirement list.
SECTION 3
These are the specs most buyers ask for by default. Each bounty can override them — the capability checklist you see on a bounty is the buyer's actual requirement list, not this baseline.
| Resolution | 2 megapixel |
|---|---|
| Frame rate | 30 FPS minimum (avg ≥19.8 FPS after drops) |
| Video codec | MP4 / H.264 — H.265/HEVC and raw frames rejected |
| Diagonal FOV | 120° to 170° (fisheye acceptable if intrinsics provided) |
| Aspect ratio | Landscape |
| Bitrate | 4–8 Mbps |
| GOP length | 30, no B-frames |
| Clip length | 120–3600 s, bounded by semantic tasks |
| Color depth | 8-bit — HDR rejected |
| Pose sample rate | 30 Hz |
| Pose → video sync | ≤1 frame |
| Head IMU sample rate | 100 Hz |
| IMU → video sync | ≤1 ms |
| Head pose odometry | 1% error / distance traveled |
SECTION 4
Bounties run a sample review before the final delivery unlock. Footage or sessions with any of the following characteristics are rejected by most buyers.
SECTION 5
Samples live on truelabel so the buyer can validate scope; full delivery is uploaded to the buyer's own storage (typically Azure Blob or S3) with credentials issued after deal contract execution.
| Sample upload cap | 5 GB per file · 25 GB per ZIP |
|---|---|
| Sample formats accepted | MP4, MCAP, JSON, CSV, ZIP |
| Full delivery | Buyer-hosted storage (credentials post-contract) |
| Required per-session metadata | Environment type, geography, session ID, camera intrinsics, camera extrinsics |
| Preferred container | MCAP with CompressedVideo topic |
SECTION 6
Every deal records consent artifacts per contributor and the rights structure the buyer accepted. Operators review both before the delivery can be marked ACCEPTED.
REFERENCE · FAQ
15questions across getting started, upload, quality, rights & consent, and payment.
Showing all 15 questions.
Egocentric video, head-mounted IMU, head & hands pose, teleoperation trajectories, tactile glove data, and mocap. The full supported list lives in Section 2 above; custom modalities can be added by the operations team on request.
NET_NEW bounties are collected after contract execution and are exclusive to the buyer by default. OFF_THE_SHELF bounties transfer existing datasets that the supplier already holds — faster to close, non-exclusive by default.
Pick EVAL when you need a small, compliant evaluation set with fixed scope and short turnaround. Rate-card priced, escrowed like every other bounty, and typically closes in under two weeks.
Samples are capped at 5 GB per file and 25 GB per ZIP. Full delivery is not uploaded through truelabel — it is transferred directly to the buyer's storage (Azure Blob or S3) with credentials issued post-contract.
MP4 (H.264) for video, MCAP for multi-stream recordings, JSON or CSV for pose/IMU tracks, and ZIP for bundles. H.265/HEVC and raw frame dumps are rejected.
Baseline is ≤1 frame pose-to-video and ≤1 ms IMU-to-video. Individual bounties can loosen or tighten this — check the bounty's capability checklist before bidding.
Yes, provided the supplier delivers lens distortion coefficients and camera intrinsics alongside the footage. Buyers need the calibration data to rectify at training time.
The buyer marks the sample rejected with a reason. The supplier can revise and resubmit within the deal window. Repeated QA failure is grounds to refund the buyer's deposit and terminate the deal.
A common diversity safeguard on NET_NEW bounties: no single contributor may supply more than 100 hours of footage across the lifetime of the dataset. The buyer sets the exact cap on the bounty.
Physical AI training data includes identifiable video of people in homes and workplaces. Buyers require a signed consent artifact per contributor so their legal team can defend downstream use of the data. truelabel stores every consent artifact alongside the deal record for audit.
On /admin/consent the operator can see the list of contributors against the list of consent artifacts received. A deal cannot move to ACCEPTED unless every contributor in the delivery has a matching consent artifact on file.
On NET_NEW bounties, the buyer receives exclusive rights by default. On OFF_THE_SHELF, the supplier retains the ability to resell to other buyers unless the bounty explicitly purchases exclusivity.
The buyer's deposit is held in a Stripe Connect escrow. Funds release to the supplier when the buyer marks the delivery ACCEPTED — typically per approved batch on net-30 terms.
Yes. If QA fails or the supplier breaches the deal contract, an operator can initiate a Stripe refund against the escrowed deposit. The Stripe webhook is the sole writer of refund state.
Every bounty has a /bounty/[id] status page that shows the current phase (ACTIVE, AWARDED, IN_DELIVERY, ACCEPTED), the matched suppliers, and any live deals. Status transitions are visible in the bounty timeline.