Platform

Billing

One wallet, in the button in the top bar of every dashboard page, pays for everything: calls, the playground, and API usage under your keys. This page covers what is in it and how each service draws from it.

Your balance

Select the wallet button to open it. Balance is shown in USD; a coloured dot next to it reads the same state at a glance — green when healthy, amber at or below your low-balance line, red at zero, when calls and API requests are blocked until you add funds.

Screenshot: The wallet popover: balance, status dot, service credits summary, and the Add funds control.

Adding funds

Enter an amount and confirm; outside India this goes through a card payment and the balance updates immediately. In India, the same dialog offers UPI, card or net banking through Razorpay — the credit is still added in USD once the payment settles.

Minimum top-up

Your workspace has a minimum top-up amount, shown in the dialog and refused below at checkout if you try to enter less. It is set for your workspace on the platform side, not by you, and can be raised or lowered — the dialog always shows the figure currently in force, not a number fixed in the page itself.

Usage

How each service is billed

Every service is billed in the unit that matches how it is actually delivered to you:

Language modelper token
Text to speechper character generated
Transcriptionper second the stream is open
Telephony (platform number)per minute, rounded up to the carrier's own billing block

Transcription is billed by time rather than by the words recognised because it is a streaming connection: the provider charges for as long as it is listening, whether or not anyone is speaking in a given second, and so does Sonex. This applies identically to a phone call, the Speech to Text playground, and the public API.

The exact rate per unit is on your API Reference pricing endpoint and can differ by the specific model or voice you chose — gpt--family models and a premium cloned voice are not priced the same as the defaults.

Coupons and service credits

A service credit is a block of pre-paid usage for one service — for example, a fixed number of transcription seconds — issued to your workspace as a coupon. Whenever that service is billed, the credit is drawn down first and the wallet is only charged for whatever the credit does not cover; the wallet popover lists any credit you are currently holding, or says No service credits when you have none. This applies the same way whether the usage happened on a call, in the playground, or through the API.

What happens at a low or empty balance

At or below the low-balance line, the wallet's status dot turns amber as an early warning; nothing is blocked yet. At zero, new calls and API requests are refused until you add funds — a call already in progress is not cut off mid-conversation for this reason, but the next one will not start until the balance is positive again.

Next