About VocalPipe: The Independent Team Behind the TTS API

By VocalPipe editorial team · Updated 2026-11-18

This page explains who runs VocalPipe and how we operate. We are an independent storefront for a straightforward text-to-speech API designed for mobile app developers. We handle the synthesis infrastructure so your product team can focus on UX and core features without heavy overhead.

You will find details on our voice licensing, data policy, and honest limitations. We also explain our network structure and how to reach our support team. This is all you need to know about the people behind the API.

About VocalPipe: The Independent Team Behind the TTS API

Frequently asked questions

Who runs VocalPipe?

VocalPipe is an independent storefront for a single text-to-speech API. Each site in our network operates independently, meaning your account and usage are specific to playl44.com. We are not affiliated with OpenAI, ElevenLabs, or any other major tech brand, providing a straightforward API for mobile developers without corporate overhead.

Where do the voices come from?

Our eight voice presets are based on licensed recordings from LibriTTS-R, which uses public-domain audiobook readings from LibriVox. These recordings form the basis of our voice presets. The voices include female presets like Aria and Nova, and male presets like Felix and Milo, all derived from these established sources.

Are the voices copyrighted?

The underlying recordings are from LibriVox public-domain audiobook readings, licensed under CC BY 4.0. While the source material is public domain, every generated audio file carries an inaudible watermark that marks it as synthetic speech. This helps identify the content as AI-generated without imposing strict copyright restrictions on the output.

Do you store my text?

No. Your input text is used only to produce the audio and is not used for training our models. Once the synthesis is complete, the text is not retained for long-term storage. We keep request metadata, such as time and character count, strictly for billing and usage tracking purposes.

Do you store the audio?

No. Generated audio is returned in the response and is not stored on our servers after delivery. We retain request metadata, including timestamp, character count, and status, solely for billing accuracy. Your actual audio files are transient, ensuring your content remains yours without us holding onto the generated media.

How do I contact support?

Support is available by email only. We do not offer live chat or phone support, keeping our structure lightweight for mobile teams. You can reach us via the contact form on our /contact/ page. We aim to respond promptly to all inquiries.

Is there a phone number?

No, we do not have a phone number. Our support model is entirely email-based to maintain efficiency and low overhead. This allows us to focus on delivering a reliable API for mobile app developers. You can submit your questions or issues through our contact page, and our team will assist you there.

Do you have an office?

We do not list a specific physical office address. As an independent API provider, our operations are distributed, allowing us to serve mobile teams globally without geographic constraints. Our infrastructure is cloud-based, ensuring that your API requests are processed reliably regardless of your team's location or time zone.

Are you affiliated with OpenAI?

No, we are not affiliated with OpenAI. Our API endpoint mimics the OpenAI speech endpoint structure, so you can use the official OpenAI SDK by simply changing the base_url to https://api.playl44.com/v1. We are an independent provider offering tts-1 and tts-1-hd models with our own pricing and voice presets.

Can I sue you if audio fails?

We do not offer an SLA or uptime guarantee, so there is no contractual basis for lawsuits based on availability. However, if synthesis fails, the charge is returned in full. We prioritize reliability, but our independent status means we do not provide enterprise contracts or guaranteed compensation for downtime beyond refunds.

Do you offer refunds?

Yes, failed requests are free, and the charge is returned in full if synthesis fails. Your balance does not expire, and you can top up via USDT on TRON. There are no monthly plans or subscriptions, so you only pay for successful generations. Unused credit remains in your account indefinitely.

How is data processed?

Input text is sent to our API to generate audio and is not used for training. Metadata like time and character count is kept for billing. Audio is returned in the response and not stored. We process requests sequentially, so under load, a request may wait in a queue before synthesis begins.

Is the site secure?

We use standard HTTPS encryption for all API requests and site interactions. Your API key is the sole authentication method, and you can issue a new key at any time, invalidating the old one instantly. We do not store your text or audio, minimizing data exposure.

Who owns the generated audio?

You own the generated audio files created through our API. We do not claim ownership over your content. The only addition is an inaudible watermark marking the file as synthetic speech. Since we do not store the audio, you retain full control over how you use and distribute your generated voice content.

Who we are

Sound wave illustration for: Who we are

We are an independent storefront for a text-to-speech API. Unlike large enterprises, we prioritize clarity and reliability over marketing noise. Our goal is to provide a straightforward text-to-speech API that mobile app teams can integrate quickly without wrestling with heavy infrastructure.

This API is designed for developers who need reliable voice generation. We handle the synthesis server-side so your team can focus on UX and core features. By keeping the technology simple, we ensure your app remains lightweight and responsive, regardless of network conditions.

Independent editorial team

Independent editorial team

We operate as a lean, independent group rather than a large corporation. This structure allows us to make direct decisions about product features and pricing without layers of management. We are committed to transparency, providing honest details about capabilities and limitations rather than hiding behind corporate jargon.

Built for mobile developers

Built for mobile developers

Our API is optimized for the constraints of mobile environments. We understand that mobile apps have strict limits on data usage and processing power. By offloading synthesis to our cloud API, your app stays lightweight. Developers can generate high-quality audio files on demand, keeping the app bundle small and fast.

