Frequently asked questions
Who runs VerbaCore?
VerbaCore is an independent storefront for a cloud text-to-speech API. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand. Our team focuses on providing reliable, scalable TTS infrastructure designed specifically for fintech teams and banks that need consistent audio delivery for customer notifications.
How are voices licensed?
Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0). These sources include LibriVox public-domain audiobook readings. Each generated audio file carries an inaudible watermark to mark it as synthetic speech, ensuring transparency about the origin of the audio content produced by our API.
Is my data used for training?
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. We keep request metadata, such as time, characters, and status, strictly for billing purposes. Your data remains private and isolated from our models.
How do I contact support?
Support is available by email only. There is no live chat or phone support. You can reach us via the contact page or the email link provided in your account dashboard. We aim to respond to inquiries promptly to assist with your integration or billing questions.
Is there a phone number?
No, there is no phone number for VerbaCore. All support is handled via email. This allows us to maintain a focused, asynchronous support structure suitable for technical teams integrating our API. You can find our email address on the /contact/ page of our website.
What is the data policy?
Input text is used solely to generate audio and is not used for training models. Generated audio is returned in the response and not stored on our servers. We retain request metadata, including timestamp, character count, and status, exclusively for billing and usage tracking purposes.
Are there any certifications?
We do not hold specific certifications such as SOC 2, HIPAA, or GDPR certificates. Our infrastructure is designed for reliability, but we do not provide formal compliance documentation. For specific regulatory needs, please review our data policy and contact support via email for further clarification.
Is there an SLA?
No, there is no Service Level Agreement (SLA) or uptime guarantee. Requests are processed sequentially, so under load, a request may wait in a queue. We strive for consistent performance, but we do not guarantee specific availability percentages or response times for our API services.
Can I upload my own voice?
No, we do not offer custom voice cloning or the ability to upload your own voice. We provide eight preset voices based on licensed recordings. If you need a specific voice, you must choose from our available options: Aria, Nova, Luna, Sage, Felix, Milo, Atlas, or Orion.
Is there a WordPress plugin?
No, there is no official WordPress plugin for VerbaCore. You can integrate our API directly into your website or application using standard HTTP requests or the OpenAI SDK by changing the base URL. Our documentation provides detailed examples for integrating the API into various platforms.
Is there a mobile SDK?
No, there is no dedicated mobile SDK. You can use the official OpenAI SDKs by changing the base URL to https://api.playq22.com/v1. This allows you to integrate our text-to-speech capabilities into iOS, Android, or other mobile applications using standard HTTP requests and JSON payloads.
Is there a browser extension?
No, we do not offer a browser extension. Our service is an API that you integrate directly into your applications or workflows. You can send text via HTTP POST requests and receive audio files directly in your browser-based applications using standard JavaScript fetch calls or similar methods.
Is this affiliated with OpenAI?
No, VerbaCore is not affiliated with OpenAI. We are an independent storefront. Our API endpoint shape matches the OpenAI speech endpoint, so their SDKs work by changing the base URL. However, we operate independently, have our own pricing, voices, and infrastructure, and are not owned by OpenAI.
How do I sign up?
Sign up on the /get-api-key/ page using Google or an email and password. Accounts are per site. You will receive a unique API key to start making requests. You can also start with a free trial of $0.50 credit if you sign in with Google.
Who we are
VerbaCore operates as an independent storefront for the VerbaCore text-to-speech API. We maintain full control over our API specifications and documentation, ensuring that our technical details remain accurate and up-to-date without corporate bureaucracy.
This is not an official subsidiary of a larger tech brand. We are a focused team dedicated to serving fintech teams and banks that need reliable, scalable text-to-speech for customer notifications.
Independent editorial team
VerbaCore operates as an independent storefront for the VerbaCore text-to-speech API. We maintain full control over our API specifications and documentation, ensuring that our technical details remain accurate and up-to-date without corporate bureaucracy.
Focused on fintech use cases
We built this API specifically for fintech teams and banks. Our infrastructure handles high-volume, low-latency audio delivery for customer notifications, ensuring your systems stay responsive even during peak transaction times.
Honest, specific content
We avoid hype and superlatives. Every claim on this page is backed by verifiable facts about our API’s capabilities, pricing, and technical limits. We promise only what we deliver.
Voice licensing
VerbaCore’s eight voice presets are built on high-quality licensed recordings, ensuring professional-grade audio for your banking notifications. These voices are based on licensed recordings from LibriTTS-R (CC BY 4.0), from LibriVox public-domain audiobook readings. This foundation allows us to deliver clear, natural-sounding speech without the need for expensive proprietary voice actors.
LibriTTS-R licensed recordings
The core audio data comes from the LibriTTS-R dataset, providing a robust collection of spoken English samples. This dataset serves as the source material for our voice presets, ensuring consistency and high fidelity.
- Derived from LibriVox public-domain readings
- Optimized for clear speech synthesis
CC BY 4.0 license
Our voice models are based on recordings licensed under CC BY 4.0. This license allows us to use, modify, and distribute the audio data for commercial purposes. You receive a clean, usable output without additional licensing fees for the voice source.
LibriVox public-domain source
The original recordings originate from LibriVox, a community of volunteers reading books in the public domain. This means the source material is free from restrictive copyright claims, allowing us to build a reliable, scalable TTS engine focused on fintech performance rather than legal overhead.
Data policy
We process your input text exclusively to generate the requested audio file. We do not use your voice scripts, notification messages, or customer data to train our models or improve the TTS engine. Your content remains yours, ensuring privacy for sensitive banking communications.
Input text used only for synthesis
Your text is sent to the API, converted to speech, and returned in the response. It is not retained for any other purpose. This ensures that your customer notifications and internal scripts remain confidential and are never repurposed for model training.
Audio not stored
Once the audio file is generated and delivered to you, we do not store the resulting speech files. The data is ephemeral, existing only for the duration of the request and response cycle. This minimizes data retention risks for high-volume notification systems.
Metadata kept for billing
We retain request metadata, including the timestamp, character count, and status code. This information is strictly used for accurate billing and to verify that you are charged correctly for the characters processed. This log supports transparent usage tracking for your accounting teams.
Technical limits
VerbaCore operates as an independent editorial team focused on fintech notifications, not a large enterprise with redundant infrastructure. Our API is reliable, but we do not promise 99.9% availability or compensate for downtime. Requests are processed sequentially, so high volume may introduce queuing delays during peak hours.
We hold no SOC 2, HIPAA, or GDPR certification certificates. Support is by email only. We prioritize honest, specific documentation over marketing promises.
No SLA or uptime guarantee
We do not offer a Service Level Agreement (SLA) guaranteeing specific uptime percentages. Our infrastructure is designed for cost-effective scalability rather than redundant enterprise-grade availability. While outages are rare, we do not provide financial credits or compensation if the API becomes temporarily unavailable.
Requests are processed one after another, meaning under heavy load, synthesis may wait in a queue. This ensures fair resource distribution but means latency can vary. We do not offer streaming, WebSocket connections, or real-time partial audio.
No certifications
We do not maintain SOC 2, HIPAA, or GDPR certification documents. Our system is built for efficiency, not for meeting specific regulatory audit requirements that banks might demand for internal compliance. We do not store generated audio, which reduces data retention risks, but we do not provide official compliance seals.
Data input is used only for synthesis and not for training models. While we follow standard privacy practices, we do not offer on-premise installation or data-center selection options. Our infrastructure remains cloud-based and independent, without enterprise contracts or dedicated virtual private clouds.
Email support only
Our support team consists of the editorial developers who built the API. We do not have a dedicated customer success team or a 24/7 help desk. If you encounter an issue with your API key, billing, or voice selection, please send an email to our support address.
We do not offer a phone number or live chat widget on this site. Our email support is the only channel for assistance. We aim to respond to all inquiries promptly during business hours, but we do not guarantee a specific response time. For urgent issues, you may retry your request, as failed requests are free.
- No phone number available
- No live chat widget
- Email is the sole support channel
- No dedicated account managers

