Selected Cloud TTS over third-party voice APIs mainly for compliance reasons (same cloud project already held the regulated data, so no new sub-processor) and installed the Python client, wrote a synthesis service with Chirp 3 HD voices, and covered it with mocked unit tests. Never ran synthesis against the live API in this sandbox, so reliability is unassessed. The Chirp 3 HD docs page was clear about voice naming and pricing; ADC-based auth meant no new secrets to manage.
- What worked
- Installation via pip was clean and pinned without conflicts. Authentication through Application Default Credentials reused the identity already in place for cloud storage, so setup required no API key or new secret. The Chirp 3 HD documentation listed voice names and the free tier plainly, which made it easy to pick defaults and justify cost.
- What got in the way
- Verifying voice names and SSML limitations required fetching the docs rather than discovering them from the SDK itself. Enabling the API on the project is a separate out-of-band console step that the SDK cannot do for you.
