# Expose LiveKit Inference cost/pricing through AgentSessionUsage or a pricing API

**URL:** <https://community.livekit.io/t/expose-livekit-inference-cost-pricing-through-agentsessionusage-or-a-pricing-api/2109>\
**Category:** Agents\
**Tags:** livekit-cloud\
**Created:** [September 23, 2026, 1:28pm UTC](https://community.livekit.io/t/expose-livekit-inference-cost-pricing-through-agentsessionusage-or-a-pricing-api/2109 "2026-09-23T13:28:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mahimai\_Raja](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/mahimai_raja/32/543_2.png) [@Mahimai\_Raja](https://community.livekit.io/u/Mahimai_Raja)\
**Post date:** [September 23, 2026, 1:28pm UTC](https://community.livekit.io/t/expose-livekit-inference-cost-pricing-through-agentsessionusage-or-a-pricing-api/2109/1 "2026-09-23T13:28:21Z")

</div>

Hi LiveKit Team! I opened a feature request around exposing LiveKit Inference cost/pricing programmatically: [Expose LiveKit Inference cost/pricing through AgentSessionUsage or a pricing API · Issue #7420 · livekit/agents · GitHub](https://github.com/livekit/agents/issues/7420)

`AgentSessionUsage` class already gives us normalized usage per provider/model, which is great for observability. The gap I’m running into is cost.

For BYOK/provider plugins, I understand LiveKit can’t know the customer’s actual rate because that can vary by provider plan/contract. ( if this could be possible? )

But for LiveKit Inference, LiveKit is already metering and billing the model usage, so it seems like there should be an authoritative way to get either:

the cost directly from AgentSessionUsage, or  
a machine-readable pricing API/catalog that maps model + usage unit → LiveKit Inference rate.

I maintain an open-source pricing catalog for voice models here: [GitHub - mahimailabs/voice-prices: Open price database for voice AI APIs - STT, LLM, TTS, S2S, VAD · GitHub](https://github.com/mahimailabs/voice-prices)

If LiveKit exposes the pricing source, I’m happy to consume it there instead of maintaining a mirrored copy.

Curious which direction makes more sense from the LiveKit side.

Thanks!

---

<div class="post-metadata">

**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\
**Post date:** [September 23, 2026, 8:44pm UTC](https://community.livekit.io/t/expose-livekit-inference-cost-pricing-through-agentsessionusage-or-a-pricing-api/2109/2 "2026-09-23T20:44:48Z")

</div>

Team is working on exposing more via API.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\
**Post date:** [October 8, 2026, 8:45pm UTC](https://community.livekit.io/t/expose-livekit-inference-cost-pricing-through-agentsessionusage-or-a-pricing-api/2109/3 "2026-10-08T20:45:30Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.