Hey Team, I need to understand few things on the p...
# ask-ai
r
Hey Team, I need to understand few things on the pricing for connection-duration I was trying to collate on how the duration is calculated and translated to billed connection units. In the over-view page when I select "24 hours" I get to see - 22 minutes. However now when I collate it with total duration from each session - it comes to ~12 minutes. Am I missing something here? Could you please help me to understand the correctness of my calculations ?
t
Thanks for reaching out, Mitesh. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
r
image.png
t
Hey there! Just wanted to explain how connection duration works in LiveKit and how it ties into billing, so it’s clear and easy to follow. Here’s the scoop: • Billable Participants: We only charge for human and agent participants’ connection minutes. SIP participants are billed separately under SIP connection minutes. • Calculation: For each billable participant, we track connection time in minutes and then add everything up. Keep in mind, connection time is rounded up to the nearest whole minute, so even a few seconds count as a full minute. • Cost Formula: The cost is worked out like this:
Number of Billable Participants × Session Duration (minutes) × Cost per Minute
. • Minimum Billing Increment: Every minute connected by billable participants is counted as one full connection unit. If you’re seeing a difference between your session durations (around 12 minutes) and what’s showing on the overview page (22 minutes), it might be because: • Partial minutes are rounded up to the next full minute. • There could be extra participants or sessions included that weren’t part of your manual tally. To get the most accurate picture, double-check the session lengths and participant numbers. And if you want, I’m here to help you dig into it more! Sources: LiveKit Pricing | Understanding LiveKit Cloud Pricing | Billing | LiveKit Docs | Towards a future-aligned pricing model | Billing | LiveKit Docs
Could you share a bit more about the sessions you're looking at? For example, are you including all the billable participants and keeping in mind that each session rounds up to the nearest minute? Understanding this will really help us figure out why the dashboard shows 22 minutes while your calculation comes out to 12.
r
Yes I've included all billable participants for past 24 hours and each session (attached screenshot)
t
Thanks so much for sharing the session details! Looking at the screenshot, I noticed a couple of things that might explain the difference you’re seeing: • Rounding Up: We bill connection time in 1-minute chunks. So, if a session lasts 54 or even 59 seconds, it gets rounded up to a full minute, which can make the total billed time a bit longer. • Participants: The number of participants also plays a role. For example, if 2 people join a 1-minute session, that counts as 2 connection minutes towards the total. From what I can see in the session log, it looks like the rounding and participant count are probably why there’s a gap between your manual calculation (~12 minutes) and the 22 minutes shown on the dashboard. If you want to double-check, here’s a simple way to calculate total connection minutes: 1. Round each session’s duration up to the nearest minute. 2. Multiply that rounded time by how many participants were in the session. 3. Add up all those numbers for every session. Feel free to reach out if you want me to walk you through this or help with anything else!
r
Okay so is it that since there are 11 calls with approximately 1 mins. each and in all those calls there are 2 participants hence the total units turn out to be 22 ? Is this correct?
t
Yes, you’ve got it right! Since there are 11 calls, each about 1 minute long, and each call has 2 participants, the total billed connection units come out to: 11 calls × 1 minute per call × 2 participants = 22 connection units That’s why you see 22 minutes on the dashboard. If you have any more questions, feel free to ask—I’m here to help!