16 team meetings of 40 minutes a month: transcript cost

Transcribing 16 team meetings of 40 minutes each is 640 audio minutes, or 10.67 hours, which costs $5.76 on MAI-Transcribe-2-Streaming and $6.40 on Sume STT 1.0 in 64 ten-minute jobs.

Meetings are the case where the 10-minute job size shapes the workflow most, because every meeting needs four chunks.

The arithmetic

MAI-Transcribe-2-Streaming is priced per hour, Sume STT 1.0 per audio minute, so the sums convert minutes to hours first. The Sume rate is the public rate on the Sume docs; confirm the live number in GET /v1/catalog.

Per minute, MAI works out to $0.009 ($0.54 / 60) against Sume's $0.01, so Sume is about 11 percent higher. On this run the difference is $0.64. Microsoft's rate is an introductory price that its page says runs through the end of the year, and the page does not say what the price becomes afterward, so a budget past December should not assume it.

Chunking meetings without losing words

A job takes at most 10 minutes of audio, so cut at a natural pause near each 10-minute point and keep the range offsets.

Sume gives no speaker labels, so plan on one recording per speaker, or label speakers by hand in review.

• Four jobs per meeting means four idempotency keys; use meeting id plus chunk index.
• Join the four word arrays by adding each range's start time to its word times.

Limits that shape a Sume run

Sume does not list MAI-Transcribe-2-Streaming, so the MAI row is a price reference. Sume STT 1.0 takes a public HTTPS audio_url and returns the transcript with word timings; there is no flag for timings because they always come back. Sentence segments are available when you send segmentation.

• duration_seconds is an optional hint from 1 to 600; leave it out and Sume reserves one minute, so send it for a long file.
• language_code is a hint such as en or ko; leave it out for auto-detect.
• diarize and tag_audio_events are fixed server-side, so do not send them; there are no speaker-label controls.
• The MAI price is an introductory rate that Microsoft says runs through the end of the year.

Running it

Submit with stt_create and an idempotency_key, wait with jobs_wait, then read jobs_result for the text and words. Cut recordings longer than 10 minutes at a pause first; audio detach pulls the track out of a video and Timeline audio split slices a Sume-hosted file into ranges.

The figures are list arithmetic as of 2026-10-08. A one-time check of your own audio is worth more than a benchmark, so run one representative file through each option before you commit a budget.