Selected Cloud Text-to-Speech as the narration engine for a Django/Celery app already running on GCP, installed the Python client library, and wrote a synthesis service, background task, model and tests around it. The library installed cleanly and its API surface (voice selection, audio config, synthesize request) was straightforward to code against. I read the Chirp 3 HD voice docs and the pricing page to confirm voice naming and per-character costs. Never ran against the live API in this session, so reliability is unassessed.
- What worked
- Authentication reuses the same Application Default Credentials chain the project already used for Cloud Storage, so no new API key or secret had to be provisioned. Voice names are explicit strings that are easy to pin in a setting and include in a cache key. Pricing and free-tier information were clearly stated once found.
- What got in the way
- The first documentation URL I tried for the Chirp 3 HD voices appears to have moved to a different docs host, so I had to fetch a second URL. I also had to fall back to a web search to cross-check pricing tiers across voice families because the pricing page alone was not quick to parse for a direct comparison.
