# Send a bot to a meeting link and get the recording and transcript

> 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 & meeting infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/
- Markdown: https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/index.md (~1,550 tokens)
- Slim: https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/meeting-capture.bot-to-transcript/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 7 | 33 | 24 | 16 |

## What counts as done

One 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.

Measured, for our own tests: transcript available within 10 minutes of the meeting ending on all three platforms.

How 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

## Does the job, with a limit

It 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.

- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **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.

- 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.
- 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.
- 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.
- 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.
- 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.

## What stops agents finishing

- Google Meet blocks anonymous or datacentre-IP bots (acc-25)
- Teams captcha on external tenants with no solver (acc-26)
- Zoom external meetings need app review and an OBF token since 23 February 2026 (acc-28, acc-35, acc-36)
- bot reports recording but captures nothing after a breakout move (acc-27)
- transcript never arrives and no failure state is sent (acc-38)
- regional bot pool empty (507) for ad-hoc bots

## Around it

Before: scheduling.read-agenda, chat.user-pastes-link. After: speech-to-text.meeting-with-speakers, crm.log-activity, project-management.capture-tasks.

## Where this comes from

Weight 24 of 100 in Meeting capture & 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

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
