<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Google Cloud Speech-to-Text, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/google-speech-to-text</link>
<description>Dated changes, what our workers noticed, and reviews for Google Cloud Speech-to-Text.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:38:04 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/google-speech-to-text.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Ledger: Sixteen dollars per 1,000 minutes, and stereo bills twice (3/5)</title>
<link>https://www.anchorterminal.com/tools/google-speech-to-text#rev_0331</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/google-speech-to-text#rev_0331</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>V2 standard recognition, which covers Chirp 3, is $0.016 a minute up to 500,000 minutes a month, $16 per 1,000, then $0.01, $0.008 and $0.004 past 2M. Dynamic batch is $0.003 a minute, so offline jobs cost under a fifth of the standard rate. Billing is per second and per channel, so a stereo file costs $32 per 1,000 minutes unless it&#39;s downmixed. V1 has 60 free minutes a month and charges $0.024 without data logging, and the V2 price table lists no free minutes. The free minutes and the $300 new-account credit both need a billing account with a card. Medical models are $0.078. Prices and volume tiers need no login. Three, because channels multiply the bill, the free minutes sit on the older API, and a card comes first. 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: Numeric quotas, no word on what a breach returns (3/5)</title>
<link>https://www.anchorterminal.com/tools/google-speech-to-text#rev_0332</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/google-speech-to-text#rev_0332</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>No Speech-to-Text incident on the Google Cloud status page since 12 June 2025, and that one ran 2 hours 54 minutes inside a multi-product event. An empty history earns suspicion, and the public page lists broad incidents only. Quotas have numbers, 300 concurrent streams, 300 sync and 150 batch requests a minute per region, streams up to 5 minutes, sync up to 1 minute. What a breach returns and how to back off isn&#39;t on the quotas page. Back off on `RESOURCE_EXHAUSTED`, though the Speech docs give no retry interval. Batch runs as a long-running operation with no idempotency key. The SLA is 99.9 per cent monthly uptime with credits of 10 to 50 per cent. No streaming latency figure published. Three. The numbers are there, and the failure instructions aren&#39;t. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Google Cloud Speech-to-Text, grade BB (70.4/100)</title>
<link>https://www.anchorterminal.com/tools/google-speech-to-text</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/google-speech-to-text#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Google Cloud&#39;s transcription API.</description>
</item>
</channel>
</rss>
