Skip to main content
The live-count endpoint provides a snapshot of a shared activity counter. It does not return individual sessions, transcripts, or a connection for observing conversations.
Get live conversation count reads a workspace-level counter. Its agent_id and agent_ids parameters are currently ignored, so filtered requests must not be presented as agent-specific counts.
You need a permitted API key and a deployment with the shared cache available.
1

Read the workspace counter

Request the live count and record when you received it. Use the value only for that workspace snapshot, alongside its request success or failure.
2

Separate zero from unavailable

A missing counter key returns zero. An unavailable cache or invalid stored value produces an error. Preserve that error state instead of displaying it as zero activity.
3

Plan richer monitoring separately

Agent configuration includes conversation_config.conversation.monitoring_enabled and monitoring_events. These saved fields do not provide a released event subscription, WebSocket connection, or live transcript viewer.
Before relying on real-time monitoring, verify the released execution path, counter updates, freshness, and event delivery behavior. The counter read itself does not establish those guarantees.
Not currently. The handler reads the same workspace counter regardless of those filters.
No released subscription workflow is established by saving that field.