About AudioPilot: The Independent TTS API Team

By AudioPilot editorial team · Updated 2026-11-19

This page explains who runs AudioPilot and how we license the voices you hear in your audiobooks. We are an independent editorial team, not affiliated with OpenAI or other major brands. Our focus is on providing freelance narrators and self-publishing authors with a reliable, character-based TTS API that fits their storytelling workflow.

Here you will find details on our voice licensing from LibriTTS-R, our data policy, and our support structure. We keep things transparent: no hidden fees, no enterprise contracts, and no certifications like SOC 2. Read on to understand exactly how we generate audio and who we are.

About AudioPilot: The Independent TTS API Team

Frequently asked questions

Are you affiliated with OpenAI?

No. AudioPilot is an independent storefront for a distinct text-to-speech API. While our endpoint structure mimics the OpenAI speech endpoint for SDK compatibility, we are not affiliated with, endorsed by, or connected to OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons.

Who owns the voice recordings?

Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. We provide these voices for your synthetic speech generation without requiring custom voice cloning or additional licensing fees beyond the API usage charges.

Can I sue if the voice sounds bad?

We do not offer an SLA or uptime guarantee, nor do we provide enterprise contracts or certifications like SOC 2. You can contact us via email if you experience issues, but we do not guarantee specific audio quality outcomes.

Do you store my text data?

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 keep request metadata, such as time, characters, and status, strictly for billing purposes to ensure accurate character-based invoicing.

How can I contact you?

Support is available by email only. We do not offer a phone number, live chat, or physical office locations. You can reach our support team via the contact page on 60w.info.

Do you offer refunds?

Yes. Failed requests are free, and the charge is returned in full if synthesis fails. For other cases, we do not offer automatic refunds but you can contact us via email. Your balance does not expire, and you can manage your account details on the dashboard.

Is the API open source?

No. We do not offer an official SDK of our own, nor is the API code open source. You can use the official OpenAI SDK by changing the base_url to https://api.60w.info/v1, or use plain HTTP requests. We do not provide mobile SDKs or browser extensions.

Do you have a physical office?

No. AudioPilot operates as a cloud-based API service. We do not have a physical office, on-premise install option, or data-center choice for customers. All operations, including billing and support, are managed remotely. You can find our contact email on the /contact/ page.

Who We Are

Sound wave illustration for: Who We Are

We are an independent editorial team building AudioPilot for freelance narrators and self-publishing authors. We designed this cloud TTS API to be a practical tool for producing professional-grade audiobooks quickly, with transparent character-based pricing and voices that fit the storytelling workflow.

Independent editorial team

Independent editorial team

Our team operates separately from larger tech companies. We focus on delivering a reliable cloud API that simplifies the production process for independent creators.

No affiliation with major brands

No affiliation with major brands

AudioPilot is not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. We are an independent storefront for the same underlying TTS API.

Focus on freelancers and authors

Focus on freelancers and authors

We target freelancers and self-publishing authors who need clear licensing and straightforward pricing. Our workflow supports splitting long texts and joining audio files, making it suitable for audiobook production without enterprise complexity.

Voice Licensing

Sound wave illustration for: Voice Licensing

AudioPilot’s voice engine relies on high-quality, licensed source material to ensure consistent and professional narration for audiobooks. We use the LibriTTS-R dataset as our primary foundation, which provides a robust and diverse set of vocal characteristics suitable for long-form storytelling.

LibriTTS-R source data

LibriTTS-R source data

The LibriTTS-R dataset serves as the core training data for our voice models. It contains hours of spoken text from a wide variety of speakers, allowing us to generate clear, natural-sounding speech that meets the needs of self-publishing authors and freelance narrators.

  • High-quality audio recordings
  • Diverse speaker profiles
  • Optimized for TTS training

CC BY 4.0 license

All source audio is licensed under Creative Commons Attribution 4.0 (CC BY 4.0). This transparent licensing model reduces legal overhead for your projects.

Public domain recordings

Many of the recordings in our dataset come from LibriVox, featuring public domain audiobook readings. This ensures that the underlying voice samples are free from restrictive copyright claims, giving you confidence in the commercial viability of your produced content.

Data Policy

Sound wave illustration for: Data Policy

When you send text to our API, we process it solely to generate the requested audio file. The input is not stored permanently after synthesis, ensuring your manuscript content remains private during the creation process. This direct pipeline keeps data usage minimal and focused entirely on delivering the sound file you need for your audiobook or narration project.

Text used only for generation

We use your input text exclusively to produce the audio output. Once the synthesis is complete, the text itself is not retained for long-term storage or secondary purposes. This ensures that your unpublished manuscripts or script drafts remain confidential and are not repurposed outside the immediate generation context.

