The Independent Team Behind This Text-to-Speech API

By CivicVoice editorial team · Updated 2026-11-18

This page explains who we are and how we operate as an independent provider of the CivicVoice text-to-speech API. We built this service specifically for government agencies, NGOs, and indie developers who need reliable, multilingual audio generation without complex infrastructure. You will find clear details on our licensing, data policies, and pricing model, ensuring you understand exactly what powers your integrations.

We prioritize transparency over marketing hype. Here, you can read about our editorial integrity, the public domain sources of our voices, and our straightforward data practices. Whether you are integrating our API into civic apps or managing community outreach, this page offers the factual context needed to trust our service with your text-to-audio workflows.

The Independent Team Behind This Text-to-Speech API

Frequently asked questions

Who runs the site?

CivicVoice is an independent storefront for this text-to-speech API. We provide direct access to the cloud service without being affiliated with OpenAI, ElevenLabs, Google, Amazon, or Microsoft. Our platform is designed for government agencies and NGOs, offering a reliable API for converting text to audio. Each site in our network operates as an independent storefront for the same underlying API.

What is the mission?

We provide a reliable text-to-speech API designed for government agencies and NGOs to make digital content accessible. Our solution helps teams convert plain text into clear audio for multilingual communities without complex infrastructure. We focus on delivering clear, synthetic speech for public information without requiring specialized technical knowledge or expensive enterprise contracts.

How are voices licensed?

Our voices are based on licensed recordings from LibriTTS-R (CC BY 4.0), derived from LibriVox public-domain audiobook readings. Every generated file carries an inaudible watermark that marks it as synthetic speech. This ensures transparency about the audio origin while providing a consistent voice experience for your digital content needs.

Is data used for training?

Input text is used only to produce the audio and is not used for training. Generated audio is returned in the response and not stored. Request metadata (time, characters, status) is kept solely for billing purposes. This ensures your content remains private and is not repurposed for model improvement.

How can I contact support?

Support is provided via email only. We do not offer a phone number or live chat for customer inquiries. You can reach us through the contact page on this site. For technical issues, you may also refer to the documentation or check your usage and billing status in your account dashboard.

Is there a phone number?

No, there is no phone number for CivicVoice. All support interactions are conducted via email. We do not offer live chat either. This approach allows us to maintain a focused, asynchronous support structure suitable for developers and agency teams who prefer written records of their technical inquiries and resolutions.

Is there live chat?

No, there is no live chat available on this site. Support is handled exclusively through email. This ensures that your questions are documented and can be addressed thoroughly without the pressure of real-time interaction. You can find the contact details on our /contact/ page to get assistance with your API usage.

What is the data policy?

Input text is used only to produce the audio and is not used for training. Generated audio is returned in the response and not stored. Request metadata (time, characters, status) is kept for billing. We do not store your audio files long-term, ensuring that your public information remains secure and private.

Our Mission

Sound wave illustration for: Our Mission

CivicVoice delivers a reliable text-to-speech API engineered for government agencies and NGOs to make digital content accessible. By converting plain text into clear audio, we help teams serve multilingual communities without requiring complex infrastructure or dedicated voice talent.

We prioritize editorial integrity and specific utility over marketing hype. Our approach is grounded in the actual capabilities of our API, ensuring that developers and public servants understand exactly what the system provides and its technical boundaries.

Accessibility First

Accessibility First

Our API supports 23 languages, including Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice preset can speak any of these languages, allowing agencies to generate consistent audio for diverse populations without managing multiple voice models.

Transparent Pricing

Transparent Pricing

Pricing is straightforward: $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count as characters. Failed requests are free, ensuring you only pay for successful synthesis. There are no monthly plans, no seats, and no minimum spend. Balances do not expire.

  • No hidden fees or subscriptions
  • Payment via USDT (TRC-20) on TRON
  • Minimum top-up: $5

Editorial Integrity

We avoid superlatives like "best" or "fastest" unless backed by published facts. We do not claim to ensure inclusivity regarding reading ability, as we provide the audio conversion tool, not the accessibility outcome. Comparisons to other brands are factual and dated. We do not use hype to obscure the simple reality of what the API does.

Voice Licensing

Sound wave illustration for: Voice Licensing

CivicVoice uses eight voice presets—such as the warm narrator Aria or the deep documentary voice Orion—based on licensed recordings from LibriTTS-R. These voices are not tied to exclusive corporate contracts, providing a stable foundation for long-term digital accessibility projects. Our integration of this license allows us to offer a transparent, open-source-compatible voice engine for public sector and non-profit use.

LibriTTS-R License

We rely on LibriTTS-R, a high-quality dataset derived from LibriVox public-domain audiobook readings. This dataset provides the acoustic foundation for our eight voice presets, ensuring consistent quality across our English and multilingual models.

  • Based on LibriVox public-domain audiobook readings.

Public Domain Sources

The underlying audio comes from LibriVox, a volunteer-driven project creating free audio books. This ensures the voices are not tied to exclusive corporate contracts, providing a stable foundation for long-term digital accessibility projects.

CC BY 4.0

LibriTTS-R is released under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. This source ensures that the voices are not tied to exclusive corporate contracts, providing a stable foundation for long-term digital accessibility projects. Our integration of this license allows us to offer a transparent, open-source-compatible voice engine for public sector and non-profit use.

Voice Licensing

Data Policy

Sound wave illustration for: Data Policy

