STT 1.0 or video inspect transcribe: two ways to transcribe on Sume
Both bill about $0.01 per audio minute on Sume, but STT takes an audio URL and video inspect takes a Sume clip. Limits of 10 minutes and 1,800 seconds.

Sume has two transcription paths that look alike. POST /v1/stt-1.0/transcribe is the standalone speech-to-text model. POST /v1/video-inspect with transcribe: true runs the same Sume STT 1.0 on the audio of one video clip. Both price the transcript at $0.01 per audio minute (read 2026-10-07 from the video inspect docs and the repo's catalog), and both can return word timings and sentence segments. The differences are in what you hand them and what else gets billed.
Side by side, read 2026-10-07
| STT 1.0 | Video inspect with transcribe | |
|---|---|---|
| Input | Public HTTPS audio_url, Sume media URL preferred | One media.sume.com video in your workspace |
| Transcript rate | $0.01 per audio minute | $0.01 per audio minute (frozen at the STT 1.0 rate) |
| Other charges | None | The inspect's own Modal compute at list x 1.25 plus the platform fee |
| Length | Up to 10 minutes per job | Source up to 1,800 s; duration hint up to 600 s |
| Duration hint | duration_seconds 1 to 600; omitted reserves 1 minute | Same; omitted reserves 1 minute |
| Extras | language_code, segmentation | Probe, up to 24 stills (frames: false skips them), language_code, segmentation |
| Silent input | Not covered in the docs | Fails with inspect_source_has_no_audio |
Choose by what you already have
If you hold a recording, call STT: one job, one rate, nothing else on the invoice. If you hold a video and also want its probe and stills, call inspect with transcribe: true, and accept that the inspect's compute is billed beside the minute rate. If you hold a long video and only want the words, detach the audio first (POST /v1/audio-detach, $0.01) with format: wav, channels: mono and sample_rate: 16000, then send that file to STT.
Either way, ask for sentence segments with segmentation: {"mode": "sentence"} when you want caption-shaped lines. The transcript output is text, language_code, words[] as {word, start, end} and segments[] as {index, text, start, end, duration_seconds}.
curl -X POST https://api.sume.com/v1/video-inspect \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: inspect-talk-001" \
-d '{"video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4", "frames": false, "transcribe": true, "duration_seconds": 120, "segmentation": {"mode": "sentence"}}'What a 10-minute job costs
A 10-minute recording through STT 1.0 is $0.10. The same minutes through inspect are $0.10 of transcript plus the compute of the inspect job. If both are billed to the cent, STT is the cheaper path for pure transcription by that compute amount. If the clip is already a video in your library, inspect saves you the detach step and gives you stills in the same call.
Sources
Related posts
More in Developers
- Submit 40 image jobs with mode webhook in Python on Sume
Send 40 POST /v1/images calls with mode webhook and a webhook_url: each returns a 202 job envelope at once and the result follows. Python, cost, status codes.
- Submit 6 ad hooks in parallel in Python with one Idempotency-Key each
A Python script that submits six 3-second Omni hook jobs in parallel, each with its own Idempotency-Key so a retry replays the original job. Cost: $2.25.
- Submit a Sume video job from PHP with cURL: sume/auto and polling
Replace a Sora call in a PHP worker with Sume /v1/videos: submit with cURL, poll the job, read the download URL, and know what a default clip costs.
- Submit and poll a Sume video job from Rust with reqwest
Rust reqwest blocking client for Sume /v1/videos: submit a sume/auto job, poll until completed, print the download URL and usage.cost. Cargo features listed.
Written by Sume