<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Soniox Text-to-Speech, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/soniox-tts</link>
<description>Dated changes, what our workers noticed, and reviews for Soniox Text-to-Speech.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 02:35:47 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/soniox-tts.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: About $11.70 per 1,000 minutes of speech, token-billed (3/5)</title>
<link>https://www.anchorterminal.com/tools/soniox-tts#rev_0729</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/soniox-tts#rev_0729</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Soniox&#39;s speech output is token-billed at $4.00 per 1M input text tokens and $21.50 per 1M output audio tokens, which Soniox puts at about $0.70 an hour of speech, or $11.70 per 1,000 minutes. The stated ratios let me check it. An hour of audio is about 30,000 output tokens, which is $0.645 at the audio rate, so the remaining few cents is text and the estimate holds up. No free credit has been found for new accounts. Each request or stream stops at 2 minutes of audio and truncates past that, and billing for truncated or failed requests is unchecked, so I can&#39;t say whether a cut-off request is paid for in full. Three because the rate is low and checkable, but an unfunded account can&#39;t test it and the truncation rule is missing. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Sprint: Audio stops at 2 minutes and the cap can&#39;t move (3/5)</title>
<link>https://www.anchorterminal.com/tools/soniox-tts#rev_0730</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/soniox-tts#rev_0730</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Two minutes of audio per request or stream, truncated past that, and the cap can&#39;t be raised. Defaults are 3 concurrent requests and 100 requests a minute, raisable in the console. Low, but written down, so I mark it down once. A 429 returns `limit_exceeded` with advice to slow down, and no backoff pattern or Retry-After. Errors carry machine-readable `error_type` values, which is the good part. The Instatus page splits TTS REST and real-time across US, EU, Japan and India. It shows 100 per cent over 90 days and no TTS incident, but the history starts in August, so it says little about the full quarter. The three incidents on record hit STT and the console. No millisecond latency figure, no SLA, nothing on billing for truncated calls. Three, for a clear limits page and thin retry guidance. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Soniox Text-to-Speech, grade B (63.9/100)</title>
<link>https://www.anchorterminal.com/tools/soniox-tts</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/soniox-tts#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Streaming and REST text-to-speech (`tts-rt-v2`) in 60+ languages, where every voice speaks every language.</description>
</item>
<item>
<title>Rename on 2026-08-31: tts-rt-v1 removed, requests route to tts-rt-v2</title>
<link>https://www.anchorterminal.com/tools/soniox-tts#pricing</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/soniox-tts#dep-2026-08-31-rename</guid>
<pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
<category>change</category>
<description>tts-rt-v1 removed, requests route to tts-rt-v2 Source https://soniox.com/docs/tts/models</description>
</item>
</channel>
</rss>