No corporate overhead

No corporate overhead

We do not have the bloated costs of large tech companies. This means lower overheads and a simpler pricing model. You pay only for what you use, with no hidden fees or complex tier structures. Our independence allows us to remain agile and responsive to the specific needs of app developers.

Voice licensing

Sound wave illustration for: Voice licensing

Our voice presets are built on licensed recordings from the LibriTTS-R dataset. These voices are based on licensed recordings from LibriTTS-R, which uses public-domain audiobook readings from LibriVox.

LibriTTS-R source

LibriTTS-R source

The underlying audio data comes from the LibriTTS-R dataset, which provides high-quality speech samples. We use these recordings as the base for our eight voice presets, ensuring consistent quality across all languages and styles.

CC BY 4.0 license

The source material is licensed under CC BY 4.0. This allows us to use the recordings as the basis for our voice presets.

LibriVox public domain

Many of the source readings originate from LibriVox, where volunteers read public-domain books. This means the underlying content is free of copyright restrictions, simplifying your rights management when deploying voice features to your users.

Data policy

Sound wave illustration for: Data policy

We prioritize your data’s privacy with a straightforward policy. Input text is used exclusively to generate the requested audio file and is never retained or repurposed for training our models. Once the synthesis is complete, the audio is returned directly in the API response and is not stored on our servers.

We only keep request metadata—such as timestamp, character count, and status—strictly for billing accuracy and usage tracking. This minimal data helps us manage your account without accessing the actual content you synthesize, ensuring your core product logic remains private and secure for your mobile app.

Text not used for training

Your input text is used solely to produce the audio file and is not used for training.

We do not retain the content to improve our voice models or for other commercial purposes.

Audio returned immediately

Generated audio is returned in the API response and is not stored on our servers.

The audio file exists only during the transfer to your client and is not kept long-term.

Metadata kept for billing

We keep request metadata (time, characters, status) strictly for billing and usage tracking.

This ensures accurate charges without storing the actual text or audio content you generate.

Honest limitations

Sound wave illustration for: Honest limitations

We built VocalPipe for mobile teams that value simplicity over complex feature sets. By focusing on reliable, on-demand synthesis, we keep the API straightforward. This means you get exactly what you need without the overhead of managing advanced infrastructure or waiting for partial audio chunks during generation.

No streaming support

We do not offer WebSocket or chunked streaming, so you must wait for the full audio file to be generated before playing it. This approach ensures consistent audio quality and simplifies integration for mobile apps that prefer standard request-response patterns over complex real-time connections.

No custom voice cloning

We provide eight high-quality presets based on licensed recordings, but we do not offer custom voice cloning for customers. You cannot upload your own voice or design a new voice profile. This keeps our infrastructure lean and ensures every generated file remains consistent with our established library.

No SLA guarantees

As an independent storefront, we do not provide formal Service Level Agreements or uptime guarantees. While we strive for reliability, our infrastructure is optimized for cost-effective scalability rather than enterprise-grade contracts. You can rely on consistent performance, but we do not promise specific availability metrics or on-premise installs.

Honest limitations

Contact and support

Sound wave illustration for: Contact and support

We keep support simple and direct. Since we are a small independent team, we do not maintain phone lines or live chat windows. This allows us to focus our energy on keeping the API stable and the documentation accurate for your mobile apps.

Email only support

All inquiries go through email. We avoid phone support to keep overhead low and ensure every request is documented clearly for future reference.

No live chat

You will not find a chat widget on the site. We believe asynchronous communication is more efficient for technical issues, allowing you to share logs and context without waiting on hold.

Response via ticket

Your email creates a support ticket that tracks the status of your issue. You will receive updates and resolutions directly in your inbox, ensuring no detail is lost.

Network structure

Sound wave illustration for: Network structure

VocalPipe operates as an independent storefront, designed specifically for mobile app developers who need reliable voice generation without heavy infrastructure. We handle the synthesis so your team can focus on UX and core features.

Independent storefront

Each site in the network is an independent storefront for the same text-to-speech API. We maintain distinct brand identities to serve different market segments while ensuring consistent technical performance.

Same API as other sites

Every site in our network uses the exact same API endpoints, voice models, and pricing logic. You get the same 8 voices, 23 languages, and $10/1M character rate regardless of which site you join.

Distinct brand identity

While the backend is shared, each storefront offers a unique entry point. This structure keeps overhead low and allows us to tailor the onboarding experience for mobile teams without compromising the core API stability.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Our mobile apps must deliver seamless user experiences that keep product teams engaged and satisfied daily.

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. Python documentation
  4. LibriTTS-R paper (arXiv 2305.18802)
  5. LibriTTS-R corpus (OpenSLR 141)
  6. MDN: Web Speech API
  7. Creative Commons Attribution 4.0
  8. OpenAI API reference: create speech
  9. ISO 639 language codes
  10. LibriVox public-domain audiobooks
  11. curl documentation
  12. W3C WAI: making audio and video accessible

More on this site