About MuseVoice: The API for Museum Audio

By MuseVoice editorial team · Updated 2026-11-18

This page explains who powers MuseVoice and why we built it for museum and tourism product teams. You will learn about our voice licensing model, our data privacy practices, and how to reach us. Support is available exclusively by email, ensuring clear communication for your team’s needs.

We are an independent storefront focused on delivering professional, multilingual audioguides without the need for voice actors. Read on to understand our mission to simplify audio content creation for heritage sites and travel experiences, using licensed synthetic speech that fits your specific constraints.

About MuseVoice: The API for Museum Audio

Frequently asked questions

Is MuseVoice affiliated with OpenAI?

No. MuseVoice is an independent storefront for the same text-to-speech API. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. You can use the official OpenAI SDKs by simply changing the base_url to our API endpoint.

Where are the voices recorded?

Our voices are based on licensed recordings from LibriTTS-R (CC BY 4.0), derived from LibriVox public-domain audiobook readings. This approach ensures high-quality synthetic speech without requiring custom voice cloning or uploading your own voice. Additionally, each generated audio file carries an inaudible watermark that clearly marks it as synthetic speech, providing transparency for your museum or tourism content.

Do I need to credit the voices?

The source recordings are from LibriVox public-domain audiobook readings under CC BY 4.0. We do not mandate specific credit formats for your generated audio files. Every file carries an inaudible watermark marking it as synthetic speech, clearly indicating its origin for your museum or tourism audiences without requiring explicit attribution in your project deliverables.

Can I use the audio for commercial projects?

Yes. MuseVoice is designed for museum and tourism product teams to generate professional, multilingual audioguides and audio content. There are no monthly plans, seats, or minimum spend requirements. You pay only for what you use, making it suitable for any commercial heritage or travel experience.

How is my data protected?

Your input text is used solely to generate audio and is never used for training models. Generated audio is returned in the response and not stored long-term. We retain request metadata—such as time, character count, and status—strictly for billing purposes. This ensures transparency while keeping your creative content private and secure during the generation process.

Is there an SLA for uptime?

No. We do not offer an SLA, uptime guarantee, or enterprise contract. Requests are processed sequentially, so under load, a request may wait in a queue. Typical speed is roughly real time (about 25 characters per second), but short phrases may take a few seconds to generate.

Do you offer enterprise contracts?

No. We do not offer enterprise contracts, SLAs, or on-premise installs. Our model is simple: $10 per 1 million characters. There are no seats, subscriptions, or minimum spend. You can top up with USDT on the TRON network whenever needed.

How do I contact support?

Support is by email only. We do not offer a phone number, live chat, or dedicated enterprise line. For questions about your account, usage, or billing, please contact us via email. We focus on providing a reliable API with clear documentation and straightforward pricing, ensuring you can resolve issues efficiently without waiting for live agents.

What is the licensing model?

Our voices are based on LibriTTS-R (CC BY 4.0) from LibriVox public-domain audiobook readings. Each generated file carries an inaudible watermark marking it as synthetic speech. You can use the audio for your projects without worrying about complex licensing, as we handle the source rights.

Are the voices synthetic or human?

Our voices are synthetic, generated from licensed recordings of human speech. They are not imitations of real people, celebrities, or politicians. Every generated file carries an inaudible watermark that marks it as synthetic speech, ensuring transparency about the nature of the audio content you create.

Do you store my text?

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. Request metadata (time, characters, status) is kept for billing. Your actual text content is not retained after processing.

Can I delete my account data?

We retain request metadata for billing purposes. You can revoke access instantly by issuing a new API key, which stops the old one immediately. For specific data deletion requests, please contact support via email.

Is the API GDPR compliant?

We do not hold a GDPR certificate, nor other certifications like SOC 2 or HIPAA. We handle data responsibly: input text is used solely to produce audio and is not used for training. Generated audio is returned in the response and not stored. We retain request metadata (time, characters, status) strictly for billing purposes. For specific legal requirements, please consult our documentation or contact us via email.

