Most teams do not need more data. They need the twelve minutes, the one shelf, the one form their model keeps failing on — the accent, the noise floor, the lighting, the phrasing. Say which one, and we go and collect it.
Grouped by modality. Every line is priced by the unit it is delivered in, with its lead time on the card and the contributor rate on the quote.
Recorded calls between a caller and an agent, both sides on separate channels.
Unscripted speech from real speakers — the hesitations, restarts and overlaps scripts never produce.
Targeted read and prompted speech to fill the accents your model drops.
The same script recorded in a car, a warehouse, a call centre and a kitchen.
Your audio, transcribed and speaker-attributed to a written standard.
The tokens that carry the transaction — account numbers, amounts, drug names, SKUs, intents.
Side-by-side judgments on model replies: which one a customer would accept.
Callers who lie, push, spoof and hand the phone to someone else mid-call.
Photographs to a spec — shelves, interiors, objects — on the devices and in the light your users actually have.
Receipts, forms and IDs photographed the way people actually photograph them, redacted to spec.
Multi-turn conversations and instructions authored by people who work in the sector, in its register.
Transcripts paired with the audio they came from, or written to a scenario where no audio exists.
Not the dataset — the call your model gets wrong. A clip is enough to start.
Quantity, locales, conditions, annotation schema, and the contributor rate you will be paying.
5% of the volume, delivered first, so the schema breaks early instead of at the end.
Weekly drops into your bucket, each with an agreement report and the reviewer chain attached.
These are the defaults for speech, and the pattern for everything else. Every one of them is negotiable in the written spec we agree before the pilot — but nobody should have to ask what a delivery contains.
16-bit PCM WAV at 16 kHz by default, 48 kHz on request. Mono, or two-channel where both sides were recorded separately. Original device capture is kept alongside anything we resample.
UTF-8 JSON per clip, with a plain-text and CSV mirror. Verbatim by default: fillers, repeats and false starts stay, and [pause], [overlap] and noise tags follow one written convention agreed in the spec.
Start and end timestamps on every word, so accuracy and latency can be scored apart. Speaker turns and diarization labels ride in the same file.
One row per clip: duration, locale, speaker profile, device, acoustic condition, consent reference and the reviewer chain that signed it off.
Per batch: QA-sample accuracy, WER against the adjudicated reference, inter-annotator agreement on the double-passed portion, rework rate, and what was rejected and why.
Weekly drops to your S3 or GCS bucket, or ours with time-boxed credentials. Data stays in the region agreed at kickoff.
You get a perpetual, non-exclusive licence for internal model development and evaluation. Exclusive and time-limited-exclusive terms exist — ask, and they are priced on the order form.
Read the termsEvery contributor consents on the recording, before they speak, to exactly this use. Consent is stored with the file and referenced in the manifest, and it can be withdrawn — which is why the consent is taken up front rather than after.
Read the privacy policyA collection is pinned to one region at kickoff — EU, US or India — and the audio, transcripts and labels stay in it. Graders stream the clip rather than copy it.
Data residencyThe pilot batch is 5% of the volume and it exists to break the schema early. If it comes back wrong, we fix the spec and re-run it before the main volume starts — that is what the pilot is for.
Send one input your model handles badly. We will tell you what would fix it, and what it would cost — before anyone signs anything.