About the EchoGuide Team, Our Mission, and Our Values

By EchoGuide editorial team · Updated 2026-11-19

This page explains who we are and why we built EchoGuide. We are an editorial team focused on tourism, creating an independent storefront for a text-to-speech API designed for museum staff and tour guides. You will learn about our voice licensing, data privacy practices, and the specific limitations of our service. Our goal is to help you create natural-sounding audio guides without writing code, using honest and specific facts about our technology.

We focus on supporting tourism professionals who need reliable, easy-to-use audio solutions. This page covers our mission to simplify audio guide creation, our values regarding data privacy, and how to contact us for support. Whether you are running a small museum or a large tour operation, you will find clear information about our voices, pricing, and technical details here.

About the EchoGuide Team, Our Mission, and Our Values

Frequently asked questions

Who runs this website?

EchoGuide is an independent storefront for a cloud text-to-speech API. We help tourism and museum staff create natural-sounding audio without coding. Our API turns your guide scripts into ready-to-play MP3s with authentic accents. We are not affiliated with OpenAI, ElevenLabs, or any other brand mentioned in comparisons.

Where do the voices come from?

Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. These sources provide the authentic German and international accents we use. Each generated file carries an inaudible watermark that marks it as synthetic speech, ensuring transparency.

Is my text data safe?

Yes. Input text is used only to produce the audio and is not used for training. We keep request metadata, such as time, characters, and status, strictly for billing purposes. Your content remains private and is not stored or repurposed for other uses beyond generating your audio files.

Do you store the generated audio?

No. Generated audio is returned in the response and not stored on our servers. We retain only the request metadata required for billing and usage tracking. Once you receive your audio file, it is yours to use, and we do not keep a copy of the generated content.

Can I contact you by phone?

No, we do not have a phone number or live chat. Support is provided by email only. If you have questions about your account, billing, or API usage, please reach out via email. We aim to respond promptly to all inquiries sent through our support channel.

Are you affiliated with OpenAI?

No, we are not affiliated with OpenAI. Our API endpoint shape matches the OpenAI speech endpoint, so official OpenAI SDKs work by changing the base URL. However, we are an independent storefront with our own keys, pricing, and voice presets, distinct from OpenAI’s services and infrastructure.

Do you have an office?

As a cloud-based API service, we operate independently without a public-facing office for walk-ins. Our team is available via email for support, and our infrastructure is hosted in the cloud to serve global tourism and museum clients.

How are voices licensed?

Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. This ensures we have the right to use these voice profiles. The resulting synthetic speech is generated via our API, and each file includes an inaudible watermark to identify it as synthetic.

Who we are

Sound wave illustration for: Who we are

We noticed that many tourism professionals write excellent scripts but struggle to turn them into clear audio files. We wanted to remove the technical barriers, so we created a tool that turns your text into natural-sounding speech without requiring any coding knowledge.

Our approach is simple: you provide the text, and we handle the synthesis. Whether you are creating an audio guide for a history museum or a self-guided tour for a travel agency, our system handles the heavy lifting. We focus on making the process as easy as writing an email, allowing you to concentrate on your content rather than the technology.

Editorial team focused on tourism

Editorial team focused on tourism

We know that an audio guide needs to be clear, engaging, and accurate. By focusing on this niche, we ensure our API settings and voice presets are optimized for guide scripts, museum labels, and tourist information.

No-code friendly approach

No-code friendly approach

You do not need to be a developer to use EchoGuide. Our platform is designed for tourism staff who are experts in their field, not in technology. You can generate audio files directly through our web interface or use simple copy-paste code snippets if you prefer. We handle the complex API details so you don't have to.

  • Web interface for direct text-to-audio conversion
  • Simple API integration for those who want to automate their workflow

Independent storefront

Independent storefront

Voice licensing

Sound wave illustration for: Voice licensing

Based on LibriTTS-R dataset

Based on LibriTTS-R dataset

Our voices are built from the LibriTTS-R dataset, which provides a high-quality foundation for natural-sounding speech. This dataset ensures that the audio generated for your museum guides or tourism scripts sounds authentic and clear.

CC BY 4.0 license

The underlying audio data is licensed under CC BY 4.0, allowing us to integrate these voices into your generated MP3s with proper attribution.

LibriVox public domain source

The recordings originate from LibriVox public-domain audiobook readings. By using these licensed recordings, we can offer you reliable, natural voices without the complexity of custom voice design or cloning.

Data privacy policy

Sound wave illustration for: Data privacy policy

We respect your creative content and operational data. When you use EchoGuide to turn guide scripts into audio, we process your text solely for the purpose of generating the speech file. We do not use your input text to train our models or improve our voice algorithms, ensuring your unique museum narratives remain yours.

Input text not used for training

Your text is used only to produce the audio and is not used for training. This means your specific guide scripts, historical notes, or tour descriptions are not ingested into our training data for future voice model improvements.

Generated audio not stored

