Frequently asked questions
What is the best TTS API for fintech?
Q: What is a TTS API for fintech? A: VerbaCore is a cloud TTS API designed for high-volume banking notifications. It offers reliable, scalable text-to-speech with simple integration. We provide 8 distinct voices and support for 23 languages, making it suitable for diverse customer bases requiring clear, synthetic audio delivery.
How does VerbaCore compare to others?
VerbaCore uses the same request shape as the OpenAI speech endpoint. It supports tts-1 and tts-1-hd models. Unlike many competitors, we accept USDT (TRC-20) for top-ups with no monthly plans. We do not offer SSML, voice cloning, or custom pronunciation lexicons.
Which voice is best for banking?
Q: Which voice is suitable for banking? A: Atlas (neutral, news) and Sage (calm, instructional) are well-suited for banking notifications. Atlas provides a clear, professional tone, while Sage offers a calm, instructional style. Both presets support all 23 languages, allowing you to maintain consistent communication across different regional banking contexts.
What is the cost per character?
Pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count as characters. Failed requests are free, with the charge returned in full. There are no monthly plans, seats, or minimum spend requirements.
Can I use OpenAI SDKs?
Yes, the official OpenAI SDKs work by changing the base_url to https://api.playq22.com/v1. Use your VerbaCore key for authentication. The request shape matches the OpenAI speech endpoint exactly, allowing for easy integration into existing fintech infrastructure without significant code changes.
What languages are supported?
We support 23 languages: Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice can speak any of these languages. Vietnamese and Thai are not supported.
Is there a free trial?
Yes, signing in with Google provides $0.50 of credit, valid for 7 days. This covers about 50,000 characters. Accounts created with email and password start without trial credit. The balance does not expire, and you can top up with USDT.
How fast is generation?
Generation is roughly real time on long texts, about 25 characters per second. Short phrases take a few seconds. Requests are processed sequentially, so under load, a request may wait in a queue. Splitting long texts ensures efficient audio delivery.
What formats are supported?
You can request audio in mp3, wav, opus, flac, or pcm formats. Use the response_format field in your JSON body. Each generated file carries an inaudible watermark marking it as synthetic speech. Input text is limited to 4096 characters per request.
Is 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 (time, characters, status) strictly for billing purposes.
What are the rate limits?
You are limited to 60 requests per minute per key. New accounts have a limit of 10 requests per minute before the first top-up. If you exceed this, requests may queue. You can issue a new key to reset limits if needed.
How do I integrate the API?
Send a POST request to https://api.playq22.com/v1/audio/speech. Include your Bearer token in the Authorization header. Provide model, input, voice, and response_format in the JSON body. Long texts should be split into 4096-character parts and joined after generation.
What is USDT payment?
We accept USDT on the TRON network (TRC-20) for top-ups. The minimum amount is $5. Credits are added automatically within minutes after transfer. We do not accept cards, PayPal, or subscriptions. There are no invoices or VAT charges.
Is there phone support?
No, there is no phone number or live chat. Support is provided via email only. You can reach us through the contact page. We do not offer an SLA, uptime guarantee, or enterprise contracts for priority support channels.
Criteria for fintech TTS APIs
Fintech teams managing thousands of daily customer interactions require a TTS API that handles volume without degradation. The solution must process high volumes of text consistently, ensuring that notification bursts do not cause bottlenecks or delays in critical communications.
Cost efficiency is paramount when generating audio at scale. Teams need transparent pricing based on character count, avoiding hidden fees or complex tiered structures that complicate budgeting for large-scale deployments across multiple regions and languages.
Scalability for high volume
High-volume fintech operations generate thousands of notifications daily. A robust API must handle concurrent requests, though requests are processed sequentially, ensuring that fraud alerts and transaction updates are delivered promptly to users.
- Handles concurrent requests for bulk notifications
- Maintains consistency during traffic spikes
- No artificial caps on daily volume
Cost efficiency per character
Pricing should be straightforward and predictable. With a rate of $0.01 per 1,000 characters, costs scale linearly with usage, making it easy to forecast expenses for large teams issuing frequent updates.
- $0.01 per 1,000 characters
- No monthly minimums or subscriptions
- Predictable scaling costs
API reliability and speed
Reliability ensures that critical financial messages reach customers. The API processes requests sequentially, which is vital for audit trails and user trust in financial communications.
- Sequential processing for order consistency
- Low latency for urgent alerts
- Consistent output quality
VerbaCore overview
VerbaCore is a cloud text-to-speech API built for fintech teams requiring reliable, scalable audio delivery. Our infrastructure handles high-volume customer notifications efficiently, converting text into clear speech with minimal latency. We prioritize straightforward integration, allowing your engineering team to adopt our service without rewriting existing workflows or adopting proprietary SDKs, as we do not provide our own SDK.
$0.01 per 1,000 characters
Your costs scale directly with usage. We charge $10 per million characters, which equals $0.01 per 1,000 characters. Failed requests are free, so you only pay for successful synthesis. There are no monthly plans, seats, or minimum spend requirements.
OpenAI SDK compatibility
Our API follows the same request shape as the OpenAI speech endpoint. You can use the official OpenAI SDKs by simply changing the base URL to https://api.playq22.com/v1. This allows you to integrate our TTS capabilities into your existing codebase with minimal configuration changes.
USDT payment via TRON
We accept USDT on the TRON network (TRC-20) for top-ups. The minimum deposit is $5, and credits are added automatically within minutes. This method avoids credit card processing fees and allows for instant funding without waiting for invoice approvals or subscription cycles.
Voice quality and options
VerbaCore offers eight distinct voice presets tailored for fintech communication, ensuring your customer notifications sound professional and clear. Each voice carries a specific tonal character, from the warm, clear narration of Aria to the neutral, news-style delivery of Atlas, allowing you to match the audio to the context of the alert or update.
These voices are built on licensed recordings from the LibriTTS-R dataset, derived from public-domain audiobook readings on LibriVox. This foundation ensures consistent audio quality across all 23 supported languages, regardless of your customer's region, providing reliable clarity for transaction alerts and account updates.
8 presets for different tones
Select from four female and four male voices to suit your brand's voice. Options range from the bright, upbeat Nova for promotional messages to the calm, instructional Sage for guided walkthroughs. The deep, documentary-style Orion suits detailed explanations, while the energetic Felix works well for time-sensitive promo notifications.
Every voice supports all 23 languages, allowing consistent audio quality regardless of your customer's region. This ensures that whether you are sending a fraud alert in Spanish or a transaction confirmation in Japanese, the tone remains professional and intelligible.
- Aria: Warm, clear narrator
- Nova: Bright, upbeat
- Luna: Soft, storytelling
- Sage: Calm, instructional
- Felix: Energetic, promo
- Milo: Friendly, conversational
- Atlas: Neutral, news
- Orion: Deep, documentary
Licensed recordings from LibriVox
Our voices are synthesized from licensed recordings sourced from LibriTTS-R, which uses public-domain audiobook readings from LibriVox. This approach provides a natural, human-like quality without the variability of custom voice cloning services, ensuring stability in your audio output for high-volume fintech communications.
Inaudible watermark in audio
Every generated audio file includes an inaudible watermark that marks the content as synthetic speech. This feature helps identify automated notifications in customer support scenarios, adding a layer of transparency for your users without affecting the listening experience.
Language support
VerbaCore supports 23 languages, including English, Spanish, German, French, Arabic, Chinese, Japanese, and Hindi. Any voice can speak any of these languages, ensuring consistent quality across your global customer base.
This broad coverage allows fintech teams to deploy localized notifications without managing multiple voice models or language-specific integrations.
23 languages available
We support Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. All voices are capable of speaking all supported languages with native-like clarity.
Automatic detection
If you do not specify a language, the API guesses it from the script. Latin script text defaults to English, which works well for English notifications. For other Latin-script languages, explicit setting is recommended.
Manual language setting
You can explicitly set the language field using an ISO code to ensure accurate pronunciation. This is critical for non-English Latin-script text or when mixing languages. Unsupported languages include Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, and Bengali.
- Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali are not supported.
Technical integration
Integration is straightforward: send a JSON payload to the POST /v1/audio/speech endpoint. The request shape mirrors OpenAI’s standard, allowing fintech teams to leverage existing OpenAI SDKs by simply adjusting the base_url to https://api.playq22.com/v1. This ensures immediate compatibility with established development workflows, though we do not provide our own SDK.
Authentication is handled via a single active Bearer token passed in the Authorization header. You can regenerate this key at any time, with the old token ceasing instantly. This simplifies credential rotation for security-conscious banking environments without leaving dangling active keys in production systems.
JSON request body
Each request accepts up to 4096 characters of text. For longer notifications, split the input and join the resulting audio files. The model field accepts either tts-1 or tts-1-hd, using the same engine and price point. Speed can be adjusted between 0.25 and 4.0 to match the urgency of the message.
The optional language field accepts ISO codes. If omitted, the system guesses the language from the script, defaulting to English for Latin text. Explicitly setting the language ensures accuracy for non-English notifications, preventing mispronunciation in multilingual customer bases.
- Model:
tts-1ortts-1-hd - Max input: 4096 characters
- Speed range: 0.25–4.0
- Auth:
Bearer tts-...
Multiple audio formats
Generate audio in mp3, wav, opus, flac, or pcm formats. This flexibility allows fintech apps to choose the optimal balance between quality and bandwidth for various delivery channels, whether pushing notifications to mobile devices or playing through IVR systems.
All generated files include an inaudible watermark identifying the speech as synthetic. This aids in compliance and transparency, as every generated file carries an inaudible watermark that marks it as synthetic speech.
Rate limits and queueing
The API allows 60 requests per minute per key, with a lower limit of 10 requests per minute before the first top-up. Requests are processed sequentially, meaning heavy loads may result in queueing delays. Typical generation speed is roughly real-time (25 characters per second), but short phrases may take a few seconds due to processing overhead.
Failed requests incur no charge, ensuring cost efficiency during peak usage or temporary service hiccups. This reliability is crucial for time-sensitive financial alerts where failed deliveries might otherwise go unnoticed.
Pricing comparison
Unlike traditional TTS providers that lock you into rigid monthly plans or per-seat licenses, VerbaCore charges strictly by volume. Your cost is exactly $0.01 per 1,000 characters, regardless of team size. This model eliminates wasted spend on unused capacity, making it ideal for fintech teams with fluctuating notification volumes.
No monthly plans
There are no subscriptions, no seats, and no minimum spend. You only pay for the characters you actually process. This flexibility allows banks to scale audio generation up or down without contractual penalties or over-provisioning costs.
Pay only for usage
Failed requests are free; if synthesis fails, the charge is returned in full. You pay $10 per 1 million characters, with spaces and punctuation counting toward the total. This transparent unit pricing ensures you never pay for wasted compute.
Free trial for testing
Sign in with Google to receive $0.50 in trial credit, valid for 7 days. This provides about 50,000 characters to test integration. Accounts created with email and password start without trial credit, ensuring fair access for all users.
Data privacy features
Your input text is used exclusively for immediate audio synthesis and is never retained for model training. This ensures that sensitive customer data or internal communications remain private and are not leveraged to improve the underlying engine.
Generated audio files are returned directly in the response and are not stored on our servers. Once delivered to your application, the audio is not kept by VerbaCore, minimizing data retention risks for high-volume fintech notifications.
Input not used for training
We do not use your input text for training purposes. The text you send via the API is processed solely to generate the requested audio file and is discarded after that immediate use. This guarantees that your specific datasets, whether customer names or transaction details, remain yours and are not ingested into the voice models.
Audio not stored
The generated audio files are returned in the HTTP response and are not stored by VerbaCore. This means we do not hold copies of your synthesized speech, reducing the attack surface for data breaches and simplifying compliance with data retention policies common in banking environments.
Metadata for billing
We retain only the necessary request metadata—such as timestamp, character count, and status—to accurately calculate your usage and billing. This limited data collection ensures transparency in your invoices without storing the actual content of your communications.

