✦  Whisper speech-to-text is live in the model catalog — run it on the fleet today

Enrich millions of data points
in seconds

Run vision, speech, and text models on Bright Data’s global compute fleet. Submit raw video, audio, images, or documents — the platform preprocesses, distributes, and collects results at fleet scale. One API.

Onboarding is personal — we provision your account and first project with you.
Catalog models ready to run vision · speech · text · documents
Batch at fleet scale millions of items per job
Built-in preprocessing video, PDF, audio & images
Per-completed-task billing no idle infrastructure cost
Distributed across Bright Data’s peer-device network
CPU devices GPU devices (DirectML · CUDA) Devices across the globe

What Bright Compute gives you

Submit your data to a catalog model or your own — the platform handles preprocessing, distribution across the fleet, and results collection. One API for batch pipelines, real-time inference, and model training.

  • Batch inference — millions of items from a manifest, zip, or cloud folder
  • Real-time inference pools — sized to your request rate, warmed and ready
  • Catalog models — permissively licensed vision, speech, and text models
  • Bring your own model — versioned uploads, one model behind many projects
Get access  ›
Batchasync · millions of items
Real-timesub-second latency pools
Trainingdistributed fine-tuning
Model catalog
Vision Speech Text & NLP Documents
Example: speech-to-text pipeline
📁
Your source
Bright Data Scraper API · Datasets · manifest URL · zip · S3 · Google Drive
↓
⚙️
Server-side preprocess
audio extract · VAD segment · normalize
↓
🌐
Peer-device inference
distributed across peer devices
↓
✅
Results
poll · webhook · durable storage

How it fits your data pipeline

Your data arrives in its original form. The platform extracts, segments, and normalizes it server-side — then fans it across the peer-device network. No preprocessing code to write or manage.

  • Video files → audio extraction → VAD utterance segmentation
  • PDF documents → per-page images → classification or OCR
  • Raw audio → format normalization → speech transcription
  • Any source: Bright Data Scraper API, Datasets, zip archive, manifest URL, S3, or Google Drive

Why Bright Compute

Bright Compute connects natively to the data infrastructure you already have — and scales to match AI-sized workloads, task by task.

  • Fully integrated with the data you already have — connects natively to Bright Data Scraper APIs and Datasets, so you can enrich data as it’s collected, no export/import step, no separate pipeline to maintain. (Standalone use — bring your own data — is fully supported too.)
  • Scale that matches AI-sized workloads — tasks run in parallel across a massively distributed peer network; process a million records in seconds, not the hours or days a sequential GPU-hour model implies
  • Pay per task, not per hour — no infrastructure to size, no idle GPU-hours to pay for; your cost-per-record is known before you run the job, and your ROI is obvious from day one
  • One pipeline, not three vendors — most teams stitch together a scraper, a GPU rental, and a labeling vendor; Bright Compute collapses that into a single flow — source it, enrich it, ship it
  • For workloads that must stay within managed infrastructure — no peer devices — the Premium tier runs on dedicated, Bright-managed servers
# per-job billing — no wasted spend POST /api/v1/inference/batch { "project_id": "my-transcription", "data_source": { "manifest_url": "…/audio-files.jsonl" } } # → 202 { "job_id": "…" } # poll /api/v1/inference/{id} or await webhook # billed only for completed tasks
Use cases

See it in action

Catalog models run out of the box — pick a use case, create a project, and submit your data.

Audio Transcription

Convert speech files — interviews, call recordings, podcasts, or broadcast audio — to text at scale. Supports multiple languages and speaker formats.

catalog-whisper-tiny catalog-parakeet-tdt-06b-v3

Object & Logo Detection

Detect and locate objects or brand logos in images. Fast bounding-box detection for large image datasets with low per-task cost.

catalog-yolox-nano catalog-clip-image

Text Classification & Sentiment

Classify documents, product reviews, or support messages by topic or sentiment. Embed passages for downstream ranking or clustering.

catalog-distilbert-sst2 catalog-minilm-l6

Image Classification & Moderation

Label images by category or screen content for sensitive material at scale. Open-vocabulary: use your own label set without retraining.

catalog-mobilenetv2 catalog-nsfw

Visual Similarity & Dedup

Embed images to detect near-duplicates or power a visual search index. High-quality embeddings for similarity ranking and clustering.

catalog-dinov2-giant catalog-clip-image

Semantic Search

Embed text passages for semantic similarity ranking and retrieval. Power search, recommendation, and RAG pipelines over large text corpora.

catalog-minilm-l6

Language Detection

Identify the language of any text passage — 20 languages, high accuracy, at batch scale. Useful for routing, filtering, and multilingual dataset cleanup.

catalog-langid
Coming soon

Document Parsing

Extract structured data from page images, tables, and complex layouts. Layout- and table-aware — handles scanned PDFs and multi-column documents.

catalog-paddleocr-vl
Coming soon

Summarize, Extract & Categorize

Summarize long documents, extract structured fields, or categorize content using an instruction-tuned LLM — all via the same batch API.

catalog-qwen25-7b
Getting started

How it works

