IoT Voice API: Team, Licensing & Data Policy

By IoT Voice API editorial team · Updated 2026-11-18

This page details the engineering background, licensing structure, and data handling practices behind the IoT Voice API. It is designed for IoT startup engineers and product managers who need transparent information about our infrastructure, voice origins, and privacy commitments before integrating our text-to-speech solution into their smart home or industrial devices.

Here you will find specifics on our LibriTTS-R voice licensing, our strict no-training data policy, and our operational limits, including the absence of an SLA. We also clarify our independence from major tech brands and provide the direct email contact for support. Use this information to verify compliance and understand exactly how your audio generation workflow operates under our API.

IoT Voice API: Team, Licensing & Data Policy

Frequently asked questions

Who runs the IoT Voice API?

IoT Voice API is an independent storefront for a cloud text-to-speech API. We operate as a standalone entity, not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our team manages the infrastructure and billing for startups building smart home and industrial applications.

Are the voices copyrighted?

Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. Each generated audio file carries an inaudible watermark marking it as synthetic speech. You can use the output commercially, but the underlying voice performances originate from these specific licensed and public sources.

Do you use user text for training?

No. 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. We retain request metadata, such as time, characters, and status, strictly for billing purposes and account management.

Where are the audio files stored?

Generated audio is returned in the response and is not stored by our servers. Only request metadata (time, characters, status) is kept for billing. You receive the audio file directly upon successful synthesis, ensuring your generated content remains under your control without long-term storage on our infrastructure.

How do I contact support?

Support is available by email only. We do not offer a phone number, live chat, or on-premise installation options. For issues regarding your API key, billing, or technical questions, please send an email to our support address. We respond to inquiries via this channel.

Is this an official OpenAI product?

No. We are not affiliated with OpenAI. Our API endpoint mimics the OpenAI speech endpoint shape, so official OpenAI SDKs work by changing the base_url. However, we are an independent storefront providing our own text-to-speech engine with different voices, pricing, and infrastructure managed by our team.

What licenses do the voices use?

Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. This foundation allows us to offer eight distinct voice presets. The generated audio includes an inaudible watermark to identify it as synthetic speech, distinguishing it from the original source recordings.

Do you sell user data?

No. Input text is used only to produce the audio and is not used for training or sold to third parties. Generated audio is returned in the response and not stored. We retain only request metadata (time, characters, status) necessary for billing and account management purposes.

Can I request a new voice?

We currently offer eight fixed presets: Aria, Nova, Luna, Sage, Felix, Milo, Atlas, and Orion. We do not offer custom voice cloning, voice design, or uploading your own voice. If you need a different voice, you must choose from the existing eight options available in the /v1/voices endpoint.

How is the API funded?

We operate without monthly plans, seats, or minimum spend. Funding comes from user top-ups via USDT on the TRON network (TRC-20). There are no subscriptions or invoices with VAT. Balance does not expire, and failed requests are refunded, ensuring you only pay for successful synthesis operations.

Do you have a physical office?

We do not have a physical office or on-premise install option. We are a cloud-based API service. Support is handled via email only, with no phone number or live chat. Our infrastructure is designed for lightweight integration into your firmware or backend without complex physical dependencies.

Can I use the API commercially?

Yes. You can use the generated audio commercially. The voices are based on CC BY 4.0 licensed recordings and public-domain sources. Each file includes an inaudible watermark. There are no restrictions on usage, and you pay only for the characters processed, with no minimum spend required.

What is the data retention period?

Input text is used only for synthesis and not stored. Generated audio is returned in the response and not stored. We retain request metadata (time, characters, status) for billing purposes. The retention period for this metadata is not explicitly defined beyond what is necessary for billing accuracy.

Are there any certifications?

No. We do not offer SLA, uptime guarantees, or enterprise contracts. We do not hold certifications such as SOC 2, HIPAA, or GDPR certificates. Our service is designed for startups needing reliable, lightweight audio generation without the overhead of enterprise-grade compliance documentation or physical data centers.

Our Mission

Sound wave illustration for: Our Mission

We provide a lightweight TTS API designed for smart home and industrial IoT devices. Our goal is to enable reliable audio generation directly within your firmware or backend, eliminating complex infrastructure requirements for startups.

The API handles text-to-speech synthesis with minimal overhead, ensuring consistent performance for voice assistants and notifications in constrained environments.

Simplifying IoT Audio

Simplifying IoT Audio

Integration requires only a standard HTTP POST request. We return audio files in formats like MP3, WAV, or Opus, compatible with most embedded systems.

No custom hardware or specialized servers are needed. Your existing backend infrastructure processes the requests and delivers audio to the end device.

  • Standard REST API endpoint
  • Compatible with common IoT audio formats

Engineering Focus

Engineering Focus

We prioritize deterministic behavior and clear error codes. The API processes requests sequentially, ensuring predictable load characteristics for your application.

Rate limits are set at 60 requests per minute per key, allowing for steady audio generation without sudden spikes that could disrupt device communication.

  • Predictable request processing
  • Clear rate limit structure

Startup Friendly

Start with a free trial of $0.50 credit, valid for 7 days. This allows you to test voice quality and integration speed before committing.

Pricing is simple: $10 per million characters. There are no monthly plans, seats, or hidden fees, keeping your operational costs predictable.

  • Free trial credit available
  • No minimum spend or subscriptions

Voice Licensing

Sound wave illustration for: Voice Licensing

