Account and billing

Track your credit usage

Read the credit meter in the sidebar and on the Subscription page, open Credits History to see what each job cost and refunded, and check how much of the plan's agents, storage and API keys the workspace has used.

Credits are spent by every speech job and every agent turn, so the balance moves all day. When you finish this page you will know the three places the portal shows the balance and what each one counts, how to read the Credits History list to see what one job cost and whether it was refunded, and where the plan's other limits, agents, storage and API keys, are reported.

What you need

  • A workspace. The sidebar meter shows your plan credits.
  • The Owner role for the live balance and Credits History.

Steps

Step 1: Read the meter in the sidebar

The plan card at the bottom of the sidebar names your plan and reads used/total Used with a bar. It counts plan credits only. When 15% or less of the plan credits remain, the figure turns red and a Low flag appears; the collapsed sidebar shows a dot instead. The user menu repeats it as Credits remaining with remaining / total.

The meter refreshes after each speech job or agent conversation and when you open the Subscription page.

Step 2: Read the balance on the Subscription page

Open the user menu and choose Subscription & billing. Under the plan name:

Line on the card What it counts
The large figure Plan credits plus extra credits: everything you can spend
Plan credits (Trial credits on a trial) The plan credits left, with a bar against this month's grant
Includes N rolled over The part of the plan credits carried over from earlier months
Rolls over up to N The most plan credits the workspace can hold: three times the monthly allowance
Next credits with a date When the next monthly allowance arrives, also on yearly billing
Extra credits The extra credits left, then one line per top-up: N never expire, or N expire with the date. A grant from EchoNova carries a Granted chip

The large figure is the total the portal can still spend. The period is the one between the start of the subscription period and the Next billing date shown above; a trial has no end date. What each balance is and how it resets is on Credits, top-ups and rollover.

The figures are live for the workspace Owner.

Step 3: Open Credits History

Open /payment-history in the portal. The page is headed Payment History and titled Credits History: Every credit consumed or refunded across your services. Rows are newest first, 20 per page, with Previous and Next and a line reading Page 1 of 3 (48 records).

Column What it shows
Date When the charge or refund was recorded
Service Which service the row belongs to, such as Text to Speech, Speech to Text, Voice agent or Chat agent
Action Consume or Refund
Credits The credits moved, as −N for a charge and +N for a refund, in whole credits. A non-zero amount under 1 reads < 1
Balance after Plan credits plus extra credits after this row
Description What the row was for; see the table below
Details On a row with priced detail: opens the service, the quantity and the rate, or for AI usage the model, the tokens, Provider cost, EchoNova fee, Billable and Paid from with the credits each source paid at its rate. A row from before the credit change reads Charged in the old credit unit, before credits changed. Old and new amounts do not compare.

The filters above the table offer All Actions, Consume and Refund, and a service filter that includes Voice agent and Chat agent. An empty list reads No credit activity yet.

Step 4: Read a row

The Description names the service and the size of the job.

Description Row for
TTS sync: N characters, TTS generation: N characters A Text to Speech generation, from the playground and the immediate API call in the first form, from the queued API call in the second. N is the characters it was priced on, spaces included
STT sync: ~Ns, STT transcription: ~Ns A Speech to Text transcription, from the playground and the immediate API call in the first form, from the queued API call in the second; N is the seconds of audio it was priced on
Sound cleaning: ~Ns A cleanup; N is the seconds of audio
Sync TTS refund:, TTS refund:, Sync STT refund:, STT refund:, Sound cleaning refund:, each followed by the reason The charge given back when that job failed; the text names why
TTS refund: job timed out, STT refund: job timed out A queued job that never finished and was refunded
Refund due to job creation failure A job that could not be created after its charge was taken
Voice agent session, Chat agent session One row for a whole agent conversation, with a running total that grows as its turns are charged

A refund row follows its charge row and carries the same number, so a failed job leaves the balance where it was. The rates behind the numbers are on Credits.

Agent conversations are charged for their connected time and their AI usage against the same balance. Each conversation appears as a single row, Voice agent session or Chat agent session, whose amount is the running total of its turns. Read what each turn cost in the conversation itself, as described on What a turn costs.

Step 5: Check the plan's other limits

Agents, knowledge storage and API keys are capped by the plan, and each cap is reported on the page that uses it:

Limit Where the portal reports it
Agents The Agents page, when the workspace is at or over the cap
Knowledge storage The Agents page and the knowledge library, when the workspace is over the cap
API keys The Developers page, when the workspace is over the cap

The caps themselves are the lines on the plan card, such as 3 agents or Unlimited agents. A downgrade dialog lists every cap the smaller plan would put you over; see Choose or change your plan.

Worked example

You are on Starter, with 600,000 plan credits. You generate a 41-character sentence in the playground, transcribe a 12-minute file, and your transcription of a corrupt file fails. You then run a short voice session with an agent. Credits History now reads, newest first:

Date Action Credits Balance after Description
today 10:55 Consume −6,040 592,719 Voice agent session
today 10:42 Refund +1,200 598,759 Sync STT refund: followed by the failure's reason
today 10:41 Consume −1,200 597,559 STT sync: ~720s
today 10:30 Consume −1,200 598,759 STT sync: ~720s
today 10:12 Consume −41 599,959 TTS sync: 41 characters

The Subscription page's Credit balance reads 592,719. The voice session row opens with Details: 5,625 credits for 2 minutes 15 seconds connected and 415 for the AI usage of its turns. The refund row has the same amount as its charge, so the failed file cost nothing.

What happens next

A charge appears in Credits History the moment a job is accepted, and its refund the moment the job fails. The sidebar and the user menu refresh after each speech job or agent conversation and when you open the Subscription page; the Subscription page itself loads the live figures every time you open it.

Limits

Limit Value Applies to
Rows per page 20 Credits History
Order Newest first Credits History
Filter All Actions, Consume, Refund, and a service filter Credits History
Rows listed Text to Speech, Speech to Text and Sound Cleaning charges and refunds, and one row per voice or chat agent session Credits History
Sidebar and user menu Plan credits only Every workspace
Low flag 15% or less of the plan credits remaining Sidebar
Live balance and Credits History Owner Every workspace

Troubleshooting

Failed to load credit history.

The list could not be fetched; click Retry. When the page shows You lack the required permission(s): billing.view instead, your role cannot view billing; ask the workspace Owner.

Balance after does not match the sidebar

The sidebar counts plan credits only; Balance after adds the extra credits. Compare it with the large figure on the Credit balance card on the Subscription page.

A job I ran is not in Credits History

An agent conversation is one Voice agent session or Chat agent session row, not one row per turn. A playground job that was refused before it started, for example for an unsupported file, was never charged and has no row.

FAQ

Which balance do the playground pages check before a job?

Your Credit balance. A job whose price is larger than it is refused with Insufficient subscription balance and leaves no row.

Can I export Credits History?

The page offers no export. Page through it with Next; each page holds 20 rows.

Does Credits History show who ran a job?

No. Rows carry the date, the action, the credits, the balance and the description only.

How do I see usage by service?

The Description names the service on every row. Use the service filter, for example Voice agent or Chat agent, or read the descriptions.