Niches · Meeting capture & meeting infrastructure
Send a bot to a meeting link and get the recording and transcript
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
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. No docs we read state these figures, so they don't count against a listing here.
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 7
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.
| Listing | Why |
|---|---|
| Attendee D 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. source |
| Fireflies.ai B 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. source |
| MeetGeek C 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. source |
| Meeting BaaS B 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. source |
| MeetStream C 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. source |
| Nylas Notetaker API BB 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. source |
| Recall.ai B 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. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Read AI E 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. |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Circleback B 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. source |
| Fathom C 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. source |
| Granola B 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. source |
| tl;dv D tldx Solutions GmbH | The v1alpha1 API reads, imports and uploads meetings; no endpoint sends the recorder to a meeting link. source |
| Zoom Realtime Media Streams (RTMS) C 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. source |
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
The same as data: /api/v1/use-cases/meeting-capture.bot-to-transcript.json, or the MCP tool get_use_case with id meeting-capture.bot-to-transcript. Other jobs in this category: /api/v1/niches?category=meeting-capture.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.