No training on user data

Your submitted text is never used to train our models or improve the underlying voice engines. The data flow is strictly transactional: input text in, audio file out. This means your unique narrative style or specific word choices do not influence future generations for other users, maintaining a clear boundary between your content and our core technology.

Metadata kept for billing

We retain request metadata—such as timestamps, character counts, and status codes—strictly for billing and usage verification. This information allows us to accurately charge you based on the 1 million characters per $10 rate. All other personal data is minimal, and we do not sell or share your usage patterns with third parties.

  • Character counts are calculated precisely, including spaces and punctuation.

Technical Infrastructure

Sound wave illustration for: Technical Infrastructure

AudioPilot operates as a cloud-based text-to-speech API. We do not offer on-premise installations or dedicated private servers. All synthesis happens on our standard cloud infrastructure, accessible via standard HTTP requests.

Users interact with the service through our public API endpoints. There are no local software packages or proprietary SDKs to install. The system relies on standard data centers to handle request routing and audio generation.

Cloud-based API

We provide a RESTful API accessible over the internet. Requests are sent via POST to our endpoint, and audio files are returned directly in the response. This design allows easy integration with any programming language that supports HTTP requests, without requiring local processing power.

No on-premise options

We do not offer on-premise installations or dedicated private servers. There is no option to install the TTS engine directly on your own hardware or within your private network. The service is entirely delivered via our cloud infrastructure.

Standard data centers

Our infrastructure runs on standard commercial data centers. We do not offer specific geographic data-center choices, nor do we provide SLA guarantees or enterprise-level uptime contracts. The system is designed for reliability but operates on a best-effort basis typical of cloud API services.

Technical Infrastructure

Support and Communication

Sound wave illustration for: Support and Communication

AudioPilot is run by a small, dedicated editorial team focused on the audiobook and self-publishing workflow. We communicate directly with you to ensure our API meets the needs of freelance narrators and indie authors without corporate bureaucracy.

Email support only

All inquiries are handled via email. This allows us to provide detailed, thoughtful responses to technical questions about character limits, voice selection, or API integration.

No phone or live chat

We do not offer phone support or live chat widgets. There is no on-call team to page during your recording sessions. Email is our single channel, keeping operations simple and transparent.

Response times

We aim to respond to all emails within one business day. During high volume periods, such as major publishing seasons, responses may take slightly longer. We prioritize clear, accurate answers over speed.

Honest Limitations

Sound wave illustration for: Honest Limitations

AudioPilot is an independent API built for efficiency, not enterprise guarantees. We do not offer a Service Level Agreement (SLA) or a fixed uptime guarantee. Our infrastructure is reliable, but we do not contractually promise specific availability percentages or financial credits for downtime.

We operate without enterprise contracts, meaning there are no minimum spend requirements or custom volume commitments. This keeps pricing simple and transparent for freelance narrators and self-publishing authors who need predictable costs without negotiating complex terms.

No SLA or uptime guarantee

We do not provide a formal Service Level Agreement (SLA) or guarantee a specific uptime percentage. While our cloud API is stable, we do not contractually commit to 99.9% availability or offer financial credits if service interruptions occur. This approach allows us to focus development resources on voice quality and pricing transparency rather than maintaining redundant enterprise-grade infrastructure.

Requests are processed in sequence, so under load a request may wait in a queue.

No enterprise contracts

We do not offer enterprise contracts, custom volume discounts, or dedicated support lines. Our pricing is flat: $10 per 1 million characters, regardless of usage volume. There are no minimum monthly spends or long-term commitments required to use the API.

This structure is designed for freelancers and indie authors who prefer simple, predictable billing over negotiated enterprise agreements. You can top up with USDT (TRC-20) as needed, and your balance never expires.

No certifications like SOC 2

We do not hold third-party certifications such as SOC 2, HIPAA, or ISO 27001. Our data policy is straightforward: input text is used only for generation and not for training. Generated audio is returned in the response and not stored. Request metadata is kept solely for billing purposes.

While we prioritize user privacy, we do not undergo the expensive and time-consuming audits required for these certifications. This keeps our operational costs low, allowing us to offer competitive character-based pricing without passing certification overhead to the user.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Once you receive the audio files for each chunk, concatenate them in the correct order.

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. curl documentation
  3. Node.js documentation
  4. MDN: Web Speech API
  5. ISO 639 language codes
  6. W3C WAI: making audio and video accessible
  7. LibriTTS-R corpus (OpenSLR 141)
  8. TRON developer hub: TRC-20
  9. IETF RFC 7845: Ogg Opus
  10. Creative Commons Attribution 4.0
  11. openai-node on GitHub
  12. LibriVox public-domain audiobooks

More on this site