Meet the Team Behind IoT Voice Labs' npm Text to Speech API

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

Welcome to the About page for IoT Voice Labs. We help smart home enthusiasts and IoT developers add voice to their projects using a simple API that works with Node.js. No coding heavy lifting is required—just send text and get audio files for your devices. This page explains who we are, how we license our voices, and exactly how we handle your data.

You will find details on our LibriTTS-R sources, our privacy policy, and a clear list of what we do and do not offer. Whether you are a no-code maker or a seasoned developer, you will get honest facts about our limits, support, and mission. No hype, just the truth about our Node.js-compatible TTS API.

Meet the Team Behind IoT Voice Labs' npm Text to Speech API

Frequently asked questions

Who runs IoT Voice Labs?

IoT Voice Labs is an independent storefront for the TTS API, accessible at tk971.info. We are not affiliated with OpenAI or other major brands. Our team focuses on helping smart home enthusiasts and IoT developers integrate voice into their projects using a simple, reliable API that works seamlessly with Node.js and other tools.

Where do the voices come from?

Our eight voice presets are based on licensed recordings from the LibriTTS-R dataset (CC BY 4.0). These voices originate from LibriVox public-domain audiobook readings. Each generated audio file contains an inaudible watermark to identify it as synthetic speech, ensuring transparency about the source of the audio you receive.

Is my data safe?

Yes. Your input text is used solely to produce the audio and is not used for training models. We keep request metadata like time, character count, and status for billing purposes. Generated audio is returned in the response and is not stored on our servers after delivery.

Do you sell my data?

No. We do not sell your data. Your input text is used only to generate the audio file and is not used for training. We retain request metadata for billing purposes only. There are no third-party data sales or sharing agreements involving your personal information or usage data.

How can I contact you?

You can contact us via email. We do not offer phone support or live chat. For technical questions or billing issues, please send an email to the address provided on our contact page. We aim to respond to all inquiries promptly via this dedicated support channel.

Do you have phone support?

No, we do not have a phone number for support. All communication is handled via email. This allows us to maintain a focused, asynchronous support model suitable for developers who prefer written documentation and clear, traceable communication threads for their API integration questions and billing inquiries.

Are you affiliated with OpenAI?

No, we are not affiliated with OpenAI. Our API mimics the OpenAI speech endpoint structure for convenience, allowing you to use OpenAI SDKs by changing the base URL. However, we are an independent provider of a different text-to-speech engine with its own pricing, voices, and models.

Do you have a mobile app?

We don’t have a mobile app. Instead, we provide a simple REST API compatible with Node.js and standard HTTP requests. You can easily integrate our TTS service into your smart home projects or IoT devices using basic code, without needing to install any specific mobile application. Just send text and receive audio files for your devices.

Do you offer refunds?

If synthesis fails, the charge is returned in full. For successful requests, we do not offer refunds, but your balance never expires. Any unused credit remains available for future API calls, ensuring you only pay for what you use without losing value over time.

How do I update my API key?

Generate a new key anytime via the /get-api-key/ page. The old key stops working immediately upon creation, ensuring security. Your current key, balance, and usage details are always visible there. Note that accounts are per site, so manage keys specifically for tk971.info. This instant revocation means you don’t need to wait for expiration to switch credentials if needed.

What is CC BY 4.0?

CC BY 4.0 is a Creative Commons Attribution license. Our voices are based on recordings from the LibriTTS-R dataset, which uses this license. This means the source audio is freely available for use with attribution. We ensure our service complies with these licensing terms for all our voice presets.

Do you store audio files?

No, we do not store generated audio files. The audio is returned directly in the API response for you to save. We only keep request metadata, such as time, character count, and status, for billing purposes. Your generated audio is transient and not retained on our servers.

Can I use this commercially?

Yes, you can use our API for commercial purposes. There are no monthly plans, seats, or minimum spend requirements. You pay only for what you use at $0.01 per 1,000 characters. Our simple pricing model makes it easy to scale your commercial IoT or smart home voice projects.

Do you have a blog?

No, we do not have a blog. We focus on delivering a reliable TTS API for your IoT projects. For technical details, consult our /docs/ page. We share service updates and pricing changes directly via the platform dashboard and email support, ensuring you get the specific information you need without navigating extra content.

Who We Are

Sound wave illustration for: Who We Are

We are IoT Voice Labs, a team of developers and smart home enthusiasts building a simple text-to-speech API for IoT projects. Our goal is to help you add voice to your devices without heavy coding. We provide a straightforward API that works with Node.js, making it easy for no-code users to generate audio files from text.

Editorial Team

Editorial Team

Our team consists of developers and smart home enthusiasts who understand the needs of IoT projects. We focus on providing a simple API that works with Node.js, making it easy for no-code users to generate audio files from text.

