Build2 distinct publishers3 min readPublished
Speaker turns and end-of-speech markers now ride in the same token sequence as the words, which buys a cheaper pipeline and a tighter coupling than a three-vendor speech stack. The accuracy claim behind it is English-only.
The Engineer · Build desk

Compiled by The EngineerSomething wrong?How this is made
The unit of purchase here is a token stream. Audio arrives in 80 ms chunks, 12.5 per second, each compressed into one soft token [11]. At every chunk the model picks one of two actions: emit a text token, or emit a "next audio" placeholder that the runtime swaps for the following chunk [12]. When the audio stops, an "empty audio" token tells the model nothing more is coming, and it flushes whatever text it is still holding [13]. Speaker turns ride that same sequence. A `<|start_of_turn|>` token marks a possible change, a token such as `<|speaker_A|>` assigns the turn, and separate tokens mark start and end of speech, all trained alongside transcription rather than handed to a downstream speaker classifier [16].
That gives you something to budget with. 12.5 chunks a second across an hour is 45,000 soft tokens [1], and $0.18 for that hour works out at $4 per million audio tokens [2]. Streaming and batch carry the same rate, and diarization is not a separate line [2].
The reward design is the part worth copying. Meta multiplies the word-error-rate reward by the delay reward instead of adding them [15]. Addition lets a model buy accuracy with unlimited stalling, because a strong WER term covers a weak delay term. Multiplication makes a near-zero score on either factor collapse the whole product. That is what produces adaptive delay, where the model spends more audio on an ambiguous word and commits early on an easy one [14]. What the launch material does not give you is a millisecond figure; the only published timing value is the 80 ms chunk period [7]. Barge-in budgets are a distribution here, not a constant, and you will have to measure it yourself.
For the accuracy number to describe your workload, your audio has to be English, streamed, and close enough to whatever mix Artificial Analysis assembled, because that benchmark covers English only [17]. Meta says 25 of more than 70 trained languages were extensively validated for this release [5], so anything outside those 25 is your eval problem. The margin over the next model on the list is 0.3 points [6], in a field where OpenAI, Google, xAI and Alibaba all shipped streaming models within weeks of each other, according to The New Stack [21].
The bundled feature is also the weak one. Speaker error at 17.5% is roughly 5.6 times the word error rate [5]. If your interface prints a name next to a quote, 17.5% is what the user meets.
On price, the bundle undercuts the $0.24 Speechmatics lists for Standard real-time transcription by 25% [9][3], while Soniox posts about $0.12 an hour with diarization, language identification and formatting included, a third under Meta [8][4]. The posted floor belongs to Soniox. What moved is the default assembly: one vendor billing one rate for work that used to need three integrations. Speechmatics will label 50 speakers by default and 100 on request, five times Meta's stated 20-plus [9][8], and if a hundred people are talking at once, speaker labels are not your first problem. Amazon Transcribe documents 30 [10]. Meta is not releasing these weights, a spokesperson told The New Stack [19], so a consolidated pipeline is a hosted dependency with no local build behind it.
Ranked by verification strength, evidence, and original report placement.
Meta's technical launch post says Muse was trained across more than 70 languages, with 25 extensively validated for the first release.
Meta says Muse supports audio longer than an hour, multilingual code-switching, and more than 20 speakers without a separate diarization pipeline.
Meta launched Muse Voice Transcribe on September 1, pricing a real-time speech model with transcription, endpoint detection and speaker diarization at $0.18 per processed audio hour.
Meta lists Muse Voice Transcribe at $3 per 1,000 minutes through the Meta Model API; streaming and non-streaming processing carry the same rate, and speaker diarization is included rather than billed as an add-on.
At the public rate, 1,000 hours of processed audio would cost $180.
Meta built Muse Voice Transcribe inside Meta Superintelligence Labs, the AI organization formed after Meta invested $14.3 billion in Scale AI and recruited its founder, Alexandr Wang.
Distinct publishers with included, body-backed reporting in this cluster.
runtimewire.com
1 article · September 2, 2026
thenewstack.io
2 articles · September 1, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
leadership
Meta prices streaming transcription at a fifth of Google Cloud's standard rate1 distinct publisher
product
Meta's 2026 Capex Plan More Than Doubles Two Years of Spending; the Product It Funds Is Still on Paper1 distinct publisher
invest
Meta hires another ChatGPT alumnus, and the whole industry pays the retention bill1 distinct publisher
invest
Meta's record child-safety settlement buys off a $200bn trial for about 6 cents on the dollar1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One launch post, one leaderboard, one story filed twice
The price sheet is solid — two publishers state $3 per 1,000 minutes and Runtime Wire worked from developer material — and the architecture is described consistently enough that the token-level account holds up. Everything about capability, though, is Meta describing Meta: 70 languages, hour-plus audio, 20-plus speakers. The only outside measurement in the whole story is Artificial Analysis's English streaming list, and the publisher that flags the absence of independent testing is not the publisher that cites it.
Shipped, priced, and not yet visibly used
What exists is real: a launched model, a posted rate, three delivery surfaces and a benchmark standing, all inside two days. What is missing is anyone on the other side of the API. No customer, no deployed product, no usage figure appears — and the closest thing to a stress test, Meta's own demo, tops out at eight speakers with 11 labeled in the long recording. Meta's glasses and Mac app are named as intended consumers, not as shipped integrations.
"Beat OpenAI and Google" is an English-only claim
The headline crown rests on a 0.3-point margin, on one leaderboard, in one language, from a model whose speaker attribution fails 17.5% of the time — and The New Stack itself concedes in its closing paragraphs that the lead will not survive a field where four large labs shipped in the same weeks. Two things push the other way and keep this from being pure froth: the price and the flat streaming rate are checkable numbers, and folding turn and endpoint tokens into the transcript stream is a genuine architectural change rather than a repackaging.
The seller wrote most of the spec sheet
Meta sets the price, publishes the capability numbers, chooses the demo, and keeps the weights closed so nobody can check the model itself — and it has a hardware roadmap that needs this to look good. Runtime Wire makes the strategic motive explicit by tying the launch to the $14.3 billion Scale AI deal and Zuckerberg's cheap-distribution essay. On the reporting side, one publisher led with a competitive-victory headline it then walks back, and the other is a downstream write-through of VentureBeat, meaning the caveats and the comparisons both arrive secondhand.
Firm on price and mechanism, soft on field behaviour
We would defend the rate, the bundling, the token-level design and the leaderboard position without hesitation — those are stated consistently and, in the pricing case, sourced to documentation. We would not yet defend any statement about how Muse behaves in a real room with cross-talk and accents, because nothing in this reporting measures that, and the two accounts do not corroborate each other so much as divide the story between them.