{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/",
    "json": "https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 7 | 33 | 24 | 16 |\n\n## What counts as done\n\nOne create call puts precisely one bot in the meeting, the API reports joined, blocked or not admitted as distinct states, and after the meeting a recording and a transcript with participant names are fetchable by API, with a completion webhook or state.\n\nMeasured, for our own tests: transcript available within 10 minutes of the meeting ending on all three platforms.\n\nHow agents ask for it: join this Zoom call and record it; send a notetaker to this Meet link; get me the transcript of the call at 3pm; record this Teams meeting\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- **Attendee (Attendee Labs, Inc.)**: POST /bots takes deduplication_key, sub-codes separate waiting-room timeout, join denied, captcha and login required, utterances carry speaker_name, and post_processing_completed fires signed. Teams captcha on external tenants and silent breakout capture are open issues.\n- **Fireflies.ai (Fireflies.AI Corp.)**: addToLiveMeeting sends the Fred bot to a meeting link and meeting.bot_joined and meeting.transcribed webhooks follow, but it is limited to 3 calls per 20 minutes, takes no idempotency key, and reports no blocked or not-admitted state.\n- **MeetGeek (AIVISION PRODUCTS SRL)**: POST /v1/bot/join takes a join_link and returns a meeting_id, and the transcript comes back with speaker names, but there's no idempotency key, no joined, blocked or not-admitted state, and the failed-analysis webhook carries no meeting id.\n- **Meeting BaaS (SAS SPOKE)**: Statuses separate in_waiting_room, bot_rejected, waiting_room_timeout and MEET_LOGIN_REQUIRED, Svix-signed bot.completed and bot.failed fire, and utterances carry speaker names. Duplicate protection is opt-in (allow_multiple_bots defaults true), and external Zoom needs the customer's own app with an OBF user present.\n- **MeetStream (MeetStream Corp.)**: Idempotency-Key and deduplication_key stop second bots, events separate waiting room, denied, not allowed and failed with a Meet failure_reason, and HMAC-signed transcription.processed or transcription.failed close the loop. External Zoom needs the customer's own reviewed Zoom app plus ZAK or OBF.\n- **Nylas Notetaker API (Nylas, Inc.)**: States separate connecting, waiting_for_entry and failed_entry with reasons (no_response, entry_denied, host_sign_in_required), and a signed notetaker.media webhook brings a speaker-labelled transcript. Invites take no idempotency key, and the bot is always an unauthenticated guest, so sign-in-only meetings reject it.\n- **Recall.ai (Hyperdoc Inc.)**: Create Bot takes an Idempotency-Key, sub-codes separate waiting room, kicked, captcha, Meet bot blocked and OBF missing, and transcript.done or transcript.failed webhooks close the loop. Ad-hoc bots can get 507, and acc-38 saw a Meet transcript never return.\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 API and MCP reference is a help-centre article that returned 403; whether the bot can be sent by API with join states and a completion signal couldn't be read.\n\n- not this job: Circleback (Circleback AI, Inc.): A meeting link can be pasted into the Circleback app, but neither the REST API nor the MCP tool list has a call to send the bot or report its join state.\n- not this job: Fathom (Fathom Video Inc.): The API has no call to send a recorder to a meeting link; capture is started by the Fathom user's own app or settings.\n- not this job: Granola (Granola, Inc.): Granola has no bot and no call to start a capture; it transcribes only when the user opens a note in the desktop or mobile app.\n- not this job: tl;dv (tldx Solutions GmbH): The v1alpha1 API reads, imports and uploads meetings; no endpoint sends the recorder to a meeting link.\n- not this job: Zoom Realtime Media Streams (RTMS) (Zoom Communications, Inc.): RTMS sends no bot from a meeting link: a Marketplace app the host or participant authorises starts a stream, on Zoom only, and Zoom stores no recording or transcript for the app to fetch afterwards.\n\n## What stops agents finishing\n\n- Google Meet blocks anonymous or datacentre-IP bots (acc-25)\n- Teams captcha on external tenants with no solver (acc-26)\n- Zoom external meetings need app review and an OBF token since 23 February 2026 (acc-28, acc-35, acc-36)\n- bot reports recording but captures nothing after a breakout move (acc-27)\n- transcript never arrives and no failure state is sent (acc-38)\n- regional bot pool empty (507) for ad-hoc bots\n\n## Around it\n\nBefore: scheduling.read-agenda, chat.user-pastes-link. After: speech-to-text.meeting-with-speakers, crm.log-activity, project-management.capture-tasks.\n\n## Where this comes from\n\nWeight 24 of 100 in Meeting capture \u0026 meeting infrastructure: 16 of 56 accounts; the job named in every bot-API thread (Recall Launch HN, Attendee Show HN) and in all Attendee and Zoom forum failure reports read\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/meeting-capture.bot-to-transcript.json, or the MCP tool get_use_case with id meeting-capture.bot-to-transcript. 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": "Send a bot to a meeting link and get the recording and transcript",
        "url": ""
      }
    ],
    "description": "Send a bot to a meeting link and get the recording and transcript: 0 companies fully do it, 7 with a limit, 33 carry the tag. Every listing in Meeting capture \u0026 meeting infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Send a bot to a meeting link and get the recording and transcript",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/meeting-capture.bot-to-transcript/",
    "published": "",
    "section": "agents",
    "title": "Send a bot to a meeting link and get the recording and transcript |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/"
  },
  "tokens": {
    "markdown": 1550,
    "slim": 330
  },
  "version": 1
}
