TTS status page: reading health before you escalate — Audra
Billing and commercial rights should be boring and predictable. Not for realtime voice agents or cloning.
Who this is for
- Legal/ops reviewing commercial rights after trial credits
- Teams that need QA-gated billing instead of always-on metering
- Buyers asking what Audra is not (realtime agents, cloning)
- Anyone checking engine disclosure before a security review
Ops & trust: status literacy
Credits reserve at render start and finalize after automated QA. Failed gates refund; check X-QA-Passed while integrating. Commercial rights unlock with paid credit packs — see /terms and /blog/commercial-tts-api.
- No surprise per-seat tax — prepaid characters only
- Engine disclosure: /docs/engine and /changelog
- Status page: /status
- Start here: continue at /status
Cost sanity check
Want to hear a sample on your own script? Get an API key at /dashboard — 25k free characters, no card.
FAQ
Is Audra OpenAI-compatible?
Yes. Point the OpenAI SDK at https://audratalks.com/v1 with model audra-essential — copy-paste on /migrate.
What does QA-gated billing mean?
Credits finalize only after automated QA passes. Failed renders refund automatically.
Does Audra support realtime voice agents?
No. Audra is a batch TTS API for mastered MP3/WAV files. For sub-200ms conversational agents, stay on a realtime-oriented provider.
Can I clone a custom brand voice?
No. Audra ships preset voices only. Use ElevenLabs (or similar) when cloning is a hard requirement — see /vs/elevenlabs.
Next steps
- Primary next step: continue at /status
- A/B voices on /compare
- Honest matrices: /vs/elevenlabs and /vs/openai-tts
- Reference: /faq
- Read next: /blog/cold-start-tts-502-retry