Our Mission

Our Mission

We aim to help IoT developers and smart home enthusiasts add voice to their projects using a simple API that works with Node.js. No coding heavy lifting is required—just send text and get audio files for your devices.

Community Focus

We are dedicated to the smart home community, providing a simple API that works with Node.js. No coding heavy lifting is required—just send text and get audio files for your devices.

Voice Licensing and Sources

Sound wave illustration for: Voice Licensing and Sources

Our voice presets are based on licensed recordings from the LibriTTS-R dataset. This collection provides the raw audio material that forms the foundation of our eight distinct voice models.

The source material is licensed under CC BY 4.0, ensuring transparency about our audio origins. We use these recordings directly as the source for synthesis rather than training new models from scratch.

LibriTTS-R License

We rely on the LibriTTS-R dataset for our voice engine. This provides a consistent, high-quality baseline for all eight presets, from Aria to Orion.

  • Based on licensed recordings
  • Used as direct synthesis source

CC BY 4.0

The underlying audio data is released under the Creative Commons Attribution 4.0 International license. This allows us to distribute our voice presets while respecting the original creators' rights.

Public Domain Sources

Many recordings in LibriTTS-R come from LibriVox public-domain audiobook readings. This means the source performances are freely available for use in our API.

Voice Licensing and Sources

Data Policy and Privacy

Sound wave illustration for: Data Policy and Privacy

Your input text is used solely to generate the requested audio file and is never used for training our models. Once the audio is returned in the response, it is not stored on our servers.

We keep minimal request metadata—such as timestamps, character counts, and status—for billing purposes only.

Honest Limits and Features

Sound wave illustration for: Honest Limits and Features

We prioritize a straightforward API that fits neatly into your Node.js scripts without unnecessary complexity. Our design focuses on delivering audio files on demand, ensuring you get exactly what you need for your IoT projects without extra overhead.

No Streaming

We do not offer WebSocket or real-time partial audio streaming. You send a POST request and receive the complete audio file. This synchronous approach is reliable for smart home triggers and pre-recorded device responses.

  • No WebSocket support
  • No real-time partial audio
  • Standard REST API response

No SSML

Our API does not support SSML (Speech Synthesis Markup Language) or custom pronunciation lexicons. You pass plain text, and the engine handles the synthesis based on the selected voice and language.

  • No SSML tags
  • Plain text input only
  • No custom pronunciation rules

No Custom Cloning

We do not offer custom voice cloning or allow you to upload your own voice samples. You choose from our eight licensed presets, which are based on LibriTTS-R recordings. These voices are ready to use immediately.

  • No voice cloning
  • No custom voice uploads
  • Fixed set of 8 voices
Honest Limits and Features

Contact and Support

Sound wave illustration for: Contact and Support

All communication for IoT Voice Labs happens via email. We do not offer phone support or live chat, keeping our process simple and asynchronous for developers who prefer written records of their queries.

There is no dedicated support phone number, so you will always reach our team through the email address provided on the contact page. This approach fits our small, focused team structure.

Email Support

Send your questions or issues to our support email. Please include your account email and a description of the problem so we can assist you quickly.

  • Email only
  • No phone number
  • No live chat

No Live Chat

We do not use live chat widgets. This avoids the pressure of instant responses and allows you to send detailed technical questions about your Node.js projects without waiting in a queue.

Response Time

We aim to reply as soon as possible, but specific response times are not guaranteed. Since we are a small team, please allow reasonable time for a thorough answer to your technical question.

Contact and Support

Why We Built This

Sound wave illustration for: Why We Built This

IoT Voice Labs started because we needed a straightforward way to add voice to our projects without heavy coding. We wanted a solution where developers could just send text and get audio files for their devices.

Developer Needs

We build tools for smart home enthusiasts who prefer simplicity. Our API lets you integrate voice quickly, fitting neatly into Node.js workflows without managing extra services.

  • Simple POST requests
  • Node.js compatible
  • No heavy coding

IoT Growth

As smart home projects expand, clear automated voice responses become essential for user interaction and device feedback.

Simplicity First

We prioritize ease of use. You send text, receive an audio file. That is all the code you need to get started.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Your devices work together to create a simple, comfortable home without any complex setup or coding knowledge required by you.

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. IETF RFC 7845: Ogg Opus
  3. Creative Commons Attribution 4.0
  4. OpenAI API reference: create speech
  5. LibriTTS-R paper (arXiv 2305.18802)
  6. Node.js documentation
  7. W3C WAI: making audio and video accessible
  8. ISO 639 language codes
  9. TRON developer hub: TRC-20
  10. openai-python on GitHub
  11. curl documentation
  12. openai-node on GitHub

More on this site