Talqing charges one platform fee, debited from a prepaid USD credit balance per workspace. Provider spend (OpenAI, Deepgram, ElevenLabs, Anam…) is billed to your own accounts on your own provider keys; Talqing reports it per call and never collects it.

The platform fee

  • Minutes are the call’s duration, billed to the second. No per-call minimum, connection fee or subscription.
  • An answered message is one the agent finished replying to. A message superseded before it was answered, or whose turn failed, is free. Time a chat sits open is not billed.

The fee is waived on failed calls

A call ending with one of these close reasons is not charged the platform fee (your provider spend on it still stands): error, stale, job_shutdown, job crashed, orphaned, unknown, avatar_start_failed, invalid_dispatch_metadata, missing_dispatch_metadata, unknown_tenant, missing_published_definition, rejected, insufficient_credits, and any reason ending in _failed.
Every other call is charged, including a caller who hangs up after two seconds, a call answered by voicemail, and a call with no close reason at all. See close reasons.

Reading the balance

Any member can read it.

The signup credit

The workspace created at your first sign-in gets $10 once. A workspace you create later starts at $0.

Buying credit

ADMIN only. Credit comes in fixed packs: usd_20, usd_50, usd_100, usd_200, usd_500, usd_1000. The id is the amount credited, regardless of currency conversion, tax or processor fees. In the dashboard: Organization → Settings → Billing.
Open checkout_url in a browser; card details never touch Talqing. After paying, read the balance again: that read applies a confirmed payment, and topup_status shows whether the processor has confirmed it yet.

Running out

The only check is balance > 0. There is no reservation and no spend cap. The 402 uses the standard error envelope:
A call already running is never cut off, and an active chat is not re-checked on every message. The balance can therefore go slightly negative; the next top-up pays that off first.

The ledger

GET /v1/billing/credits/ledger lists every balance movement, newest first, each with amount, balance_after, and session_id or topup_id. A usage row also carries its session’s channel (voice, video or text) and conversation_id.

Estimating cost per minute

Provider spend is usually far larger than the platform fee, so estimate it before running at volume.
  • Dashboard: the agent editor’s right rail shows a live per-minute estimate for the draft, split into STT, LLM, TTS (or Realtime), Avatar and Platform.
  • API: GET /v1/catalog returns each model’s provider rates plus the assumed usage behind an estimate: cost_estimate_usage_per_minute (per spoken minute: 800 LLM input and 250 output tokens, 900 TTS characters, 60 s of streaming or 20 s of batch STT) and cost_estimate_usage_per_text_message (800 input and 250 output tokens per reply). Multiply the rates by those quantities and add platform_fee_per_minute or platform_fee_per_message.
These are estimates. The bill comes from what each provider metered on the real call; see costs.

Next

Provider keys

The other half of the bill.

Costs

What one call actually cost, line by line.