Contact information
We value clear, documented communication for enterprise needs. Our support team is available to assist with technical questions, billing inquiries, and integration details. We believe in providing reliable, asynchronous support that respects your team's workflow without the noise of real-time interruptions.
All inquiries are handled through a single, dedicated channel. This ensures that your messages are logged, tracked, and addressed by the same team that understands the API's nuances. You can expect thoughtful, detailed responses rather than quick, generic fixes.
Support by email only
Our primary and only method for customer support is email. This allows us to maintain a complete record of your technical issues and billing questions. You can reach us at [email protected] for any assistance regarding your VerbaCore account or API usage.
No phone number
We do not maintain a direct phone line for customer inquiries. This decision reduces overhead and allows us to keep pricing transparent for fintech teams. You can always reach us via email at [email protected] for detailed, written responses that you can share with your development or product teams.
No live chat
There is no live chat widget on our site. We prefer asynchronous communication that allows our support engineers to research your specific API context before responding. This ensures accurate answers for complex integration questions rather than real-time guesswork. Send your query to [email protected].
Our mission
We built VerbaCore to solve a specific problem for fintech teams: delivering high-volume customer notifications without breaking the bank or the API budget. Our goal is to provide a straightforward, reliable voice API that integrates seamlessly into your existing workflows, allowing you to scale communication efforts efficiently.
Help fintech teams scale
We focus on enabling banks to send thousands of audio notifications daily. With a rate limit of 60 requests per minute and support for splitting long texts, our API handles the volume you need.
Provide reliable voice APIs
Our system uses licensed LibriTTS-R recordings to ensure consistent quality. We process requests sequentially, ensuring predictable behavior for your customer alerts, and return audio files directly without storing them, keeping your data flow clean and efficient.
Keep pricing transparent
We charge $10 per million characters with no hidden fees or monthly plans. Failed requests are free, and you can top up with USDT on the TRON network (TRC-20) for immediate credit. This simplicity helps fintech teams predict costs accurately as they scale.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Your recent transaction has been successfully processed and verified by our secure banking network.
23 languages
Any voice speaks any of these languages.
