The People Powering the Voxable Voice Platform

By Voxable editorial team · Updated 2026-11-18

Voxable is an independent storefront for a straightforward text-to-speech API, built for indie developers and no-code creators who want natural audio without complex infrastructure. We offer a simple API with clear pricing and a free trial, helping you turn text into speech without writing complex code. This page explains who we are, how we license our voice data from LibriVox, and what happens to your input text, which is used only for generation and not for training.

If you care about transparency—knowing exactly where voices come from, how your characters are billed, and how we handle support—this is the right place. We skip the hype, list our technical limits honestly, and show you how to reach us. No SLAs, no phone numbers, just a clean API and a team that values your time. We support you via email only, ensuring you get exactly what you need without the enterprise fluff.

The People Powering the Voxable Voice Platform

Frequently asked questions

Who runs this site?

Voxable is an independent storefront for this text-to-speech API. We help indie developers and no-code creators turn text into natural-sounding audio without writing complex code. The service provides a simple API, clear pricing, and a free trial to support your project's growth.

Where do the voices come from?

Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. Each generated file carries an inaudible watermark marking it as synthetic speech, ensuring transparency while delivering high-quality audio outputs for your content creation needs.

Is my text used for training?

No. Input text is used only to produce the audio and is not used for training. We respect your data privacy by ensuring your content remains dedicated to your specific generation requests without being repurposed for model improvement or other commercial uses.

Do you store generated audio?

Generated audio is returned in the response and not stored by us. We keep request metadata, such as time, characters, and status, strictly for billing purposes. Your actual audio files are delivered directly to you without lingering storage on our servers.

How do I contact support?

Support is available by email only. We do not offer phone support or live chat. You can reach us through the contact page on our site. We aim to assist indie developers and no-code users with any questions about the API or billing.

Is there a phone number?

No, there is no phone number for Voxable. All support interactions are handled via email. This allows us to maintain clear records of your queries and provide detailed, written responses tailored to your specific technical or billing needs effectively.

Are you affiliated with OpenAI?

We are not affiliated with OpenAI, ElevenLabs, or Google. Our API endpoint shape matches the OpenAI speech endpoint, allowing you to use official OpenAI SDKs by simply changing the base_url. We are an independent provider of this text-to-speech API, distinct from those major brands.

Do you have a physical address?

We do not list a physical address. As a cloud-based API service, we operate fully digitally without a traditional office for customer visits. Our operations are remote, supporting developers globally through our online platform and API endpoints. Support is by email only, so no physical location is required for your interactions with Voxable.

What is the editorial team?

We don’t have a separate editorial team. The content you see here is managed directly by the Voxable team to ensure accuracy and honesty. We focus on providing clear, specific information about our API, pricing, and features without marketing fluff or hype.

Can I suggest a voice?

We currently offer eight fixed presets based on licensed recordings. We do not offer custom voice cloning or uploading your own voice. If you need a specific voice, you can choose from our existing options like Aria, Nova, or Atlas for your projects.

How are prices set?

Pricing is set at $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count as characters. Failed requests are free. We do not use monthly plans or subscriptions, ensuring you only pay for what you actually generate successfully.

Is the site secure?

We secure your API key with Bearer token authentication. Input text is processed solely to generate audio and isn’t used for training, while generated audio isn’t stored. We retain request metadata for billing purposes. We don’t hold specific certifications like SOC 2 or HIPAA.

Do you use cookies?

We use cookies to keep you logged in and remember your account preferences. We don’t track you across other sites or sell your data. Our cookies help you use the API smoothly, so you don’t have to sign in every time. We focus on giving indie developers a simple, secure experience without unnecessary clutter.

Who owns the copyright?

We do not explicitly claim copyright over your generated audio. Your input text is used solely to produce the audio and is not used for training. Since the voices derive from public-domain LibriVox readings, you retain creative rights to your output files. We simply provide the synthesis engine, leaving usage decisions entirely up to you.

Who We Are

Sound wave illustration for: Who We Are

Voxable is a small, independent team focused on building a straightforward text-to-speech API for indie developers and no-code creators. We strip away the complexity of audio generation so you can turn text into natural-sounding speech without writing boilerplate code or managing infrastructure.

We prioritize clear pricing and simple integration over marketing fluff. Our goal is to provide reliable audio synthesis that scales with your project, whether you are building a mobile app, a game, or a standalone web tool.

Editorial Team

Editorial Team

We are developers and engineers who have spent years building tools for non-technical creators. We understand the frustration of juggling multiple APIs and complex configurations.

Our background in indie development drives our design choices: simplicity, transparency, and ease of use. We built Voxable because we needed a reliable TTS solution that didn’t require a dedicated engineering team to operate.

Indie Focus

Indie Focus

We design for indie developers and no-code users first. Our API works seamlessly with simple HTTP requests, making it easy to integrate into any workflow.

We avoid enterprise complexity. There are no minimum spends, no seats, and no monthly plans. You pay only for what you use, with clear pricing that scales as your project grows.

No Hype

We don’t claim to be the “best” or “fastest.” We provide honest, specific facts about our capabilities and limits. Our product is a cloud TTS API that delivers audio files reliably, without overpromising on features like streaming or custom voice cloning.

