Skip to main content

Account, registration and daily credits

How to join WebVoice, accept policies, and start using credits securely.

Creating your account

You can access WebVoice by registering with your email address and a password, or by using passwordless login: we send a one-time code to your inbox and you confirm it from the same browser session. Both flows are designed to be quick and work well on desktop and mobile.

After the first successful login, your profile stores preferences such as interface language, so the experience stays consistent when you return — even on a new device, once you authenticate again.

Terms, privacy and AI policy

Before using voice, chat or API features, you may be asked to accept our Terms of Service, Privacy Policy and AI Policy. These documents explain how we process data, what the services are for, and how artificial intelligence is used responsibly. You can read them at any time from the footer links on every public page.

Accepting the AI policy where required ensures that you are informed about automated processing related to speech, transcription and assistants — in line with transparency rules for users in the European Union and beyond.

Free daily credits

WebVoice uses a credit-based system: text-to-speech, speech-to-text, translation, chat and other features consume credits according to clear rules (for example, audio duration or text length). Eligible accounts receive a daily allocation of free credits so you can try the platform regularly without always purchasing a pack.

You can top up with one-off purchases or subscriptions from the billing area once logged in. Usage and balance appear in your dashboard so you always know where you stand.

Voice memos (free text)

Text-only voice memos and memo transcriptions are free and unlimited in count. Each memo can store up to 10000 characters of text (web app and API). Audio recording and speech-to-text transcription still use credits where applicable.

API keys (after login)

From the API section of your account you can create and revoke API keys, read the full REST documentation, and integrate TTS, STT, translation and other endpoints into your own apps. Keys are tied to your user and share the same credit balance as the web interface.

Summary

  • Email + password or email code login
  • Legal and AI disclosures available before and after sign-up
  • Daily free credits plus optional purchases
  • Free voice memo text (up to 10000 characters per memo)
  • One credit pool for web and API

Trusted for production voice workloads

Inside the product — app screenshots, workflow, and reserved logo slots on the main site.

Product teams, agencies, and developers use WebVoice for TTS, STT, chat, and API-first integrations — from prototypes to customer-facing apps.

SaaS & product
Agencies
Education
Internal tools
50K+

Hours of audio synthesized & transcribed monthly (illustrative range)

30+

Neural voices and locales in the catalogue (varies by deployment)

REST

Same credit wallet for browser app and documented HTTP API

Figures are indicative and depend on traffic and configuration.

“We shipped read-aloud and STT in one sprint — the API matched what we tested in the UI.”

“Credits per feature make finance happy — we can forecast TTS vs chat separately.”

“Low-latency Groq routes for chat let us keep UX snappy without a separate vendor.”

Quotes represent typical feedback patterns; not attributed to specific customers.

Frequently asked questions

Credits are a single balance for the web app and API. They pay for text-to-speech, speech-to-text, translation, chat turns, image generation (where enabled), and other metered features. Daily free credits renew at login; purchased credits do not expire.

You can register and use daily free credits without a subscription. Buying credits or a plan is optional when you need higher volume.

Yes. API keys are tied to your account and draw from the same credit wallet as the browser app, so you can prototype in the UI and ship server-side calls with one pool of credits.

Safeguard-class models are tuned for stronger refusals and policy alignment. They are a good default for customer-facing or regulated workflows. Other models may trade cost or latency for different strengths — see the model list for credits per request.

Processing depends on the feature: some workloads run on our infrastructure and third-party providers you configure (e.g. Groq, MiniMax). Read the privacy and AI policy pages for retention and provider details.

Ready to try WebVoice?

Get Started API documentation