Our voices are synthesized from licensed recordings, ensuring clear provenance for commercial IoT applications. We do not clone private individuals or use celebrity likenesses; the eight presets are derived from public-domain audiobook readings and the LibriTTS-R dataset.

This approach provides reliable, consistent audio generation without the legal complexities of individual voice licensing, making it ideal for smart home and industrial deployments where transparency matters.

LibriTTS-R Source

The core voice models are built on the LibriTTS-R dataset. This resource provides high-quality, clean speech data that forms the basis for our eight distinct voice presets.

  • High-fidelity source material
  • Clean speech data
  • Eight distinct voice presets

CC BY 4.0 License

We utilize content under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. This allows us to legally synthesize and distribute audio while adhering to standard attribution requirements for the underlying dataset.

LibriVox Recordings

The voices are based on licensed recordings: LibriTTS-R (CC BY 4.0), from LibriVox public-domain audiobook readings. These recordings are in the public domain, ensuring that the underlying audio sources are free from restrictive copyright claims.

Voice Licensing

Data Privacy

Sound wave illustration for: Data Privacy

We prioritize privacy for IoT deployments where data sensitivity matters. Our API treats input text and generated audio as transient assets rather than training data.

This ensures your smart home or industrial voice commands remain private and are not repurposed for model improvement without explicit consent.

No Training on Input

Input text is used exclusively for synthesis. We do not store or analyze your content to improve our models.

No Audio Storage

Generated audio is returned in the response and not stored.

Metadata Retention

We retain request metadata—including timestamp, character count, and status—for billing and debugging purposes only.

  • Timestamp of request
  • Character count processed
  • Request status (success/failure)

Our Limits

Sound wave illustration for: Our Limits

We build for startups that prioritize core functionality over enterprise bells and whistles. Our engineering focus means we deliver a reliable REST API without the overhead of complex infrastructure, allowing you to integrate TTS directly into your firmware or backend. We are transparent about what we do not offer, so you can plan your architecture with confidence.

Our limits are defined by our single-engine architecture and lightweight operational model. We do not provide enterprise-grade guarantees or dedicated support channels, keeping our service simple and cost-effective for IoT applications.

No SLA Provided

We do not offer a Service Level Agreement (SLA). Our infrastructure is designed for standard operational needs rather than critical industrial redundancy. While we aim for consistent performance, we do not guarantee specific response times or throughput metrics.

Requests are processed in order, and during high load, queues may form. This is inherent to our single-engine design, which keeps costs low for startups who do not require guaranteed latency.

No Uptime Guarantee

We do not guarantee uptime. Our service operates on a best-effort basis. Planned maintenance or unexpected outages may occur without prior notice or compensation.

This approach allows us to maintain a lightweight infrastructure. If strict uptime is critical for your specific IoT device, consider implementing local fallback audio files in your firmware.

Email Support Only

We do not offer a phone number, live chat, or dedicated account managers. All support is handled via email. This keeps our operational overhead low and ensures every query is documented.

For most IoT startups, email support is sufficient for API integration questions, key management, and billing inquiries. We respond to emails during business hours, but there is no guaranteed response time.

Our Limits

Contact Information

Sound wave illustration for: Contact Information

For all technical inquiries, billing questions, or integration support, please contact us via email. Our team monitors the inbox and responds to submitted tickets during standard business hours. This channel serves as our primary and only method for direct communication with customers.

We do not offer a phone number. If you prefer asynchronous communication, email remains the most efficient way to get detailed answers to specific engineering or account-related questions without waiting on hold.

No Phone Number

We do not offer a phone number. This allows us to keep our operational overhead low and pass those savings directly to you through competitive per-character pricing. If you need immediate clarification, email is the fastest route to a documented response.

No Live Chat

We have opted out of live chat widgets to avoid fragmented conversations. Our support workflow is designed around email threads, ensuring that context is preserved and that you receive comprehensive, searchable answers. This approach is particularly effective for debugging API endpoints or discussing bulk generation needs.

Contact Information

Independence

Sound wave illustration for: Independence

IoT Voice API operates as an independent storefront for the same underlying text-to-speech engine, distinct from major tech brands. We do not claim affiliation with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other entity mentioned in comparative contexts. Our identity is defined by our engineering focus on IoT startups, not by brand mimicry.

Not Affiliated with OpenAI

While our API endpoint structure and SDK compatibility mirror the OpenAI speech endpoint, we are not OpenAI. We use the same request shape for convenience, but our infrastructure, billing, and voice models are entirely separate. Comparisons are based on published technical facts, not brand association.

Independent Storefront

We are a single, independent provider. There are no subsidiary relationships or shared operational contracts with larger platforms. Your key, balance, and usage data belong solely to this network’s account system, managed independently without third-party overlay services or shared customer support pools.

No Brand Imitation

We do not imitate the visual identity, voice profiles, or product naming conventions of other companies. Our 8 voice presets (e.g., Aria, Nova, Atlas) are distinct from competitors’ offerings. We present our product on its own merits, using clear engineering descriptions rather than borrowed brand prestige.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Transform your residential devices into an intuitive, connected ecosystem that delights modern homeowners.

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. Creative Commons Attribution 4.0
  3. W3C WAI: making audio and video accessible
  4. MDN: Web Speech API
  5. LibriTTS-R corpus (OpenSLR 141)
  6. openai-python on GitHub
  7. IETF RFC 7845: Ogg Opus
  8. OpenAI API reference: create speech
  9. FFmpeg documentation
  10. LibriVox public-domain audiobooks
  11. Python documentation
  12. ISO 639 language codes

More on this site