Who owns the generated audio?

We do not explicitly define ownership of the generated audio. Your input text is not used for training, and the audio is not stored after delivery. You receive the file directly via the API response. For specific ownership details, please refer to the terms on our pricing page or contact support.

Who We Are

Sound wave illustration for: Who We Are

MuseVoice is a product-focused team dedicated to solving the specific challenges of museum and tourism audio production. We understand the logistical constraints of heritage sites and design our API to streamline the creation of professional, multilingual audioguides without the overhead of hiring voice actors for every language.

Product-focused team

Product-focused team

Our engineering and product decisions are driven entirely by the needs of tourism product teams. We prioritize reliable, licensable synthetic speech that integrates smoothly into existing audio guide workflows, ensuring consistent quality across diverse visitor experiences.

Built for tourism needs

Built for tourism needs

We designed the API to handle the unique demands of heritage content, including support for 23 languages and voice presets optimized for narration and instructional clarity. The system generates watermark-safe audio files that meet the compliance and branding needs of modern museums.

Independent storefront

MuseVoice operates as an independent storefront for the underlying text-to-speech API. This structure allows us to maintain direct control over pricing, licensing, and service terms, ensuring that museum teams receive transparent, predictable billing without third-party platform fees or restrictions.

Voice Licensing

Sound wave illustration for: Voice Licensing

MuseVoice voices are generated from the LibriTTS-R dataset, which was created using public domain audiobook readings from LibriVox. This foundation ensures that the synthetic voices you use in your museum audio guides are built on licensed, high-quality source material without the legal complexities of traditional voice actor contracts.

The underlying data carries a CC BY 4.0 license, providing a clear legal framework for using these voices in commercial tourism products. While the source recordings are freely available, our API handles the technical synthesis and delivery, allowing your team to focus on content rather than licensing logistics.

LibriTTS-R licensed

The voices in our API are derived from the LibriTTS-R dataset, a large-scale text-to-speech dataset based on public domain audiobooks. This gives your museum and tourism products a consistent, professional audio quality without the variable costs of hiring individual voice talent for each language.

  • Based on real human recordings from LibriVox

CC BY 4.0 rights

The source recordings are licensed under Creative Commons Attribution 4.0 International. This means the data is free to use, even commercially, provided the original sources are acknowledged where appropriate. Our API simplifies this by providing the final audio file, so you can integrate these voices directly into your audioguide apps and websites.

Public domain sources

We use recordings from LibriVox, a community-driven project that digitizes public domain books. Because these books are in the public domain, the voice recordings are free from restrictive copyright claims, allowing you to generate unlimited multilingual content for your heritage sites without worrying about complex royalty structures.

Voice Licensing

Data Policy

Sound wave illustration for: Data Policy

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

Text not used for training

Your input text is used solely to generate the audio file and is not used for training or improving our models. This ensures your content remains private and your intellectual property stays yours.

No audio storage

Generated audio is returned in the response and is not stored on our servers after delivery. Once the file is sent to your application, we do not retain a copy of the audio file.

Metadata kept for billing

Request metadata, including time, character count, and status, is kept for billing purposes. This allows us to accurately calculate costs and ensure you are charged only for successful synthesis requests.

Support Contact

Sound wave illustration for: Support Contact

MuseVoice is an independent storefront built specifically for tourism and museum product teams. We focus on delivering reliable, multilingual audioguide generation without the overhead of large enterprise support structures. Our team understands the unique constraints of heritage sites and travel experiences, ensuring our API integrates smoothly into your existing workflows.

We keep our support model simple and direct. You won’t find complex ticketing systems or automated bots; instead, you get straightforward communication channels tailored for product teams who need clear answers about API usage, billing, or voice selection.

Email support only

