Guides
Billing models
Prepaid Credits vs Pay-as-You-Use — how they differ and which endpoints each unlocks.
Every organization uses one of two billing models. It determines which endpoints are available and whether you manage access tokens.
At a glance
| Prepaid Credits | Pay-as-You-Use | |
|---|---|---|
| Upfront payment | Required (purchase credits) | Not required |
| Token management | Required (generate / upgrade / renew) | Optional |
| Per-transcription charge | No — charged for token operations | Yes (per transcription) |
| External API endpoints | Available | Not available |
| Widget API endpoints | Available | Available |
| Best for | Multi-user management, predictable costs | Simple usage-based billing |
Prepaid Credits
You purchase credits upfront and spend them by issuing access tokens — one
per clinician or seat. Generating, upgrading, or renewing a token costs credits
based on its tier; individual transcriptions are then covered by that token.
This model unlocks the full External API (/external/access-tokens) for
programmatic token management.
Use it when you manage many users and want predictable, seat-based costs.
Pay-as-You-Use
No upfront purchase and no required token management — you're charged per transcription as you go. Access tokens are optional. Only the Widget API is available (the External API token-management endpoints are not).
Use it when you want the simplest possible usage-based billing.
Checking your balance
Signed-in dashboard users can read credit balance, usage logs, and transactions
via the Organization Dashboard endpoints (/organizations/credits/*) — see the
API Reference. Both billing models share the same widget
integration flow described in Widget integration.