We operate with a strict data boundary. Input text is used only to produce the audio and is not used for training. This ensures your content remains yours, whether you are localizing a government notice or creating an NGO newsletter.

Once the audio file is delivered in the response, it is not stored. This ensures your generated speech remains private and transient. We prioritize simplicity and clarity for teams managing sensitive community communications.

No Training Data

Input text is used exclusively for the single synthesis request. We do not use your content to improve or train our underlying TTS engines.

No Storage of Audio

Once the audio file is delivered in the response, it is not stored. This ensures your generated speech remains private and transient.

Billing Metadata

Request metadata (time, characters, status) is kept for billing. We retain only what is necessary to verify your usage and process your USDT top-ups accurately.

Team Structure

Sound wave illustration for: Team Structure

CivicVoice operates as an independent storefront for the same text-to-speech API, maintaining editorial integrity and transparent pricing. Our structure is designed to keep operations simple and direct, ensuring that the product remains focused on reliable multilingual audio generation for government agencies and NGOs without the overhead of complex corporate divisions.

Editorial Team

The editorial team ensures that all product information, pricing details, and feature descriptions remain accurate and honest. We verify that claims about voice licenses, supported languages, and API behavior align strictly with the published facts, avoiding hype and superlatives in favor of clear, specific details for our audience of indie developers and civic tech teams.

Developers

Our developers maintain the API infrastructure, ensuring endpoints like /v1/audio/speech process requests correctly. They handle the integration of the eight voice presets based on LibriTTS-R recordings and manage the character counting system that drives our $0.01 per 1,000 characters pricing model. The focus is on stable, straightforward delivery of audio files in formats like MP3, WAV, and FLAC.

Support Staff

Support is handled exclusively via email, with no phone number or live chat available. Our staff assists with API key management, billing inquiries, and technical questions regarding the 60 requests per minute rate limit. We aim to provide clear, direct answers without the delay of automated chat bots or complex phone trees, keeping communication efficient for our users.

Team Structure

Contact Information

Sound wave illustration for: Contact Information

Our support operates exclusively through email. This channel allows us to maintain a clear, written record of each request, ensuring that technical details and account specifics are preserved for accurate resolution. When you reach out, please include your API key and a description of the issue, such as a failed request or billing discrepancy.

Email Support

You can contact the CivicVoice team directly via email for any questions regarding the API, your account balance, or top-up statuses. We do not guarantee immediate responses, as our small team handles all inquiries asynchronously. Including your API key in the message helps us locate your account quickly and provide specific assistance without unnecessary back-and-forth.

No Phone Number

We do not maintain a phone line. This decision keeps our overhead low, allowing us to pass those savings on to you through our transparent, per-character pricing. Without the complexity of voice queues and hold times, you can communicate your technical needs clearly in writing, which is often more efficient for debugging API integrations.

No Live Chat

There is no live chat widget on this site. Real-time chat can become fragmented and difficult to reference later. By sticking to email, we ensure that every support interaction is documented and searchable. This approach suits developers and NGO staff who prefer asynchronous communication that fits into their workflow without interrupting their current tasks.

Contact Information

Honest Limits

Sound wave illustration for: Honest Limits

CivicVoice operates as an independent, lean API provider rather than a large enterprise. This structure keeps costs predictable but means we do not offer Service Level Agreements (SLAs) or custom contracts tailored to specific government or NGO needs. Requests are processed sequentially, so during high demand, synthesis may experience queue delays without penalty or guaranteed response times.

We do not provide uptime guarantees, nor do we hold third-party certifications such as SOC 2, HIPAA, or GDPR. We do not offer on-premise installations or data-center selection options. Our support is handled exclusively via email, with no phone line or live chat available for immediate assistance.

No SLA

We do not offer Service Level Agreements or enterprise contracts. Requests are processed one after another, meaning under load a request may wait in a queue. There is no priority processing lane available for purchase.

No Uptime Guarantee

We do not guarantee a specific percentage of uptime. While we strive for reliability, no formal SLA backs this claim.

No Certifications

We do not hold certifications like SOC 2, HIPAA, or GDPR. Our data policy ensures input is not used for training, but we do not offer audited compliance certificates.

Support is by email only. There is no phone number or live chat.

No on-premise install or data-center choice.

  • Email support only
  • No phone or live chat
  • No SOC 2, HIPAA, or GDPR certificates
  • No on-premise option
  • No data-center choice
  • No enterprise contracts

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Simplify grant applications to empower indie developers navigating complex government and NGO funding landscapes effectively.

Avatar of the voice aria
ariafemale
Avatar of the voice nova
novafemale
Avatar of the voice luna
lunafemale
Avatar of the voice sage
sagefemale
Avatar of the voice felix
felixmale
Avatar of the voice milo
milomale
Avatar of the voice atlas
atlasmale
Avatar of the voice orion
orionmale

23 languages

Any voice speaks any of these languages.

Sources and further reading

  1. Wikipedia
  2. openai-node on GitHub
  3. IETF RFC 7845: Ogg Opus
  4. Creative Commons Attribution 4.0
  5. curl documentation
  6. W3C WAI: making audio and video accessible
  7. MDN: Web Speech API
  8. ISO 639 language codes
  9. LibriTTS-R paper (arXiv 2305.18802)
  10. openai-python on GitHub
  11. Python documentation
  12. OpenAI API reference: create speech

More on this site