Frequently asked questions
Who owns the PlayVeBet API?
PlayVeBet operates this specific storefront for the text-to-speech API. The API is provided by the entity behind playvebet.com. We are an independent provider, not a subsidiary of any major tech company. Our infrastructure handles requests for the tts-1 and tts-1-hd models.
Are the voices copyrighted?
The voices are based on licensed recordings from LibriTTS-R under CC BY 4.0 and LibriVox public-domain audiobook readings. While the source material has specific licenses, the generated audio files are synthetic. Each file carries an inaudible watermark marking it as synthetic speech. You do not need to worry about underlying voice copyright for standard usage.
Is my data used for training models?
No. 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, such as time, characters, and status, is kept solely for billing purposes. Your data is not repurposed for model improvement or other commercial uses.
Do you have a physical office?
All interactions, including support and account management, are handled digitally through the website and email. This structure allows us to remain agile and cost-effective for our clients.
Can I get an invoice for USDT?
No. We do not provide invoices or VAT documentation. Payments are made via USDT on the TRON network (TRC-20). There are no subscriptions or minimum spends. Since we do not issue invoices, you should manage your own records based on your blockchain transaction history and the balance shown in your account dashboard.
Is there a GDPR certificate?
No. We do not have a GDPR certificate. We also do not offer SLAs, uptime guarantees, or other certifications like SOC 2 or HIPAA. Our data practices are described in our general terms, but we do not hold third-party compliance certificates.
Do you offer a phone number?
No. We do not have a phone number or live chat support. All communication is conducted via email. This allows us to maintain a lean operational structure. You can reach our support team through the contact form on the /contact/ page or by emailing the support address provided in your account settings.
Is the site affiliated with OpenAI?
No. We are not affiliated with OpenAI, despite our API endpoint and request format being compatible with the OpenAI speech endpoint. We use the same request shape, allowing you to use OpenAI SDKs by changing the base_url. However, we are an independent provider with our own models, voices, and pricing structure.
Who writes the content on the site?
The content is written by the PlayVeBet editorial team. We ensure all information matches the product facts exactly. Our team focuses on providing honest, specific details about the API, pricing, and voices. We avoid hype and superlatives, ensuring that every claim is verifiable against our actual service capabilities and current pricing model.
Do you store audio files long-term?
No. Generated audio is returned in the response and not stored long-term. Input text is used only to produce the audio and is not retained for training. We keep request metadata, such as time, characters, and status, for billing purposes. Once the audio is delivered, it is not archived in our systems.
Can I use the API for commercial projects?
Yes. You can use the API for any purpose, including commercial projects. There are no monthly plans, seats, or minimum spends. You pay only for what you use, with failed requests being free. The only requirement is having a valid API key and sufficient balance in your account to cover the character usage.
Is there a privacy policy link?
Do you have a SOC 2 certification?
No. We do not have a SOC 2 certification. We also do not offer SLAs, uptime guarantees, or other enterprise contracts. Our infrastructure is designed for reliability, but we do not provide third-party audited certifications. If you require SOC 2 compliance, you may need to conduct your own due diligence or request specific details via email.
How do I contact support?
Support is available by email only. We do not offer a phone number or live chat. You can find the support email address on the /contact/ page or in your account dashboard. Please include your API key and a description of your issue.
Company Structure and Identity
PlayVeBet operates as an independent storefront for a single text-to-speech API, designed specifically for language learning startups. We do not own the underlying engine; we provide the interface and billing layer. Our structure allows for direct, character-accurate audio generation via standard HTTP endpoints, ensuring seamless integration into educational workflows without intermediary complexity.
Independent Storefront Model
Each site in our network is an independent storefront selling the same API services. We handle account creation, key management, and USDT-based top-ups directly. This model ensures that pricing and rate limits remain consistent across all access points, while allowing each domain to maintain its own identity and billing records.
Network of Independent Sites
Our network consists of multiple independent domains, each serving as a distinct entry point to the same backend. While the API endpoint and voice library remain identical, account balances and API keys are isolated per site. This separation allows different educational platforms to operate independently without shared account constraints.
Single API Infrastructure
All storefronts connect to a single cloud infrastructure. When you send a request to https://api.playvebet.com/v1/audio/speech, you are accessing the same processing queue as any other user. This unified architecture ensures consistent character pricing ($0.01 per 1,000 characters) regardless of which independent site you used to obtain your key.
Voice Licensing and Sources
PlayVeBet’s voice models are generated from licensed recordings sourced from the LibriTTS-R dataset. This dataset comprises audio readings from LibriVox public-domain audiobook readings.
LibriTTS-R Dataset Usage
The eight voice presets—Aria, Nova, Luna, Sage, Felix, Milo, Atlas, and Orion—are derived directly from these source recordings. By utilizing the LibriTTS-R dataset, we maintain a consistent acoustic baseline while allowing for precise text-to-speech synthesis tailored to educational workflows.
CC BY 4.0 License Terms
LibriTTS-R is distributed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. This permits the use, adaptation, and distribution of the source material, provided appropriate credit is given to the original contributors and the license terms are preserved in our documentation.
LibriVox Public Domain Source
The underlying audio files originate from LibriVox, a platform hosting public domain audiobook readings.
Data Policy and Privacy
PlayVeBet processes input text exclusively for the purpose of generating the requested audio file. We do not use your source text to train our models or improve the underlying TTS engine, ensuring that your educational content remains proprietary and distinct from our training data.
Input Text Usage Restrictions
The text you submit via the API is used solely to synthesize the specific audio response returned in that request. Once the audio is generated and delivered, the input text is not retained for any other purpose, such as model improvement or secondary analysis.
Audio Generation Storage Policy
Generated audio files are returned directly in the API response and are not stored on our servers after delivery. Your application is responsible for storing the resulting audio files if needed for your language learning workflows.
Billing Metadata Retention
We retain request metadata, including the timestamp, character count, and status (success or failure), specifically for billing and usage verification. This data ensures accurate charge calculation based on the $0.01 per 1,000 characters rate and allows us to process refunds for failed requests.
Support and Contact Information
PlayVeBet provides support exclusively via email. This channel serves all inquiries regarding API usage, billing discrepancies, or technical questions related to the text-to-speech service.
Email-Only Support Channel
All communication is routed through a single email address. This ensures that every query is tracked and addressed systematically without the distraction of multiple platforms. Please include your API key and account details to expedite resolution.
No Live Chat Availability
We do not operate a live chat widget on our website. This decision allows our support engineers to focus on complex technical issues rather than managing concurrent chat sessions. You can expect a detailed written response rather than a quick, potentially vague chat reply.
No Phone Support Number
There is no dedicated phone line for customer inquiries. This structure aligns with our API-first approach, where developers prefer asynchronous communication that creates a permanent record of the discussion. Email remains the most efficient way to share code snippets and error logs.

