Com tecnologia deChatGPTClaudeGoogle Gemini
Funciona comGoogle DriveDropboxOneDrive

Getting started

Billing and pricing

How metered billing works: $10 free credit, per-model rates, usage endpoints, and adding a payment method.

API billing is purely usage-based: there is no base fee, no per-seat charge, and no minimum. Each request is metered against the model it uses, your free credit absorbs cost first, and only usage beyond the credit is billed to your payment method.

Every account starts with $10 in free API credit, granted automatically. That is roughly 39 hours of audio on Whisper VoiceKit Best or 55 hours on Whisper VoiceKit Fast.

How billing works

  1. Every metered request records a usage event: the model used, the quantity in seconds, and the cost at that model's hourly rate, rounded up to the next cent.
  2. Remaining free credit is applied to each event first. While credit remains, nothing is billed.
  3. Once credit is exhausted, usage above it is charged to the payment method on file and invoiced through your metered subscription.
  4. Usage accumulates per calendar month; the period field in usage responses is formatted YYYYMM.

Pre-recorded models meter the duration of the source audio. Realtime and voice agent models meter session connection time, from WebSocket open to close.

For long jobs you can pass estimated_duration_sec when creating a transcript or session token. The API then checks the estimate against your remaining credit up front and rejects the request with 402 instead of letting it fail midway.

Metered rates

ModelModel idUnitRate
Whisper VoiceKit Bestwhisper-voicekit-bestAudio hour$0.252
Whisper VoiceKit Fastwhisper-voicekit-fastAudio hour$0.18
Whisper VoiceKit Realtime Prowhisper-voicekit-realtime-proSession hour$0.54
Whisper VoiceKit Realtimewhisper-voicekit-realtimeSession hour$0.18
Whisper VoiceKit Agentwhisper-voicekit-agentSession hour$5.40

Rates are also served live by GET /v2/pricing, which is the recommended source if you display pricing to your own users.

Free credit and running out

The $10 credit is granted once per account and never expires. Check your balance any time with GET /v2/credits; the credit_balance_cents field is what remains.

When the balance reaches zero and no payment method is on file, metered endpoints stop accepting new work and return 402 Payment Required with the error code v2_billing_required. Existing transcripts remain readable; only new metered requests are blocked. Add a payment method through checkout to continue.

Adding a payment method

Start a secure hosted checkout to attach a payment method and activate metered billing. The endpoint returns a URL; open it in a browser to complete setup. Afterwards, usage beyond your remaining credit is billed automatically.

POST/v2/billing/checkoutCreate a hosted checkout session for metered billing
bash
curl -X POST https://api.realtimevoicekit.com/v2/billing/checkout \
  -H "Authorization: Bearer rtvk_your_api_key"

# {"url": "https://checkout..."}  Open this URL to add a payment method.

You can also start checkout from the API dashboard. If a metered subscription is already active, the endpoint returns 409 with code already_api_subscribed.

Tracking credit and usage

Three read endpoints expose everything you need for cost dashboards and alerts:

GET/v2/creditsCredit balance and billing totals
GET/v2/usageItemized usage events, newest first (limit, offset)
GET/v2/usage/summaryCredits plus per-model rollups
bash
curl https://api.realtimevoicekit.com/v2/credits \
  -H "Authorization: Bearer rtvk_your_api_key"

All monetary fields are integers in USD cents. The GET /v2/credits response contains:

FieldMeaning
free_credit_centsFree credit granted to the account.
credit_balance_centsCredit remaining right now.
lifetime_retail_centsRetail value of all usage ever recorded.
lifetime_billable_centsUsage actually billed beyond credit, lifetime.
period_billable_centsBillable usage in the current calendar month.
periodCurrent billing period, formatted YYYYMM.
subscribedtrue when a metered billing subscription is active.

Each event from GET /v2/usage includes the sku (model id), unit_type, quantity in seconds, retail_cost_cents, credit_applied_cents, billable_cents, and created_at, so you can attribute every cent to a specific transcript or session.

Next steps

4.2de 21 avaliações