{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/meeting-capture.live-in-meeting/",
    "json": "https://www.anchorterminal.com/niches/meeting-capture.live-in-meeting/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/meeting-capture.live-in-meeting/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/meeting-capture.live-in-meeting/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 2 | 47 | 13 | 9 |\n\n## What counts as done\n\nA transcript or per-participant audio stream arrives over a webhook or WebSocket during the call with each segment tied to a named participant, and the bot can play audio or post chat through a documented endpoint.\n\nMeasured, for our own tests: words arrive within 1 second of being spoken, and the stream reconnects after a drop without losing the session.\n\nHow agents ask for it: listen to the call and flag risks as they come up; answer questions in the meeting; take live minutes and stop when told; show live speaking time\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Attendee (Attendee Labs, Inc.)**: websocket_settings.per_participant_audio streams audio tagged with participant_uuid, transcript.update webhooks carry speaker_name per utterance, and output_audio, send_chat_message and a bidirectional audio WebSocket let the bot speak and chat. WebSocket reconnects up to 30 times.\n- **Recall.ai (Hyperdoc Inc.)**: Real-time transcription sends utterances with participant name over webhook or WebSocket, separate audio per participant is streamed, and output media, output audio and chat endpoints let the bot act. WebSocket retries 30 times at 3 seconds.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Meeting BaaS (SAS SPOKE)**: Bidirectional WebSocket streaming lets the bot hear and speak, and send-chat-message posts chat, but streamed audio is mixed only, and live transcript segments name the active speaker at that moment, null when unknown; Teams speaker detection lags 1 to 2 seconds.\n- **MeetStream (MeetStream Corp.)**: Live audio arrives as WebSocket frames tagged with speaker_id and speaker_name, live transcripts carry speakerName, and the bot can chat and show images. The docs put live transcripts a second or two after speech, outside the 1-second bar.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Read AI (Read AI, Inc.)**: The plans page names an in-meeting dashboard for the user, but no live API, stream or output endpoint could be checked; the reference returned 403.\n\n- not this job: Circleback (Circleback AI, Inc.): API, MCP and webhooks deliver meetings after they end; no live transcript, stream or in-meeting output is documented.\n- not this job: Fathom (Fathom Video Inc.): API and webhooks deliver content after a meeting is ready; there's no live transcript, audio stream or in-meeting output.\n- not this job: Fireflies.ai (Fireflies.AI Corp.): The Realtime API streams live transcript segments with speaker_name over WebSocket, but no documented call lets the bot speak or post chat, so the success can't be met.\n- not this job: Granola (Granola, Inc.): The live transcript shows only inside the app; the API and MCP expose notes after they exist, with no stream or in-meeting output.\n- not this job: MeetGeek (AIVISION PRODUCTS SRL): Meetings are readable only after analysis; no live stream, chat or audio output endpoint is in the API or MCP tools.\n- not this job: Nylas Notetaker API (Nylas, Inc.): Notetaker outputs arrive only after the meeting; the docs index lists no live transcript, audio stream or output-audio endpoint, only chat announcements and a static camera image.\n- not this job: tl;dv (tldx Solutions GmbH): Meetings and transcripts are readable only once ready; no live stream or in-meeting output exists in the API.\n- not this job: Zoom Realtime Media Streams (RTMS) (Zoom Communications, Inc.): Per-participant audio with user_name and diarised transcripts stream over WebSocket, with reconnect guidance, but RTMS is receive-only: no documented endpoint lets the app speak or post chat, so the success can't be met.\n\n## What stops agents finishing\n\n- live text comes from platform captions 1.5 to 2 seconds late (acc-42)\n- RTMS needs a Developer Pack sold only through sales on some accounts (acc-34)\n- RTMS session stuck connecting with no event (acc-33)\n- speaker ID blank in RTMS audio metadata (acc-31, acc-32)\n- no speech-end or silence event (acc-37)\n\n## Around it\n\nBefore: meeting-capture.bot-to-transcript. After: voice-agents.tool-call-mid-call, company-knowledge.cited-answer.\n\n## Where this comes from\n\nWeight 13 of 100 in Meeting capture \u0026 meeting infrastructure: 9 of 56 accounts: four in-meeting agents (acc-22, acc-23, acc-42, acc-43) and five RTMS reports (acc-31, acc-32, acc-33, acc-34, acc-37)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/meeting-capture.live-in-meeting.json, or the MCP tool get_use_case with id meeting-capture.live-in-meeting. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Stream the meeting live to an agent that acts or speaks during the call",
        "url": ""
      }
    ],
    "description": "Stream the meeting live to an agent that acts or speaks during the call: 2 companies fully do it, 2 with a limit, 47 carry the tag. Every listing in Meeting capture \u0026 meeting infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Stream the meeting live to an agent that acts or speaks during the call",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/meeting-capture.live-in-meeting/",
    "published": "",
    "section": "agents",
    "title": "Stream the meeting live to an agent that acts or speaks during the…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/meeting-capture.live-in-meeting/"
  },
  "tokens": {
    "markdown": 1400,
    "slim": 280
  },
  "version": 1
}
