Your Independent Cloud API for Text-to-Speech Solutions

By AudioPage editorial team · Updated 2026-11-18

AudioPage is an independent storefront for the AudioPage TTS API. We help no-code authors turn manuscripts into audio files without writing code or buying expensive subscriptions. Send text to our endpoint and receive an audio file. The API uses the same request shape as OpenAI, so you can use standard tools by changing the base URL. This approach lets you generate audiobooks directly from your writing workflow.

Our voices are based on licensed recordings from LibriVox public-domain audiobook readings. Input text is used only to produce audio and is not used for training. We do not offer service-level agreements, certifications, or phone support. You can reach our support team via email for any questions about your account or billing. Read on to compare voices, prices, and formats to find the right tool for your audiobook.

Your Independent Cloud API for Text-to-Speech Solutions

Frequently asked questions

Who runs this site?

AudioPage is an independent storefront for the same text-to-speech API. We operate as a self-publishing tool for no-code authors, allowing you to generate audio files directly without learning Python or managing complex infrastructure.

Are you affiliated with OpenAI?

No. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint shape matches OpenAI’s for convenience, but we are a separate entity using our own infrastructure.

How are voices licensed?

Our voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. This ensures high-quality, legally sourced audio foundations for our eight voice presets used in synthesis.

Do you use my text for training?

No. Input text is used only to produce the audio and is not used for training models. Generated audio is returned in the response and not stored. Request metadata (time, characters, status) is kept for billing purposes only.

Where is my data stored?

We retain request metadata—time, character count, and status—solely for billing accuracy. Your input text is processed to generate audio and is not stored long-term. The resulting audio file is returned directly in the API response and is not retained on our servers. We do not use your input text for training models.

How do I contact support?

Support is available by email only. We do not offer a phone number or live chat. Please use the contact page to reach us with any questions regarding your account, billing, or technical issues with the API.

Do you have an SLA?

No. We do not offer an SLA, uptime guarantee, or enterprise contract. Our service is designed for independent authors and developers who do not require strict commercial guarantees or dedicated support tiers for their audio generation needs.

Are you certified?

No. We do not hold certifications such as SOC 2, HIPAA, or GDPR certificates. As an independent storefront, we prioritize accessible text-to-speech technology without the overhead of enterprise-grade compliance documentation and audits. Our focus remains on delivering reliable audio files for your manuscripts, ensuring straightforward pricing and usage without complex regulatory requirements.

Do you have a phone number?

No. We do not offer a phone number or live chat. All support requests are handled via email. This approach helps us maintain a lean operation and keep costs low for our users, ensuring you pay only for the audio generation you need without overhead for premium support channels.

Is this a store or a blog?

This is an independent storefront for the AudioPage text-to-speech API. We provide API access for generating audio files from text. While we offer documentation, our primary function is selling API usage, not publishing articles. Use our API endpoint to send text and receive audio files, or consult our guides for integration steps.

Do you sell other APIs?

We offer only the AudioPage text-to-speech API. We do not provide speech-to-text, translation, or other services. Our focus is strictly on converting text into audio files. This means you won’t find video editing, custom voice cloning, or streaming WebSocket endpoints here. We offer a single, specialized API endpoint for generating audio from text inputs.

What is the editorial team?

We do not have an editorial team. AudioPage is an independent storefront operated by the AudioPage team. Our content is practical and specific to no-code authors, focusing on clear instructions rather than journalistic reporting or reviews.

Why CC BY 4.0?

Our voices are based on LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. This license allows us to legally use these recordings as the foundation for our synthetic voices, ensuring high quality while respecting the original creators’ licensing terms.

Is the watermark audible?

No. Every generated file carries an inaudible watermark that marks it as synthetic speech. You will not hear it during playback, but it serves as a digital signature to identify the audio as AI-generated without affecting listening experience.

Do you offer refunds?

If synthesis fails, the charge is returned in full, making that request free. We do not offer refunds for successful audio generations. Your balance never expires, so you can use your credit whenever you are ready. Failed requests are automatically credited back to your account.

Can I use the audio commercially?

Yes. You can use the generated audio for commercial purposes, including audiobooks and self-publishing. The 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. Voices are based on licensed recordings from LibriVox public-domain audiobook readings, allowing you to distribute the files according to your publishing needs.

Do you have a team size?

We are an independent storefront, so we do not publish a specific team size. Our lean structure allows us to operate efficiently, providing direct API access and support without the bureaucracy of a large corporate entity. This means you get straightforward service without the overhead of an enterprise division.

Where are you located?

We operate as a cloud-based service via playk74.com. We do not offer data-center choice or specify a physical location. Our infrastructure is not tied to a specific geographic region, and we do not provide on-premise installation options. This design ensures broad accessibility without the need for you to select or manage specific server locations.

Do you have a newsletter?

No. We do not offer a newsletter. Updates and information are available through our documentation. We keep communication direct, so you can check your balance, usage, and key status directly on your dashboard page. Support is by email only, with no live chat or phone number.

How do you make money?

