EchoPress API: The Story Behind Our Service

By PlayN57 editorial team · Updated 2026-11-18

Welcome to the story behind EchoPress, the independent text-to-speech API built for publishers and WordPress bloggers. This page explains who we are, how we license our voices, and why we designed a simple, transparent service for your content. You will learn about our data policies, and the specific limits of our infrastructure.

If you are looking for a reliable way to turn articles into audio without complex infrastructure, this is your guide. We focus on honest details, clear pricing, and straightforward support. Read on to understand how EchoPress helps you keep readers engaged with natural-sounding audio files, created by a team that understands the needs of digital publishers.

EchoPress API: The Story Behind Our Service

Frequently asked questions

Who runs EchoPress?

EchoPress is an independent storefront for a cloud text-to-speech API. Accounts are created per site, and we operate as a standalone service for publishers and WordPress bloggers. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. We provide a simple, affordable API designed specifically for generating audio versions of your articles without complex infrastructure.

Are the voices copyrighted?

Our voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. Every generated audio file carries an inaudible watermark marking it as synthetic speech. This ensures transparency about the audio source while providing high-quality, natural-sounding voices for your blog content without requiring complex licensing negotiations for each article.

Do you store my blog content?

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. Your blog content remains yours, and we do not retain the actual text or audio files after delivery.

How can I contact support?

Support is available by email only. We do not have a phone number, live chat, or on-premise support team. For any questions regarding your API key, billing, or technical issues, please send an email to our support address. We aim to respond promptly to all inquiries from publishers and developers using our text-to-speech API.

Is this site affiliated with OpenAI?

No, EchoPress is not affiliated with OpenAI. We use a request shape similar to the OpenAI speech endpoint, so official OpenAI SDKs work by changing the base_url to https://api.playn57.com/v1. We are an independent service using different engines and voices. We do not claim to be the official provider for OpenAI or any other major tech brand.

What is the CC BY 4.0 license?

CC BY 4.0 is the license for the LibriTTS-R dataset, while the source recordings come from LibriVox public-domain audiobook readings. This license supports our model of providing accessible, high-quality synthetic voices for publishers. It ensures that the underlying voice data is legally sound for commercial use, allowing you to generate audio for your blog without additional voice licensing fees.

Do you have a physical office?

We operate entirely online, managing accounts, billing, and support through our web interface and email. This structure allows us to keep costs low and offer affordable rates for publishers. You can manage your API key and balance entirely through our website without visiting a physical location.

Are you certified (SOC 2, HIPAA)?

We do not have SOC 2, HIPAA, or GDPR certifications. We are an independent service without enterprise contracts or SLAs. Our focus is on providing a simple, affordable text-to-speech API for bloggers and publishers. We do not offer data-center choices or specific compliance certifications, keeping our infrastructure straightforward and cost-effective for individual and small business users.

Who We Are

Sound wave illustration for: Who We Are

We are a small team of developers and editors who have built static blog sites and know exactly where audio fits into the workflow. We understand that publishers need simple, reliable tools to keep readers engaged without adding complex infrastructure to their existing sites.

The Editorial Team

The Editorial Team

We are developers and editors who have built static blog sites. We understand where audio fits into the publishing workflow.

Publisher-Focused Mission

Publisher-Focused Mission

Our goal is to help WordPress bloggers offer audio versions of their articles. We turn static text into natural-sounding audio that keeps readers on your site longer, using a straightforward API that integrates easily with your existing content.

Independent Storefront

Independent Storefront

EchoPress is an independent storefront for a single text-to-speech API. We are not affiliated with OpenAI or other major brands. We provide direct access to the API with transparent pricing and simple usage, designed specifically for the needs of content creators and publishers.

Voice Licensing

Sound wave illustration for: Voice Licensing

EchoPress voices are based on licensed recordings from the LibriTTS-R dataset (CC BY 4.0) and LibriVox public-domain audiobook readings. This approach allows us to offer consistent, natural-sounding audio for your blog posts while maintaining clear provenance for every voice preset.

LibriTTS-R Dataset

LibriTTS-R Dataset

Our eight voice presets are built directly from the LibriTTS-R dataset, which provides a robust foundation for clear, articulate narration.

CC BY 4.0 License

The underlying audio data is licensed under Creative Commons Attribution 4.0 (CC BY 4.0). This transparent licensing model means the underlying audio data is licensed under Creative Commons Attribution 4.0 (CC BY 4.0).

Public Domain Sources

Many of the source recordings come from LibriVox public-domain audiobook readings. By leveraging these existing public domain resources, we keep infrastructure simple and costs low, passing the savings directly to you as a publisher.

