Balance and billing

The unit is g. 1 g is one minute of audio at tariff ×1.

What a recording costs

The recording's length in minutes multiplied by the tariff of the paid options that are on:

Options	Tariff	One minute of audio
no paid options	×1	1 g
Emotions	×2	2 g
Personal data	×1.2	1.2 g
both	×2.2	2.2 g

The charge happens on completion, once the recording is recognised: 4 minutes 43 seconds with every option is 10.37 g. While a job is queued or running its estimate is held back from the available balance, so a burst of uploads cannot overdraw it. A failed job charges nothing.

Beta period

While the beta lasts there is no money behind the balance. Every midnight Tashkent time each account is topped up to its daily target, 240 g by default, that is four hours of audio at tariff ×1. The top-up is the difference to the target: spend 37 g during the day and +37 g arrives at night. An account already at the target gets no top-up and nothing appears in its history.

The target can be changed for a particular account by arrangement.

Where to look

• In the cabinet: the balance under your name in the left menu, and the "Billing" page with the history of top-ups and charges.
• In the API: GET /v1/usage returns balance_g, in_flight_g, available_g and topup_target_g; GET /v1/billing returns the balance and the history:

{"unit": "g", "balance_g": 203.63,
 "transactions": [
   {"kind": "charge", "amount_g": -10.37, "balance_after_g": 203.63, "job_id": "41f79b78-…", "seconds": 282.7, "factor": 2.2, "note": "", "created_at": "…"},
   {"kind": "topup", "amount_g": 214, "balance_after_g": 240, "job_id": null, "note": "beta period", "created_at": "…"}
 ]}

When the balance does not cover a recording, POST /v1/jobs answers 429 insufficient_balance with a hint saying what is there, what is needed and when the top-up comes.