Generated audio is returned in the response and not stored. Once you receive your MP3 file, we do not keep a copy of the generated speech on our servers for later retrieval or analysis.

Metadata kept for billing

Request metadata (time, characters, status) is kept for billing. We retain minimal data such as when the request was made, the character count, and whether it succeeded, solely to calculate your usage and process your TRC-20 top-ups accurately.

Service limitations

Sound wave illustration for: Service limitations

EchoGuide is an independent storefront, not a large enterprise provider. We focus on delivering a reliable, straightforward API for tourism and museum professionals without the overhead of complex enterprise agreements. Our service is built on transparency and simplicity, allowing you to integrate audio guides quickly without negotiating custom terms or waiting for lengthy onboarding processes. This approach keeps our pricing clear and our operations lean, ensuring that your primary concern remains the quality of your audio content rather than administrative details.

We do not offer a Service Level Agreement (SLA) or an uptime guarantee. While we strive to maintain consistent service, we do not promise specific availability percentages or financial credits for downtime. This means our service may experience occasional interruptions, especially during high traffic, without formal compensation. This model suits teams who value flexibility and direct access over guaranteed contractual performance metrics.

No SLA or uptime guarantee

We do not provide a Service Level Agreement (SLA) or an uptime guarantee. While we strive for reliability, we do not promise specific availability percentages or offer financial credits for downtime. This means our service may experience occasional interruptions, especially during peak usage, without formal compensation. This model suits teams who value flexibility and direct API access over guaranteed contractual performance metrics.

Requests are processed sequentially, so under heavy load, your synthesis job may wait in a queue. Typical speed is roughly real-time for long texts, but short phrases may take a few seconds. We do not guarantee instant delivery for every request, so please build appropriate buffer times into your workflow.

  • No financial credits for downtime
  • No guaranteed 99.9% or higher uptime
  • Queue processing during high load

No enterprise contracts

EchoGuide operates as an independent storefront with no enterprise contracts. We do not offer custom pricing tiers, dedicated account managers, or negotiated terms for high-volume users. Each account is billed according to the standard rate: $10 per 1 million characters. This simplicity allows for quick onboarding and predictable costs without the need for legal reviews or long-term commitments.

Our service is designed for self-service integration. You manage your API keys, monitor your balance, and handle your own infrastructure. This is ideal for tourism operators and museum staff who prefer direct control over their audio production workflow without relying on a vendor’s sales or support team for routine issues.

No certifications listed

We do not hold or display specific industry certifications such as SOC 2, HIPAA, or GDPR certificates. While we follow standard data practices—keeping input text only for synthesis and not using it for training—we do not undergo third-party audits to validate these claims. Our privacy approach is transparent but not formally certified, so please assess our data handling against your own institutional requirements before integrating into sensitive environments.

Service limitations

How to contact us

Sound wave illustration for: How to contact us

For questions about your account, billing, or API usage, our support team is available via email. We aim to respond to all inquiries as quickly as possible, though response times may vary depending on volume.

We keep things simple. You can reach us directly without navigating complex menus or waiting on hold for a representative who might not know your specific use case.

Email support only

All communication goes through our support email address. This is the single channel for technical issues, billing questions, and general inquiries regarding the EchoGuide API.

No phone number

We do not maintain a telephone line for customer support. This allows us to keep overhead low and pass those savings on to you as tourism professionals.

No live chat available

There is no real-time live chat widget on our site. If you prefer asynchronous communication, email is the best way to ensure your question is documented and answered thoroughly.

Our mission

Sound wave illustration for: Our mission

EchoGuide exists to remove the technical barrier between your guide script and the final audio file. We provide a simple, code-free workflow that turns your text into high-quality MP3s, allowing museum staff to create professional audio guides without needing developers or complex software setups.

Simplify audio guide creation

We focus on making the process straightforward: paste your text, choose a voice, and receive your audio. This allows tourism teams to produce content quickly, whether for a single exhibit or a full museum tour, without getting bogged down in technical details.

Support tourism professionals

Our tool is built for those who know the stories but may not know the tech. By handling the synthesis engine, we let you focus on content and visitor experience, ensuring your audio guides are accessible and natural-sounding for all guests.

Honest and specific facts

We believe in transparency. We do not promise infinite uptime or enterprise-level SLAs. We clearly state our pricing, character limits, and supported languages. You get exactly what the API delivers, with no hidden features or inflated claims about voice cloning or real-time streaming.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Support your international visitors with clear, natural audio in their native tongue.

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-python on GitHub
  3. ISO 639 language codes
  4. W3C WAI: making audio and video accessible
  5. LibriVox public-domain audiobooks
  6. IETF RFC 7845: Ogg Opus
  7. OpenAI API reference: create speech
  8. TRON developer hub: TRC-20
  9. MDN: Web Speech API
  10. FFmpeg documentation
  11. curl documentation
  12. Creative Commons Attribution 4.0

More on this site