We focus on what matters: clear documentation, predictable pricing, and a straightforward API that just works.

Voice Licensing

Sound wave illustration for: Voice Licensing

We built the Voxable voice engine using recordings from the LibriTTS-R dataset, which is licensed under CC BY 4.0, and public-domain audiobook readings from LibriVox. These sources provide the raw audio material that forms the basis of our eight voice presets.

LibriTTS-R Source

Our voice models are derived from licensed recordings in the LibriTTS-R dataset. This dataset contains high-quality speech data that we process to create distinct voice profiles like Aria, Nova, and Felix.

CC BY 4.0 License

The LibriTTS-R data operates under the Creative Commons Attribution 4.0 International license. This legal framework defines how we can use, modify, and distribute the source audio recordings within our API infrastructure.

Public Domain Origin

In addition to the dataset, we utilize recordings from LibriVox, which are in the public domain. These older audiobook readings supplement our voice library, ensuring a diverse range of tonal qualities without restrictive copyright claims on the source material.

Voice Licensing

Data Privacy

Sound wave illustration for: Data Privacy

We process your input text solely to generate the audio file you request. The text is not used for model training or to improve the underlying engine, ensuring your creative content remains yours.

No Training Data

Your input text is used exclusively to produce the audio and is not stored for training purposes. This ensures your voiceovers remain private and are not used to refine the synthesis engine over time.

No Audio Storage

Generated audio files are returned directly in the response and are not stored on our servers. Once you download your file, the audio is gone from our systems, keeping your outputs transient and secure.

Metadata Only

We retain request metadata, including timestamp, character count, and status, strictly for billing and usage tracking. This minimal data allows us to manage your account and process charges accurately without storing your actual content.

  • Timestamps
  • Character counts
  • Request status

Technical Limits

Sound wave illustration for: Technical Limits

We design the API for indie developers who need predictable scaling without enterprise overhead. Our technical constraints are transparent from day one, ensuring you can plan your project’s audio generation needs accurately.

4096 Char Limit

Each API request accepts up to 4,096 characters of input text. For longer scripts, simply split the text into chunks and concatenate the resulting audio files. This approach keeps individual requests lightweight and reliable.

60 RPM Limit

Your API key supports 60 requests per minute for standard usage. New accounts without a top-up start with a 10 requests-per-minute limit, which increases to the full 60 RPM once you add funds. This structure helps manage server load during peak times.

No SLA

We do not offer a Service Level Agreement or uptime guarantee. Our infrastructure is optimized for cost-effective scaling rather than enterprise-grade redundancy. You can expect reliable performance, but we do not contractually promise specific availability percentages.

Technical Limits

Support Channels

Sound wave illustration for: Support Channels

We handle all support via email. There is no phone number and no live chat widget. This keeps our team small and focused on building the API for indie developers and no-code creators.

We avoid complex support queues so you get clear, specific answers. You can reach us for editorial questions, feedback, or bug reports using the dedicated addresses listed in our Contact section.

Email Only

All support flows through email addresses. We do not use a single generic inbox; instead, we route messages to the right team member based on your need.

This approach ensures your query is handled by someone who understands the technical context, whether it is a billing question or a voice nuance.

No Phone

We do not offer a phone support line. Phone calls can be disruptive and difficult to track, which doesn't fit the asynchronous nature of most developer workflows.

If you need to discuss something complex, email allows you to attach logs, code snippets, or audio files for a thorough review.

No Live Chat

There is no live chat widget on this site. Real-time chat often leads to fragmented conversations where context is lost.

By using email, you get a persistent record of your support thread that you can reference later when debugging your integration.

Support Channels

Contact Us

Sound wave illustration for: Contact Us

We are a small team of indie developers and no-code creators who built Voxable because we needed a reliable, transparent TTS API. We focus on delivering clear pricing and simple integration without enterprise overhead. Our goal is to help you turn text into audio quickly, so you can focus on building your product.

We value direct communication and prefer email for all interactions. Whether you have a question about the API, want to suggest a feature, or found a bug, we are here to help. We respond to all messages and aim to resolve issues efficiently.

Editorial Email

For any general questions, partnership inquiries, or to learn more about our mission, please reach out to us directly via email. We handle all support personally to ensure your questions are answered accurately.

None

None

Feedback

We are always looking to improve. If you have suggestions for new features, voice improvements, or pricing structures, we want to hear them. Your input directly influences our development roadmap.

None

None

Bugs Reports

Found a bug? Report it with as much detail as possible, including your request ID, the voice used, and the text input. This helps us reproduce and fix issues quickly.

None

None

  • Include your API key prefix (first 4 chars)

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Indie developers use no-code tools to bring their unique creative game visions to life effortlessly.

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. Tether (USDT)
  3. FFmpeg documentation
  4. Node.js documentation
  5. Creative Commons Attribution 4.0
  6. OpenAI API reference: create speech
  7. LibriTTS-R paper (arXiv 2305.18802)
  8. W3C WAI: making audio and video accessible
  9. TRON developer hub: TRC-20
  10. LibriVox public-domain audiobooks
  11. LibriTTS-R corpus (OpenSLR 141)
  12. ISO 639 language codes

More on this site