Four steps from data to results — no infrastructure to manage.

  1. 1

    Get your API key

    Sign in at app.dcmp.brightdata.com, go to Settings → API Keys, and create a key with inference permissions.

  2. 2

    Create a project

    Choose a catalog model — or upload your own — and set the compute tier. The project holds the model, tier, and pipeline configuration.

  3. 3

    Submit a batch

    Point the API at a manifest URL, zip archive, S3 bucket, or Google Drive folder. You get a job ID back immediately — the platform handles the rest.

  4. 4

    Collect results

    Poll the job endpoint or configure a webhook for completion events. Results are durable — access them any time after the job finishes.

# 1 — create a transcription project curl -sX POST https://api.dcmp.brightdata.com/api/v1/projects/new \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "Transcription", "type": "batch", "model_id": "catalog-whisper-tiny", "project_id": "my-transcription" }' # → {"project_id":"my-transcription", …} # 2 — submit a batch from a manifest URL curl -sX POST https://api.dcmp.brightdata.com/api/v1/inference/batch \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "project_id": "my-transcription", "data_source": { "manifest_url": "https://…/audio-files.jsonl" } }' # → 202 {"job_id":"…","poll_url":"/api/v1/inference/{id}"}
Preprocessing

Handles messy real-world data

Real-world data isn’t clean tensors. Submit raw files — the platform preprocesses server-side before inference ever touches a device.

Video

FFmpeg audio extraction + Silero VAD utterance segmentation — one video file becomes many discrete utterances, each a separate inference task.

PDF & Documents

Pages rendered to images, type-classified, and dispatched one per task. Multi-column, scanned, and mixed-layout documents handled automatically.

Audio

Format normalization, silence trimming, and speech-activity segmentation — any audio codec in, clean utterance segments out.

Images

Any format decoded, resized, and normalized to model-input tensors. Preprocessing chains validated at project creation, not at submit time.

Any source

Manifest URLs (JSONL), zip archives, S3 buckets (IAM role-based), and Google Drive folders — the platform fetches and fans out automatically.

Validated pipelines

Declare the input type at project creation — preprocessing chains resolve and validate immediately, so bad config is caught before any data moves.

Pricing

Pay per task, not per hour

Priced by task complexity — no reserved infrastructure, no idle charges. Volume pricing available; contact us for rates.

Lightweight

Language identification, text classification, and embeddings. Tasks that run efficiently on CPU-class peer devices.

  • Language identification
  • Text classification & sentiment
  • Embeddings at scale
  • Per-completed-task billing
Advanced

Speech transcription, high-accuracy embeddings, and LLM-based extraction. Tasks requiring dedicated GPU capacity.

  • Speech transcription (Whisper)
  • High-accuracy embeddings
  • LLM-based extraction & summarization
  • Per-completed-task billing
FAQ

Frequently asked questions

What models are available in the catalog?
The catalog includes permissively-licensed models across vision (MobileNetV2, YOLOX-Nano, CLIP, DINOv2, NSFW, SigLIP), speech (Whisper-tiny, Whisper large-v3, Parakeet-TDT 0.6B, Silero VAD), text (DistilBERT SST-2, MiniLM-L6), and document parsing (PaddleOCR-VL — coming soon). The full catalog with availability and metadata is visible in the control panel and via GET /api/v1/catalog.
Can I use my own model?
Yes. Upload your model via POST /api/v1/models/upload-token, give it a name, and use the returned model_id when creating a project. Uploaded models are versioned, account-scoped, and one model can back any number of projects.
What input formats and data sources are supported?
Data sources: inline items (~35 images per call), manifest URLs (JSONL, up to 1 M items), zip archives, S3 buckets (IAM role), and Google Drive folders. Input formats: images (JPEG, PNG, WebP, and more), audio (MP3, WAV, FLAC, OGG), video (MP4, MKV, WebM), and PDF. The platform decodes and normalizes before dispatch — you submit the file as-is.
How is billing calculated?
You are billed per completed task — a task is one item through one inference pass. Preprocessing steps do not generate separate charges. Rates vary by task complexity tier (Lightweight / Standard / Advanced). Failed or cancelled tasks are not charged. Contact us for current rates and volume pricing.
Is my data processed securely?
The platform is multi-tenant and project-isolated: your data, results, and API keys are scoped to your account. Inference payloads are encrypted in transit. For batch inference, inputs are normalized server-side before dispatch — raw source files are not forwarded to peer devices. For workloads where sensitive data must not run on peer devices, a premium option exists to keep all processing within Bright-managed infrastructure. For compliance or data-residency questions, contact us.
What compute tiers are available and how do I choose?
Three tiers, priced by task complexity: Lightweight (language ID, text classification, embeddings — runs on CPU-class peer devices), Standard (image classification, object detection, sentiment — runs on GPU-capable peer devices), and Advanced (transcription, high-accuracy embeddings, LLM-based extraction — dedicated GPU capacity). Tier is set on the project, not per-submit. The auto tier selects the appropriate complexity class automatically.

Start enriching your data at scale

Talk to us about your use case. We’ll provision your account, walk through the API, and validate your first batch before you scale.