Skip to content
Documentation

RTC plans and billing

CHAMPREP RTC is a subscription add-on. You buy it in CHAMPREP Billing on top of any CHAMPREP plan, Free included. The workspace that pays (a personal account, a team or an organization) owns the subscription, and every project and API key of that workspace uses it.

RTC never handles card data. Every purchase, card and invoice is in CHAMPREP Billing.

RTC is available when billing finds one of these for the paying workspace:

  • an RTC subscription tier;
  • the free trial;
  • the small allowance included in a paid CHAMPREP plan.

A pack alone does not open RTC. Without any of them, RTC answers RTC_SUBSCRIPTION_REQUIRED with the offers that fix it.

The free trial can be used once per account, once per workspace and once per card. A workspace that already had a trial cannot start another one from a different account, and a card that already started a trial cannot start another one in a different workspace.

AllowanceTrial
Length30 days
Participant-minutes1,000
Recording minutes60
Recording storage1 GB-month
Downloads2 GB
Room sizeUp to 4 participants
Rooms at once2
Projects1
Webhook endpoints1
Recordings kept7 days

The paying workspace needs a saved card before the trial starts. Nothing is charged. Start it from the RTC console or with POST /v1/subscription/trial.

Paid CHAMPREP plans (Basic, Plus, Team and Enterprise) include a small RTC allowance: about 300 participant-minutes a month, 1 project, rooms of up to 4 participants and 2 rooms at once. Recording is not included. The Free plan includes no RTC allowance; buy a tier or start the trial.

TierPriceWhat it includes
Starter$29 a monthReal-time video and audio for your app: 3 projects, rooms of up to 25, 10 rooms at once, 10,000 participant-minutes, 500 recording minutes, 25 GB-months of recording storage, 50 GB of downloads and 3 webhook endpoints a month. Recordings kept 30 days. Overage on packs.
Growth$99 a monthFor growing apps: 10 projects, rooms of up to 32, 50 rooms at once, 50,000 participant-minutes, 3,000 recording minutes, 150 GB-months of recording storage, 300 GB of downloads, 10 webhook endpoints, delivery to your own storage and 1,000 transcription minutes. Recordings kept 90 days. Overage on packs or pay-as-you-go.
Business$399 a monthFor production scale: 50 projects, rooms of up to 32, 250 rooms at once, 250,000 participant-minutes, 15,000 recording minutes, 1 TB-month of recording storage, 2 TB of downloads, 25 webhook endpoints, delivery to your own storage and 10,000 transcription minutes. Recordings kept 365 days. Overage on packs or pay-as-you-go.
EnterpriseBy contractContact CHAMPREP

Allowances reset each billing period. CHAMPREP Billing shows the current prices and taxes before you buy. Delivery to your own storage is described in Bring your own storage.

AllowanceUnit
Participant-minutesOne per started minute per connected participant
Recording minutesOne per started minute per recording
Transcription minutesOne per started minute of the longer of the recording’s length and its total speech (transcription); failed runs are free
Recording storageGB-months, sampled once a day. A GB kept for one day counts as 1/days-in-month of a GB-month. Recordings in Trash still count until you delete them from Trash or they are auto-deleted after 30 days.
DownloadsGB of recording downloads plus GB delivered to your own storage
Rooms at onceRooms open at the same time. A slot is released when the room ends.

Packs are one-time top-ups. They do not reset at the end of the month.

PackAdds
Participant-minutes10,000 or 100,000 participant-minutes
Recording minutes1,000 recording minutes
Recording storage100 GB-months
Transcription minutes1,000 transcription minutes ($15)
Downloads100 GB

When an allowance is used up, the refusal lists the packs for that allowance in its offers. A pack adds to an RTC subscription; it does not open RTC on its own.

Transcripts of recordings use the rtc-transcription-minutes allowance.

Transcription minutes
Growth1,000 a month
Business10,000 a month
Starter, the trial and the allowance included with paid CHAMPREP plansNone; Starter can buy packs
Pack1,000 minutes for $15, any tier
Pay-as-you-go (Growth and Business)$0.018 a minute past the allowance and packs
  • One minute is counted per started minute of the longer of the recording’s length and the total speech across participants, so a normal meeting is billed for its length.
  • A failed or cancelled transcript is free.
  • The recording’s length is reserved before the transcript is queued. When the allowance cannot cover it, the request fails free and its transcript.failed event carries RTC_ALLOWANCE_EXHAUSTED and the offers.

Live captions are not sold yet.

  • A workspace has one RTC tier at a time.
  • An upgrade applies at once. Billing charges the prorated difference for the rest of the period.
  • A downgrade takes effect at the end of the current billing period. There is no refund or credit for the remaining period.

Change the tier in CHAMPREP Billing.

GET /v1/subscription returns the paying workspace’s RTC subscription. It works without a subscription, so the console can show what to buy. It needs a signed-in console session of the workspace; project API keys are refused. Your application learns about allowances from the refusal codes and offers below, and from the quota.warning and quota.exhausted webhooks.