Use cases in fintech
VerbaCore’s API enables fintech teams to convert critical text messages into clear audio notifications efficiently. With support for 23 languages and a simple JSON request structure, integrating voice into your existing infrastructure requires minimal code changes.
Fraud alerts
Instantly convert high-priority text alerts into voice calls to notify customers of unusual activity. The API processes requests sequentially, leveraging voices like Atlas for a neutral, authoritative tone.
- Convert JSON alert payloads to audio in seconds
- Use neutral voices for clear, urgent communication
- Support multiple languages for global fraud teams
Transaction notifications
Generate audio confirmations for payments, transfers, or purchases directly from your transaction logs. Since spaces count as characters, precise character limits help manage costs while maintaining message clarity for your users.
- Support for up to 4,096 characters per request
- Cost-effective at $0.01 per 1,000 characters
- Choose upbeat voices like Nova for positive confirmations
Account updates
Automate voice notifications for password changes, KYC status updates, or security settings. The system handles text splitting for longer updates, ensuring no part of the message is cut off while maintaining audio continuity.
- Automatic text splitting for updates over 4,096 characters
- Reliable queue processing handles high-volume bursts
- Clear narration using voices like Sage or Luna
Performance metrics
VerbaCore processes text-to-speech requests with a typical generation speed of roughly 25 characters per second, delivering audio that matches real-time speech patterns for long texts. Short phrases may take a few seconds to synthesize, ensuring consistent quality without unnecessary delay.
Real-time generation
The API generates audio files at a pace that aligns with natural speech duration. While short commands synthesize quickly, longer notifications benefit from this consistent throughput, allowing fintech teams to scale notification volumes without significant latency bottlenecks.
Queue processing
Requests are processed sequentially, meaning that under heavy load, new requests may wait in a queue before synthesis begins. This ensures stable performance but requires teams to account for potential delays during peak notification periods.
60 requests per minute
Each API key is limited to 60 requests per minute, with a lower limit of 10 requests per minute before the first top-up. This rate limit supports steady high-volume workflows while preventing sudden spikes from overwhelming the system.
Support and limits
VerbaCore offers straightforward support and transparent operational limits designed for fintech teams who prioritize clear expectations. We provide direct assistance without the overhead of complex support tiers, ensuring your integration questions are handled efficiently by our team.
Understanding the infrastructure constraints helps you design robust notification pipelines. Our service operates without formal commitments, meaning you should build your own retry logic and monitoring around our public rate limits and processing queues.
Email support only
All customer inquiries are handled exclusively via email. We do not maintain a phone number or offer live chat for immediate assistance. This approach allows our support engineers to provide detailed, documented responses to your technical or billing questions without interruption.
Email support ensures that every interaction is logged and searchable, which is particularly useful when troubleshooting integration issues or verifying account details for high-volume fintech notifications.
No SLA or uptime guarantee
As an independent API, we do not publish a formal Service Level Agreement (SLA) or offer an uptime guarantee. While we strive for consistent availability, you should design your applications to handle transient failures gracefully.
Requests are processed sequentially, so during periods of high load, a request may wait in a queue. This means latency can vary, and you should account for potential delays in time-sensitive fraud alerts or transaction notifications.
No certifications
We do not currently hold external certifications such as SOC 2, HIPAA, or GDPR certificates. Our data practices are defined by our privacy policy rather than third-party audits.
Input text is used only to produce audio and is not used for training. Generated audio is returned in the response and not stored. Request metadata is kept solely for billing purposes, ensuring a minimal data footprint for your customers.
How to get started
To begin using VerbaCore, create an account directly on our /get-api-key/ page. You can sign up instantly using your Google account, which provides immediate access to your unique API credentials without waiting for email verification.
Once registered, your API key is displayed immediately alongside your current balance and usage statistics. You can start sending requests right away using the provided curl example or by configuring your existing OpenAI SDK clients to point to our API base URL.
Sign up with Google
Creating your account is immediate and requires no credit card. Simply click the Google sign-in button on the registration page to link your identity to your new VerbaCore account.
Get API key instantly
Your API key appears on the dashboard right after sign-up. You can copy this key to use in your Authorization: Bearer headers. If needed, you can issue a new key at any time, which instantly invalidates the previous one.
Start with free trial
Google sign-ups receive a $0.50 credit, valid for 7 days. This covers approximately 50,000 characters, allowing you to test voice quality and integration speed before committing to USDT top-ups.
Why choose VerbaCore
VerbaCore offers a transparent, usage-based pricing structure tailored for high-volume fintech operations. At $0.01 per 1,000 characters, you pay only for what you use, with no monthly plans, seats, or minimum spend. Failed requests are free, ensuring you never pay for errors.
Simple pricing model
Our pricing scales linearly with your volume. You can top up with USDT on TRON, with no invoices or VAT complications. Balance never expires, allowing you to manage cash flow efficiently without worrying about subscription renewals or unused credits.
Reliable API
The API processes requests sequentially, handling queues under load while maintaining consistent quality. With a rate limit of 60 requests per minute per key, you can plan your burst traffic effectively. The endpoint mirrors the OpenAI speech API, allowing easy integration with existing SDKs.
- 60 requests per minute per key
- OpenAI SDK compatible
- Sequential processing ensures stability
Built for fintech teams
Designed for teams needing reliable, scalable TTS for customer notifications. We support 23 languages and 8 distinct voices, ensuring your alerts sound professional and clear. Input text is not used for training, and generated audio is not stored, supporting your data privacy requirements.
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.