Data Policy

Sound wave illustration for: Data Policy

EchoPress is built for bloggers who care about their content. We process your text strictly to generate audio, ensuring your articles remain yours. We do not use your input text to train our models, so your editorial voice stays unique to your site.

Input Text Usage

Your text is sent to the API engine solely to produce the audio file. Once the synthesis is complete, the input text is not stored for future training or analysis. This ensures your content remains exclusively yours, with no hidden data mining.

Audio Storage

The generated audio file is returned directly in the API response to your server or application. We do not store the resulting audio files on our servers. You retain full control over where the audio lives, whether on your WordPress media library or a CDN of your choice.

Billing Metadata

We keep a simple record of your requests: timestamp, character count, and status. This data is used only to calculate your usage and ensure accurate billing. No personal content is mixed into these records, keeping your operational data clean and transparent.

Our Limits

Sound wave illustration for: Our Limits

We run a lean service for bloggers and publishers, which means we do not offer a formal SLA guaranteeing specific uptime or latency targets. While we strive for reliability, our infrastructure is designed for cost-efficiency rather than enterprise-grade redundancy.

No SLA Guarantee

Our service is built on a shared cloud infrastructure optimized for affordable character pricing. This allows us to offer $0.01 per 1,000 characters, but it also means we cannot promise 99.99% uptime or compensation for downtime.

  • Shared infrastructure, not dedicated servers
  • Cost-optimized architecture
  • No uptime compensation

Email Support Only

We do not have a phone number or live chat. All support is handled via email to keep operational costs low. Our team is passionate about helping publishers, but we are a small team without a call center.

  • Email only
  • No phone number
  • No live chat

No Enterprise Contracts

EchoPress is an independent storefront for a single TTS API. We do not offer custom enterprise contracts, SLAs, dedicated account managers, or on-premise install. If you need a custom agreement, you may need to explore other providers.

  • No custom contracts
  • No dedicated account managers
  • Standard pricing only
Our Limits

Contact Us

Sound wave illustration for: Contact Us

We handle all communication through a single, dedicated email address. There is no phone number, no live chat, and no automated queue waiting to connect you to a human. This keeps our support team focused and efficient, allowing us to manage inquiries without the overhead of call centers.

You can reach us at [email protected] for any questions regarding your account, billing, or API usage. We believe in direct, clear communication that respects your time and ours.

Email Support

Send your questions to [email protected]. This is our only channel for customer service. We prefer email because it allows us to provide detailed, thoughtful answers without the pressure of real-time calls.

None

No Phone Number

We do not offer a phone line. If you call, you will not reach us. This decision helps us keep costs low and ensures that every support request is documented and searchable for future reference.

None

Response Expectations

We aim to reply within 24 hours on business days. Since we are a small independent team, complex technical queries may take a bit longer. Please include your API key or account email in your message so we can locate your details quickly.

None

  • Business days: Monday–Friday
  • Response time: ~24 hours
  • Channel: Email only

Why We Built This

Sound wave illustration for: Why We Built This

We built EchoPress because adding audio to WordPress blogs felt unnecessarily complex for independent publishers. Most solutions required heavy infrastructure or expensive enterprise contracts, creating a barrier for smaller sites. We wanted a simple API that turns static text into engaging audio files without the overhead, letting you keep readers on your site longer with minimal effort.

Simplifying TTS for Blogs

Publishers often struggle to convert long articles into audio formats that work seamlessly with existing blog layouts. Our API accepts standard text inputs and returns audio files directly, integrating easily with WordPress themes or custom plugins. This removes the technical friction, allowing you to focus on content rather than managing complex voice synthesis infrastructure.

  • Direct API integration for WordPress and static sites
  • No heavy infrastructure or dedicated servers required
  • Supports mp3, wav, opus, flac, and pcm formats

Affordable Access

High-quality synthetic speech often comes with steep monthly fees or per-minute charges that add up quickly. We price our service at $10 per million characters, ensuring that even high-volume publishers can offer audio versions of their articles without breaking their budget. There are no minimum spends or subscriptions, so you only pay for what you use.

  • $0.01 per 1,000 characters
  • No monthly plans or hidden fees
  • Free trial credit for new accounts

Transparency First

We believe publishers should know exactly what they are getting. Our service uses licensed voices from public-domain sources, and every generated file carries an inaudible watermark to identify it as synthetic speech. We do not use your input text for training, and we clearly state our limits, such as the lack of an SLA or phone support, so you can plan your content strategy with confidence.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Each voice is based on licensed recordings, ensuring high-quality audio that fits your content's tone.

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

More on this site