FieldMeaning
sourceWhat opens RTC: subscription, trial, migration (a complimentary grant), plan (a paid plan’s allowance) or none
accessallowed, with a reasonCode and, when RTC is refused, a reason
tierThe current tier (addonCode, displayName, priceMinor, currency, interval), or null
trialstate (available, active, used or disabled), endsAt, days and requiresPaymentMethod
periodThe current billing period, start and end
featuresEvery allowance by feature code: kind, enabled, limit, used, remaining, percentage (and unlimited where it applies)
entitlementsA compact view: flags (switches on or off) and features (numbers)
offersWhat you can buy or start now (offers)
quotaWarningPercentsThe percentages that send quota.warning
manageUrlWhere the owner manages the subscription in CHAMPREP Billing
hasOrganizationWhether the RTC organization is created yet

The answer is not cached (Cache-Control: no-store). It may also list feature codes that no RTC plan includes yet; they read as not enabled.

Feature codeAllowance
max-projectsProjects
max-participantsParticipants per room
rtc-max-concurrent-roomsRooms open at once
participant-minutesParticipant-minutes each period
rtc-recordingRecording on or off
rtc-composite-recordingComposite recording on or off
rtc-recording-minutesRecording minutes each period
recording-storage-gb-monthRecording storage, in GB-months
egress-gbDownloads and deliveries, in GB
rtc-recording-retention-daysDays a recording is kept
rtc-byo-storageDelivery to your own storage on or off
rtc-webhook-endpointsWebhook endpoints
rtc-transcription-minutesTranscription minutes each period

POST /v1/subscription/trial starts the free trial. It needs a signed-in console session of the workspace owner; API keys are refused. Send an empty JSON body.

A successful answer is 201:

{ "state": "active", "startedAt": "2026-11-08T12:00:00.000Z", "endsAt": "2026-12-08T12:00:00.000Z" }
HTTPCodeMeaning
402PAYMENT_METHOD_REQUIREDAdd a card to the paying workspace first (see offers)
409TRIAL_ALREADY_USEDThis account, this workspace or this card already used a trial
403TRIAL_NOT_ALLOWEDThis account cannot start the trial
409TRIAL_UNAVAILABLEThe trial is not available
409ALREADY_SUBSCRIBEDThe workspace already has an RTC subscription, trial or grant

When the subscription stops a request, RTC answers with a stable code and, where something fixes it, offers. Refusals about one allowance or feature also carry feature.

HTTPCodeWhenOffers
402RTC_SUBSCRIPTION_REQUIREDNo subscription, trial or included allowanceTrial, subscribe
402RTC_PAYMENT_REQUIREDAn unpaid invoiceNone; pay it in CHAMPREP Billing
403RTC_ACCESS_DENIEDAn organization, team or platform policyNone
402RTC_ALLOWANCE_EXHAUSTEDRecording or transcription minutes, storage or downloads are used up (feature says which)Packs for that allowance, upgrades
403RTC_FEATURE_NOT_IN_PLANThe plan does not include the feature, for example recording or transcriptionUpgrades, subscribe, trial
403RTC_PLAN_LIMITRoom size or rooms open at onceUpgrades
{
"error": "Your RTC allowance for rtc-recording-minutes is used up",
"code": "RTC_ALLOWANCE_EXHAUSTED",
"feature": "rtc-recording-minutes",
"offers": [
{ "kind": "pack", "addonCode": "rtc-recording-minutes-1k", "label": "1,000 RTC recording minutes", "featureCode": "rtc-recording-minutes" }
]
}

With RTC-Version: 2026-11-01, offers and feature are inside the structured error object. See errors.

Each offer has a kind and a label, and may carry more:

FieldMeaning
kindtrial, subscribe, upgrade, pack or payment_method
label, descriptionText you can show
addonCodeThe tier or pack, for example rtc-growth
priceMinor, currency, intervalThe price in minor units, its currency, and month, year or none
featureCodeThe allowance a pack tops up
urlA CHAMPREP Billing page: checkout, packs or add a card
actionstart_trial: call POST /v1/subscription/trial

Send the owner to url, or start the trial when action is start_trial. Never collect card details in your own application.

RTC sends two events to your webhook endpoints:

  • quota.warning when an allowance passes a warning percentage (80 % unless CHAMPREP sets others).
  • quota.exhausted when an allowance is used up, including the trial and packs.

Each is sent at most once per allowance, billing period and percentage.

{ "type": "quota.warning", "data": { "feature": "participant-minutes", "threshold": 80, "percentage": 82, "limit": 10000, "used": 8200, "remaining": 1800, "periodStart": "2026-11-01" } }
{ "type": "quota.exhausted", "data": { "feature": "rtc-recording-minutes", "periodStart": "2026-11-01" } }

Only the type and data fields are shown; the full envelope is in webhooks.

  • Admission and creation are refused with the codes above. When billing cannot answer, RTC refuses with 503 rather than admitting unbilled usage.
  • A running recording stops when its recording minutes are used up. The recording.stopped event carries reason: "allowance". It also stops when billing stays unreachable for more than 30 seconds (reason: "billing_unavailable").
  • Downloads are refused when the download allowance is used up.