Editorial Team and Content
We maintain editorial consistency across all network sites through a unified content framework. Each page is reviewed to ensure strict adherence to the product facts, preventing feature inflation or marketing exaggeration. Our writers prioritize precise technical descriptions over promotional language, ensuring that developers receive accurate information about the API’s capabilities and limitations.
Guided by PlayVeBet Editorial Team
Our editorial team ensures that every claim on this site is verifiable against the single source of truth. We do not invent client stories or use superlatives like "best" or "fastest." Instead, we describe specific workflows, such as splitting long texts into 4096-character segments for synthesis, and cite exact pricing and rate limits.
Fact-Based Content Standards
We validate all technical details, including endpoint structures and voice presets, against the live API documentation. If a feature is not listed in our product facts, it is treated as non-existent. This approach prevents confusion for language learning startups integrating our TTS API into their educational workflows.
No Hype or Superlatives
Our content avoids marketing fluff. We do not claim industry leadership or superior realism without specific, dated comparisons. We state exactly what the API does, such as generating audio from text via standard HTTP requests, and what it does not, such as supporting SSML or custom voice cloning.
Technical Limitations and Honesty
PlayVeBet operates as an independent storefront without formal Service Level Agreements or uptime guarantees. While our infrastructure processes requests sequentially with consistent performance, we do not contractually guarantee specific availability windows or response times. This model allows us to maintain straightforward pricing without enterprise overhead.
No SLA or Uptime Guarantee
We do not offer formal SLAs or uptime guarantees. Requests are processed sequentially, and during high load, synthesis may experience queue delays. We prioritize accurate character processing over speed guarantees, ensuring every request receives full attention without prioritization tiers.
No Enterprise Contracts
Our pricing is uniform for all users. There are no negotiated volume discounts, custom billing cycles, or dedicated support tiers. Every account, regardless of usage volume, accesses the same API endpoints, rate limits (60 requests per minute), and voice presets under identical terms.
No On-Premise Installation
PlayVeBet is a cloud-native API. We do not provide on-premise installation options or dedicated data-center choices. All text synthesis occurs on our servers, and audio files are returned directly in the response without persistent storage. This ensures consistent engine updates and uniform voice quality across all users.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Empower your global team with intuitive language learning tools that bridge cultural gaps and accelerate collaboration.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- openai-node on GitHub
- LibriTTS-R corpus (OpenSLR 141)
- IETF RFC 7845: Ogg Opus
- LibriTTS-R paper (arXiv 2305.18802)
- Node.js documentation
- OpenAI API reference: create speech
- ISO 639 language codes
- W3C WAI: making audio and video accessible
- TRON developer hub: TRC-20
- LibriVox public-domain audiobooks
- Tether (USDT)
