Transcribe a whole back catalogue in one run

Anyone with years of recordings and no text for any of it. The archive is the asset, but one-at-a-time upload means it never gets done.

The flow

1. GrantGive the batch connector a scoped role over the prefix you want — not the whole bucket.
2. EnumerateList the prefix and submit each object with an Idempotency-Key derived from its key, so a resumed run never double-bills.
3. CollectResults land as each job completes; a failed object retries without touching the rest.

# submit — returns immediately, does not block
curl -X POST https://whipscribe.com/api/v1/transcribe/url \
  -H "X-API-Key: $KEY" \
  -H "Idempotency-Key: bulk-transcribe-a-back-catalogue-$SOURCE_ID" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/recording.mp4",
       "word_timestamps":true}'

→ 202 {"job_id":"a1b2…","status":"queued"}

# then poll — a self-serve (Pro) key collects by polling
curl "https://whipscribe.com/api/v1/jobs/$JOB" -H "X-API-Key: $KEY"
→ {"status":"processing"} … {"status":"done"}

What it costs

1,000 hours of archive is about $480 at credit pricing, once, with credits that do not expire if you spread the run. $24 per 5,000 minutes — about $0.29 an audio hour — and credits never expire.

Why this needs an API rather than a person

This is the case with no manual equivalent. Nobody uploads four thousand files by hand.

Build it on