All support inquiries are handled via email. This allows our team to provide detailed, thoughtful responses to your technical or billing questions without the pressure of real-time availability. You can reach us at [email protected] for any assistance regarding your MuseVoice account or API usage.

Email support is our primary channel because it ensures that your questions are documented and addressed by someone who understands the specific needs of museum and tourism audio products. We strive to respond promptly, but due to our lean structure, response times may vary compared to larger support teams.

No live chat

We do not offer live chat support. This decision was made to maintain a focused, efficient support process. Live chat can sometimes lead to fragmented conversations and delayed resolutions, especially when dealing with technical API details or billing inquiries.

By relying on email, we ensure that each query is given the attention it deserves. You can include relevant details like your API key, request examples, or specific issues in your email, allowing our team to investigate and resolve your issue more effectively.

No phone number

There is no phone number for MuseVoice support. We found that phone support often requires scheduling and can be less flexible for product teams working across different time zones or focusing on development tasks.

Email support allows you to communicate at your own pace, providing context and attachments as needed. This approach aligns with the technical nature of our API and the needs of museum and tourism product teams who value clear, documented communication over real-time voice conversations.

Support Contact

Limitations

Sound wave illustration for: Limitations

MuseVoice delivers reliable, file-based audio synthesis rather than real-time streaming. Because requests are processed sequentially, longer texts may wait in a queue, and generation speed aligns with roughly real-time playback (25 characters per second). This batch-oriented approach ensures stable, consistent output for pre-generated audioguides without the complexity of WebSocket connections.

No streaming audio

Our API returns complete audio files (mp3, wav, opus, flac, pcm) upon successful synthesis. There is no partial audio stream or live playback capability. This design suits museum audio guides where content is generated in advance, ensuring every sentence is complete before the user hears it, without buffering interruptions.

No SSML support

We do not support Speech Synthesis Markup Language (SSML). Voice pacing, pauses, and emphasis are controlled solely through the speed parameter (0.25–4.0). If you need precise control over pronunciation or specific pauses, you must split your text into smaller chunks and adjust the speed of each segment manually.

  • No SSML tags (prosody, break, phoneme)

No custom cloning

MuseVoice does not offer voice cloning or custom voice design. You choose from eight licensed presets (e.g., Aria, Felix, Atlas). Each voice is based on licensed recordings from LibriTTS-R and public domain audiobook readings. We do not upload your own voice samples, so you cannot create a unique brand voice from your staff's recordings.

  • No voice upload or cloning
Limitations

Our Mission

Sound wave illustration for: Our Mission

MuseVoice exists to help museum and tourism teams produce professional audio without the cost of hiring voice actors. We provide a reliable API that delivers licensed, watermark-safe synthetic speech, allowing heritage sites to create engaging content at scale.

Making audio accessible

We remove barriers to entry for audio production. With a simple API and transparent pricing of $10 per million characters, teams can generate audio on demand without complex infrastructure or long-term commitments.

Simplifying multilingual content

MuseVoice supports 23 languages, enabling tourism product teams to reach diverse audiences effortlessly. Our API handles language detection and synthesis, ensuring consistent quality across different regions and visitor demographics.

Supporting heritage sites

We understand the unique constraints of heritage and travel experiences. Our technology is designed to integrate seamlessly into existing workflows, helping museums deliver high-quality, multilingual audioguides and audio content.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Our audioguide transforms museum visits into immersive storytelling experiences for visitors.

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. LibriTTS-R paper (arXiv 2305.18802)
  3. IETF RFC 7845: Ogg Opus
  4. OpenAI API reference: create speech
  5. W3C WAI: making audio and video accessible
  6. Tether (USDT)
  7. FFmpeg documentation
  8. LibriVox public-domain audiobooks
  9. MDN: Web Speech API
  10. openai-python on GitHub
  11. Creative Commons Attribution 4.0
  12. openai-node on GitHub

More on this site