We charge $10 per 1 million characters. Payments are made via USDT on the TRON network (TRC-20). We do not have monthly plans or subscriptions, so you only pay for the audio you actually generate. Failed requests are free, and your balance never expires. Top-ups start at $5 and are credited automatically within minutes after the transfer.

Who We Are

Sound wave illustration for: Who We Are

AudioPage is an independent storefront for a cloud text-to-speech API. We help no-code authors turn manuscripts into audio files without learning Python or buying expensive subscriptions. Our dashboard lets you manage keys and test voices, but the core product is the API endpoint you call to receive audio files.

Editorial focus

Editorial focus

We prioritize practical utility over marketing hype. Our documentation and pricing pages list real limits, such as the 4096-character input cap and the $0.01 per 1,000 characters rate, so you know exactly what to expect before you spend.

Industry expertise

Industry expertise

We understand the workflow of self-publishing. Our API handles voice selection and language detection to ensure your manuscript sounds cohesive. You can mix voices and adjust speed to match the tone of your book, from warm narrators to energetic promos.

No-code audience

You do not need to manage complex integrations to get started. Our interface provides ready curl examples and a simple dashboard to monitor usage. We designed our tools to let you generate audio files directly, without writing code or managing complex integrations.

Voice Licensing

Sound wave illustration for: Voice Licensing

AudioPage provides a transparent, independent API for text-to-speech, designed to help authors and creators produce audio without complex technical setups or expensive subscriptions.

Our infrastructure focuses on delivering reliable speech synthesis with clear licensing terms, ensuring you understand exactly how your voice data is sourced and used.

LibriTTS-R source

Our voices are based on licensed recordings from the LibriTTS-R dataset. This data originates from LibriVox, which hosts public-domain audiobook readings. Each voice preset—such as Aria, Nova, or Felix—derives its characteristics from these real human narration samples.

CC BY 4.0 license

The LibriTTS-R dataset is distributed under the CC BY 4.0 license. This license governs the source recordings used to build our voice presets. It allows us to legally process these sources to create the available voices for our API.

Public domain origin

The underlying recordings in LibriTTS-R come from LibriVox, a platform dedicated to public-domain audiobooks. This origin ensures that the foundational audio for our voices is free from restrictive copyright claims, allowing straightforward usage of the generated speech.

Voice Licensing

Data Policy

Sound wave illustration for: Data Policy

AudioPage is built for authors who value their intellectual property. We process your manuscripts strictly to generate audio files and do not use the input text to train or improve our underlying models. Your words remain yours.

Text not trained on

When you send text to our API, it is used solely for the purpose of synthesis. We do not ingest your content into our training datasets, ensuring that your unique voice and narrative style are not repurposed for model development.

No audio storage

Generated audio is returned directly in the response and is not stored on our servers after delivery. Once you have your file, the temporary copy is gone, keeping your audiobook assets private and under your control.

Billing metadata kept

We retain request metadata—such as timestamp, character count, and status—exclusively for accurate billing and usage tracking. This data does not contain the content of your text, only the metrics needed to process your account and invoices.

Honest Limits

Sound wave illustration for: Honest Limits

This section details the operational boundaries of our API service. We provide a straightforward, no-frills text-to-speech endpoint without the enterprise-level contractual protections often found in larger platforms.

No SLA

We do not offer a Service Level Agreement. There is no formal contract guaranteeing specific performance metrics or defining financial compensation if we fail to meet them.

No uptime guarantee

We do not guarantee any specific percentage of uptime. While we strive for consistent operation, brief interruptions may occur without notice or compensation.

No certifications

We do not hold third-party industry certifications. You will not find SOC 2, HIPAA, or GDPR certificates on file, as we operate as a lean independent storefront.

Honest Limits

Contact

Sound wave illustration for: Contact

We provide email support for all inquiries. When you reach out, your message goes directly to our team. There is no automated menu to navigate first, ensuring your question is handled by a person rather than a bot.

Email support only

Email is our single channel for assistance. You can contact us at any time, and a team member will read your message and respond directly. We do not use ticketing systems that require you to wait in a queue before a human sees your issue.

No live chat

We do not offer live chat widgets on this site. If you need immediate clarification, please send an email. Our team reviews messages during working hours and replies via email. This allows us to provide detailed, written answers that you can reference later without rushing.

No phone

There is no phone number for AudioPage. We do not handle voice calls. For no-code authors who prefer written communication, email is sufficient for discussing API keys, billing, or technical details. You can attach screenshots or code snippets to help us resolve your issue faster.

Contact

Independence

Sound wave illustration for: Independence

AudioPage is an independent storefront for a single text-to-speech API. We are not OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand. Our API mimics the OpenAI speech endpoint structure for convenience, but we are not OpenAI.

Not affiliated with OpenAI

Our API mimics the OpenAI speech endpoint structure for convenience, but we are not OpenAI. We do not use OpenAI's engines or infrastructure.

Independent storefront

We operate as a single, independent storefront. We do not resell another company's API; we provide direct access to our own infrastructure and keys.

No bias

Our recommendations focus on practical utility for no-code audiobook creators. We compare voices, prices, and formats based on facts, not vendor marketing.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Turn your written words into immersive audio stories without writing a single line of code today

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

More on this site