Niches · Meeting capture & meeting infrastructure
Capture a meeting without a bot joining as a participant
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
A transcript with speaker labels taken from device audio, a desktop SDK or the platform's own stream, fetchable by API or MCP after the call, with the docs stating what participants see or are told.
How agents ask for it: record this call without a bot showing up
, transcribe the Zoom meeting from inside Zoom
, capture my in-person meeting
Does the job, with a limit 6
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. | Attendee-managed RTMS app sessions return transcripts and recordings with no participant added, and the guide says what users see, but it is Zoom only and the user must start the RTMS app, which needs a Marketplace app and Developer Pack. source |
| Circleback B Circleback AI, Inc. | The desktop app records Zoom, Meet, Teams or any platform from microphone and computer audio with no participant joining, and transcripts are readable by API, but how remote speakers are labelled from device audio isn't stated. source |
| Fathom C Fathom Video Inc. | The new version records botless from the desktop app, and transcripts with speaker names are readable by API, but it is a user-side setting, and the help article read doesn't say what participants see beyond the optional consent email. source |
| Granola B Granola, Inc. | Captures from device audio with no bot, the transcript is readable by API or MCP afterwards, and the docs describe the chat message and watermark participants see. Remote speakers are labelled them unless speaker tags are set up (acc-45), and transcripts need a paid plan. source |
| Recall.ai B Hyperdoc Inc. | The Desktop Recording SDK records Zoom, Teams and Meet on Windows and Apple Silicon without a bot tile, with participant events and transcripts by API, but needs an Electron app, and the docs don't say what other participants are told. source |
| Zoom Realtime Media Streams (RTMS) C Zoom Communications, Inc. | Diarised transcripts and per-participant audio come from Zoom's own stream with no bot, and the docs show precisely what participants see. Zoom only, needs Developer Pack credits sold partly through sales (acc-34), sessions can stall connecting (acc-33), and the app must store transcripts itself. source |
Couldn't check 4
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Fireflies.ai B Fireflies.AI Corp. | The API docs describe only the bot and file upload; whether Fireflies' desktop or extension capture works without a bot, and what participants see, wasn't read. |
| MeetGeek C AIVISION PRODUCTS SRL | The API has only the bot and file upload; acc-55 shows uploads from a public link left recordings exposed. Whether MeetGeek has a botless device capture wasn't found in the docs read. source |
| Read AI E Read AI, Inc. | No botless capture route could be checked; help-centre pages returned 403. |
| tl;dv D tldx Solutions GmbH | Whether tl;dv's desktop app captures without a bot, and what participants see, wasn't in the API docs read. |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Meeting BaaS B SAS SPOKE | Every capture route in the v2 API is a bot joining the meeting; no desktop SDK, device audio or RTMS route is documented. source |
| MeetStream C MeetStream Corp. | Every capture route documented is a bot in the meeting; no desktop SDK, device audio or RTMS route is in the docs index. source |
| Nylas Notetaker API BB Nylas, Inc. | Notetaker only joins as a bot participant; no desktop, device-audio or RTMS route is documented. source |
What stops agents finishing
- RTMS needs a Marketplace app, a Developer Pack and host authorisation (acc-33, acc-34)
- device-audio capture labels remote speakers only as Them (acc-45)
- desktop SDKs need a native app, not a web app
Around it
After: meeting-capture.ask-my-meetings, meeting-capture.post-meeting-push.
Where this comes from
Weight 11 of 100 in Meeting capture & meeting infrastructure: 7 of 56 accounts (acc-05, acc-17, acc-19, acc-28, acc-33, acc-34, acc-54); Zoom's end of anonymous SDK joins pushes more builders here
The same as data: /api/v1/use-cases/meeting-capture.botless-capture.json, or the MCP tool get_use_case with id meeting-capture.botless-capture. 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.